Aside from being beneficial from a visualisation and analytical perspective, Hashtags can be used to control what Users can see when they log-in to Opsview Monitor.
This means you can navigate through ‘Settings > Hosts’ and ‘Settings > Service Checks’, tag objects (Hosts/Service Checks) with our previously created ‘superimportant’ Hashtag, and then create a Role that gives Users access to only view/configure (depending on the configuration within the Role) objects tagged with ‘SUPERIMPORTANT’. When Users who are members of the new Role log in, they will only be able to view/configure objects that were appropriately tagged.
This is a really nice way of configuring access control; it means once you have configured a new Role to restrict User’s visibility to just objects tagged with ‘SUPERIMPORTANT’, you can grant visibility to new objects (i.e. newly added Hosts) simply by assigning them the Hashtag ‘SUPERIMPORTANT’.
For information on how to configure Roles, view Roles.
The 'New Hashtag' configuration window contains two tabs. The first of these is the 'Hashtags' tab:
Within this tab, you can can set the following fields:
- Name: The actual Hashtag, i.e. 'SUPERIMPORTANT'. NOTE: Don't include the # symbol here, it is used purely for display within the product.
- Hashtag View: Enabled/Disabled. If set to Disabled, the Hashtag will not be visible within 'Monitoring > Hashtags'; however it will be visible still within filtering options for Event Viewer, and also within various Settings sections including Roles, Notification Profiles and more. Note: If this is set to disabled, the below fields will all be hidden.
- Public: If checked, unauthenticated users will be able view the Hashtag within 'Monitoring > Hashtags'.
- Description: A friendly, descriptive name. For example, if the Hashtag is 'apache', the description could be set to 'Apache Web Servers'. This is the name that will appear below the Hashtag within the analysis view, i.e. below we have a Hashtag with the name 'data-center-c' and the Description 'Data Center C: New York'.
- Exclude Handed: As covered in the Overview section, this option tells the Hashtag to only calculate its state based on unhandled states. For example, if the Hashtag above contained 4 CRITICAL Service Checks but they were all handled, then the Hashtag would display as 'OK' / Green if this option were checked.
The second of the tabs is the 'Objects' tab:
The Objects tab is where you can choose what objects are tagged with the new Hashtag.
You can choose to select Hosts first and then filter the list of Service Checks to just list Service Checks that the selected Hosts have. You can also choose to select the Service Checks first and select the 'All Hosts with these Service Checks' box, which tells Opsview Monitor ' 'Any Host that has the selected Service Checks, tag with this Hashtag'.
In our example, we are going to tag all Hosts that have Apache Service Checks with our new Hashtag:
This means that if we now add ten Hosts that have one of these Service Checks applied, they will be tagged with 'SUPERIMPORTANT'.
This Hashtag will be visible from within the Hosts Settings window as below:
The Hashtag is visible on the 'Globally Applied Hashtags:' line, instead of the 'Hashtags:' line above it, as the Hashtag was assigned via the 'Settings > Hashtags' section and not on a per-Host basis. This means that if you wanted to un-Hashtag this Host, i.e. remove 'SUPERIMPORTANT', you would have to do so via 'Settings > Hashtags'.