How to use Filter Controls, the details

SNIP has a powerful console filtering mechanism built into the tool. These controls allow the log to be re-displayed with filtering of its content. This allows displaying in the log ONLY what you the administrator need to see,rather than trying to read over the log when potentially many thousands of other entries are present.   Using the individual filters is covered further in the knowledge base (KB) articles below.

FilterMenus2-merged2In an active SNIP NTRIP Caster with dozens of active connections and many clients, these new abilities are useful to filter the displayed console information to only the context of current interest.  At any given time, users are connecting and casters are either working or not. [Aside: as a rough worldwide summary, and considering only “professional grade” CORS caster installations, any given caster is in fact off-line about 2~3% of the time.]  So the console log becomes full of many different asynchronous connection events. These filters allow the administrator to cleanly sort things out.  It is used to control


Detailed KB articles on filtering

  • The Log Threshold control.  This control sets the verbosity of the log, more minor entries are filtered
  • Filtering by Stream Type.  The control allows removing entire types of entries (such as suppressing client details)
  • Filtering by Data Stream (mountPt).  The control allow removing data about specific data streams

The controls are used together to determine whether a given console log entry is displayed.  All console log entries are always kept.  The filter does not remove any entries, so you can always go back and look at any prior event, (up to the prior 5,000th entry). The display is regenerated when any control changes, and a Refresh tool button can also force this to occur.

Hint#1:  It is common to clear away the existing console clutter (press the trash can icon) then then have SNIP regenerate only the data of current interest. Log contents are never lost by this, only reordered and redisplayed.

Hint#2: The console will not scroll if the slider is not at the bottom of the window.  So to stop a busy log from scrolling when reading it, simply scroll it a line or two.  The display will remain static until you again scroll to the bottom.

A Simple Example of Filtering in in Use

Here is a simple example of using the filter control to assist a new NTRIP Client with debugging a connection problem, a common support operation for Caster operators.

Capturing the Console for further Analysis

Here is an article how to capture the console log entries to a file for further use.

 

Was this article helpful?

Related Articles

Leave A Comment?

You must be logged in to post a comment.