Info | ||
---|---|---|
| ||
Caution: This feature is still in beta and can change at any time. This feature should be used in non production environments. In due course this will replace Business Services. |
To enable Enterprise Services add this to opCommon.json and restart the omkd daemon.
Beta testing and hence may undergo further changes. Therefore, you are advised NOT to use this in any production environment. This may also, in future, replace Business Services. |
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 on a single page. You can also group any related Interfaces/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 |
---|
Future Development: 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.
...
Overview
Enterprise Services display interface status panels and node status panels in a single page. This allows grouping related interfaces/nodes together to have a single location that a user can see these related items.
Enterprise Services are supported under the MSP authorization system when added as a dashboard component, RBAC for enterprise services is still being worked on.
How metrics are calculated
Nodes
...
j son /beta/opcharts_enterprise_services=true
...
Restart the
omkd
daemonCode 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.
If any node Node is unreachable, the enterprise service Enterprise Service is marked unreachable, if nodes are degraded but none are unreachable the enterprise service is marked degraded.
Interfaces
Interfaces down metrics are calculated by getting all interface inventory with the status "Interface Down", and store a count of these interfaces.
The overall interface status is calculated from all interfaces related status level and averaged out.
If any interface is marked "Interface Down" the enterprise service is marked unreachable.
Monitored Services
All service inventory tagged with the enterprise service name is aggerated to get the current status. If any monitored service is marked down then enterprise service is marked unreachable.
Overall Status
Overall Status can be Up, Degraded or Down Unreachable. If a Node is Reachable, but it is not at its optimal level/health, the Service is marked Degraded.
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.
Overall Status: The Overall Status can be Status colour Green title Up
, Status subtle true colour Yellow title Degraded
,
colour | Green |
---|---|
title | Up |
subtle | true |
---|---|
colour | Yellow |
title | Degraded |
...
or Status colour Red title Down
colour | Red |
---|---|
title | Down |
The overall state of the enterprise service Enterprise Service is calculated from the worst state of each one of the services.
Monitored Services | Nodes | Interfaces |
---|---|---|
Services Fatal | Nodes Unreachable | Interfaces Down |
Services Degraded | Nodes Degraded | Interfaces Up |
Services Up | Node Up | |
Status | Status | Status |
Enterprise Service Rules
Enterprise service rules calculate how each group of entities control the status of the service.
The rules set out levels on how each component should be degraded, based on the status level, its . It is set as an array of Level Type and Level.
so For example, Normal , - 100, Degraded , – 90 would mean, a status of 99 would be reachable Reachable but a status of 89 would be degraded, you Degraded.
You can use this to tune the alerts. Any Level Type not Normal put raise For example, you can configure a proactive enterprise alert for this service.
...
any service if any Level Type is not Normal.
Adding Status Panels/Tables
After creating a new Enterprise Service on the opCharts, you can add Interfaces, Nodes and Monitored Services status panels/tables to it.
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".
...