...
| title | Caution |
|---|
This feature is still in Beta testing and hence may undergo further changes. Therefore, you are advised NOT to use this in any production environment.
...
Table of Contents
Table of Contents
Overview
opCharts enables you to build dynamic interactive charts and targeted custom dashboards for single-pane-of-glass views into your NMIS data. It increases your network visibility and accelerates root cause discovery by combining multiple data sets on its adaptable graphical interface.
You can create one such dashboard to monitor Enterprise Services too, which allows you to view Interface and Node status panels for Interfaces, Monitored Services and Nodes on a single page. You can also group any related Interfaces/Monitored Services/Nodes together to view them all at one location. Further, the MSP authorization system supports the Enterprise Services when added as a dashboard component.
| Info | ||
|---|---|---|
| ||
RBAC support will be added for Enterprise Services soon. |
Enabling Enterprise Services
To enable Enterprise Services –
Add the following code to opcommon.json
| Code Block |
|---|
"beta":{
"opcharts_enterprise_services": "true"
}, |
Execute the following commands
| Code Block |
|---|
sudo/usr/local/omk/bin/patch_config.exe /usr/local/omk/conf/opCommon.j
son /beta/opcharts_enterprise_services=true |
Restart the omkd daemon
| Code Block |
|---|
sudoservice omkd restart |
Service Metrics
Node Status: The Node Status is calculated from the status events for the Node. It aggregates the status event levels and presents an average of the same.
Enterprise Service Metrics
- Nodes State: If any Node is unreachable, the
...
- Nodes State is marked
...
- Down. If
...
- any Node is
...
- degraded, the
...
- Nodes State is marked Degraded, otherwise it is Normal.
Interface Status: The Interface status is calculated by aggregating all the Interface-related status levels and averaging them out.
The Down Metrics shows all the Interfaces marked as Interface Down. It stores a count of such Interfaces.
If any Interface is marked Interface Down, the Enterprise Service is marked Unreachable.
Monitored Services: The Service Status shows the aggregate of all service inventory tagged with the Enterprise Service name.
If any monitored Service is marked Down, then the Enterprise Service is marked Unreachable.
...
- Interfaces State: If any Interface is marked Down, the Interfaces State is marked Down, otherwise it is Normal.
- Services State: If any Monitored Service is marked Down, then the Services State is marked Down. If any Monitored Service is degraded, the Services State is marked Degraded, otherwise it is Normal.
- Overall State: The Overall State can be
,Status colour Green title Up Status
...
, orcolour Yellow title Degraded Status colour Red title Down
The
...
- Overall State of the Enterprise Service is calculated from the worst
...
- of
...
- the
...
- Nodes State, Interfaces State and Services State, where Up is best and Down is worst.
So if each State is Normal, the Overall State will be Up, but if any of the States is Down the Overall State will be Down, or if the States are Normal and Degraded then the Overall State will be Degraded.
- Node Status:The Node Status is calculated from the status events for the Nodes. It aggregates the status event levels and presents an average of 0% to 100%.
- Interface Status: The Interface Status is calculated by aggregating all the Interface-related status event levels and averaging them out 0% to 100%.
- Service Status: The Service Status shows the average status event level of all the Monitored Services for the Enterprise Service 0% to 100%.
Enterprise Service Rules
Enterprise service Service rules calculate how each group of entities control the status of the service.Enterprise Service. The Enterprise Service rules are defined in /usr/local/omk/conf/ES_Rules.json
The rules set out levels on how each component should be degraded, based on the status level. It is set as an array of Level Type and Level.
...
You can use this to tune the alerts. For example, you can configure a proactive enterprise alert for any service if any Level Type is not Normal.
Adding
...
Nodes, Interfaces and Monitored Services
After creating a new Enterprise Service on the opCharts, you can add Nodes, Interfaces, Nodes and Monitored Services status panels/tables to it.to it. At the top of the Enterprise Service page you will see a row of buttons for each option:
Click on one of the options, and the page for that option will load. Click the '+' icon to add a Node.
Add an Interface
To add a new interface, press the "+" icon in the Interfaces section as shown in the screen shot above. Enter or select the node name, select the interface index/name and press "Add".
Add a Node
Adding a Node is similar, press the "+" icon in the Nodes section. Enter the node name and press the "Add" button, a node panel for and the selected node should now be displayedwill be added to Enterprise Service.
Add a Monitored Service
In opCharts 4.8.1 and newer you can now add Nodes, Interfaces and Monitored Services directly to an Enterprise Service from their relevant views.
Choose the items that you want added to an Enterprise Service using opCharts' advanced filtering capabilities, then to the left click on the checkbox for that item/s. You will notice a new button become visible, click this and then click on 'Enterprise Service'. You can then choose the Enterprise Service to add to.
Remove an Interface, Node or Service
To remove either, press the "x" icon near the top right of the panel and it will be removed from the document. Save the document to accept your changes.
Repair RBAC for an Enterprise Service
We changed how an Enterprise Service is referenced in the database with opCharts-4.5.0 and this causes issues with RBAC (portal users) for Enterprise Services created before 4.5.0.
Easy method, delete the Enterprise Service and recreate with the same name, the nodes, interfaces and services will still be attached to the Enterprise Service.
You will need to add the roles you had before.