{"id":1378,"date":"2016-05-15T18:35:06","date_gmt":"2016-05-15T18:35:06","guid":{"rendered":"\/?post_type=ht_kb&p=1378"},"modified":"2018-03-10T20:51:26","modified_gmt":"2018-03-10T20:51:26","slug":"how-to-use-filter-controls-the-details","status":"publish","type":"ht_kb","link":"https:\/\/www.use-snip.com\/kb\/knowledge-base\/how-to-use-filter-controls-the-details\/","title":{"rendered":"How to use Filter Controls, the details"},"content":{"rendered":"

SNIP<\/strong><\/span> 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.\u00a0\u00a0 Using the individual filters is covered further in the knowledge base (KB) articles below.<\/p>\n

\"FilterMenus2-merged2\"<\/a>In an active SNIP<\/strong> NTRIP Caster<\/a> 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.\u00a0 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.]\u00a0 So the console log becomes full of many different asynchronous connection events. These filters allow the administrator to cleanly sort things out.\u00a0 It is used to control<\/p>\n

\n

Detailed KB articles on filtering<\/h4>\n