Granularity in monitoring settings

Panorama9 will look for issues throughout your network. Sometimes the preconfigured settings may not fit your IT environment. Tweaking Panorama9 will allow you to define thresholds so it only generates the issues you need.

Screenshot-Panorama9 | Dashboard - Mozilla Firefox.png

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

Configure threshold settings

To configure the threshold values navigate to "Monitoring" -> "Thresholds".

Here you will be creating templates whereas the "Scope" selected will determine what type of machines or peripherals that 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 Panorama9. 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  Panorama9 receives the list of installed software from a device (this can take up to 24 hours).

 

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

The 30 minute (1800 seconds) timeout for generating issues when computers are left unlocked is too strict and you wish to expand it to 60 minutes (3600 seconds). Also you would like the timeout for servers to be 10 minutes (600 seconds) since they should never be left unlocked.
Create one new setting for scope "Server" and scroll to "Compliance Issues". Write 600 (the system counts seconds) 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" or whatever makes sense to you and click "Save" when done.

Create a second setting for scope "Computer" and scroll to "Compliance Issues". Write 3600 (the system counts seconds) 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" or whatever makes sens to you 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" that for any good reason should never be above e.g. 50% full since it must have enough free space for what you need it for. Create a new template and call it whatever makes sense to you. Add the device "SRV-ABC" under "Apply to these devices only" and scroll to the "Server capacity - consider drive full at" value and enter 50 in this case. Click "Save" when done.

Last updated:

Comments