This section provides an overview of Hashtags, what they are, how they work, how to use them and how to analyze them.
A Hashtag in Opsview Monitor works very similar to Hashtags within well-known social media platforms such as Twitter © and Facebook ©. You can 'tag' various objects within Opsview Monitor such as Hosts and Service Checks with a Hashtag '#superimportant', and then do things based on that Hashtag. These include only give users the ability to view objects in the UI that are tagged with #superimportant, only notify users for objects that have failed if they are tagged with #superimportant, and so on.
The power of Hashtags is incredible and it reduces the management overhead significantly. For example, if you add 20 new Hosts ' you may need to edit 15+ roles to update the access control so the relevant users can see the new Hosts. Instead you can simply tag them with the relevant hashtags and they will appear within the user interface for those users once logged in. For example, tag the new Windows Server 2008 Hosts with #windowsservers, which will allow Windows Administrators to view them within Opsview Monitor.
Aside from using Hashtags for notifications and access control, you can also use them for analytics. For example, you can create hundreds of Hashtags in your Opsview Monitor system, but choose to only set 20 of them to be 'visible'.
By changing a Hashtag to be 'visible' you can analyze it via 'Monitoring > Hashtags'; this allows you to tag every Apache-related Service Check with the Hashtag #apache, and once it is set to visible you can view it within Monitoring > Hashtags. If a Service Check tagged with #apache changes from an OK state to WARNING, then the Hashtag will change to yellow/WARNING:
If a Service Check tagged with #apache changes from an OK/WARNING state to CRITICAL, then the Hashtag will change to red/CRITICAL:
These views are great in that you can tag software, hardware, locations and more ' and then if there a problem within that location, for example, you will be able to view it via the visible Hashtag:
If all problems (i.e. WARNING, CRITICAL, UNKNOWN) Service Checks are 'Handled', i.e. they've been acknowledged, then either a check will appear, meaning 'There are problems on objects tagged with #apache, but they are all in a handled state':
Or alternatively, you can choose to configure the Hashtag in a way that says 'If there are any Service Checks in a problem state tagged with #apache, change the Hashtag to be red/CRITICAL; however, if all of these problem Service Checks are handled, then change the Hashtag back to being green/OK'. This effectively tells the Hashtag to only look at unhandled Service Checks when determining its state. (This setting can be configured on a Hashtag by Hashtag basis).
You can also undertake 'Actions' on Hashtags, including:
- Schedule Downtime
- Mass Re-Check
- Mass Acknowledge
- Set Service Status.
This allows you to schedule downtime on everything tagged with #location-1, for example. This way you can undertake maintenance on anything tagged with #location-1, and notifications for example will not be generated due to the scheduled downtime that has been set.
Finally, Hashtags can be used for filtering the Events Viewer (Monitoring > Events Viewer). By default, Events Viewer will list all Events generated within the past day:
This list could be large, depending on the number of Hosts within the Opsview Monitor software ' and the number of state changes that have occurred. You can filter this list of events using Hashtags by clicking on the 'Filter Options' button and selecting the Hashtags tab, as shown below:
In the example below, I have filtered on the Hashtag 'SAN':
This filter is visible at the bottom of the Events Viewer window:
This view can then be further filtered via the 'Filter Options' window and then shared via the 'Share Link' button on the top navigation bar:
By clicking the 'Arrow' icon in the top navigation bar, the 'Share View' window will load. This window contains a unique URL which, when entered into a browser, will load the Event Viewer as it is currently is; in our example filtered on the Hashtag 'SAN'.
These Hashtag and Event Viewer windows can also be added to the 'My Dashboards' section (As covered in Section 4.16), and filtered using Hashtags, as shown below: