Granularity in monitoring settings

The Panorama9 system will look for issues throughout your network. It's done using a long list of triggers and thresholds values that determines if something looks broken or requires your attention. But sometimes these preconfigured settings may not fit your IT environment. If a monitoring system is to be trusted and useful then it must be able to distinguish between a true problem and a situation that is normal. Tweaking the Panorama9 system will allow you to define thresholds that during analysis of collected data only triggers and generate an issue that you consider to be valid.

Screenshot-Panorama9 | Dashboard - Mozilla Firefox.png

You may configure threshold settings and apply them to all devices in your network, a group of devices or a single machine. You have complete control and can anytime update them or revert to the default Panorama9 values. 

Configure threshold settings

To configure the threshold values login to the Panorama9 dashboard and navigate to "Monitoring" -> "Threshold".

When you create a new settings template the "Scope" selected will determine what machines or peripherals are targeted.
All devices in a selected scope will be targeted by default (e.g. all servers if scope is "Server"), unless devices or machines are entered explicitly in "Apply to these devices only". You can either choose to target  individual machines or peripherals or groups of machines.
Note that some scopes where targeting devices does not apply. These are "Internet service" and "Misc". You can only create a single setting instance of each.
The same applies to settings targeting all devices in a scope. Only one instance is allowed of e.g. scope "Server" when "Apply to these devices only" is empty. Multiple instances are allowed when targeting different devices in the same scope.

When a new setting template is created all the values seen are the defaults used by the Panorama9 system. Any fields with changes from the default values will appear with golden border. You can even hover the mouse over a field to see the change(s) compared to the default.

Below are three examples that will illustrate how to apply threshold values.

 

Example 1 - stop Panorama9 from flagging Bittorrent as an unapproved P2P application

You have a valid reason why all your computers and servers should have the Bittorrent client installed. By Default Panorama9 will flag the application as P2P file sharing software and generate a compliance issue. You can quickly whitelist the application by creating two settings with scope "server" and "computer".
Leave the "Apply to these devices only" empty as we want to target ALL devices in each scope.
Scroll down to "P2P file sharing applications" and just delete "Bittorrent" from the list and then click "Save" for each template.

Already generated issues will be marked as solved next time the Panorama9 system receives the list of installed software from a device (this may take up to 24 hours).

 

Example 2 - set timeout for when devices are considered to be left unlocked.

You think that the 30 minute timeout for generating issues when computers are left unlocked is too strict and wish to expand it to 60 minutes. Also you would like the timeout for servers to be 10 minutes since they should never be left unlocked.
Create one new setting for scope "Server" and scroll to "Compliance Issues". Write 600 in the appropriate field. Again, leave the "Apply to these devices only" empty to target ALL devices in the scope "Server".
Call it "All servers" and click "Save" when done.

Create a second setting for scope "Computer" and scroll to "Compliance Issues". Write 3600 in the appropriate field. Again, leave the "Apply to these devices only" empty to target ALL devices in the scope "Computer".
Call it "All computers" and click "Save" when done.

Screenshot-Panorama9___Thresholds_-_Mozilla_Firefox.png

 

Example 3 - Panorama9 should not generate SLA issues for a specific device

You have a server named "SRV-ABC" with a large disk setup that for a good reason should never be above 50% full since it must have enough free space when restoring from a backup. Create a new setting instance and give it a meaningfull name. Add the device "SRV-ABC" to "Apply to these devices only" and scroll to the "Server capacity - consider drive full at" value and enter 50. Click "Save" and Panorama9 will warn you when less than 50% of the disk space is available.

Last updated:

Comments