Please submit any feature requests and vote on ideas that have already been submitted to indicate your interest in seeing them developed
Most of our customers with appetite for monitoring components would consider integration in their existing landscape and allowing the departments to look at the dashboards we currently deploy with nMonitoring.
As the information is already consolidated in nMonitoring database, opening access to external systems would enabling us to reach two types of audience, and in practical terms more than double the chances of closing a deal: many companies have this kind of budget sitting in the IT departments. IT Departments go for consolidation of tools, meaning their appetite for integrating something with the existing monitoring platform is prefered, while installing another standalone monitoring tool is often rejected. The value of the standalone tool would be fully preserved to the Lab Operations team.
A second reason for the functionality is that the risk of the customer monitoring impact on lab routine would be minimal, once nMon safely collects all data.
The customers who have a central IT component monitoring process (Operation Center concept) would benefit from including critical events from automated labs in the their monitoring platforms (examples are Grafana, Nagios, windows server monitoring, PRTG, among others).
This is generally done via Interface/api/open database to share events.
Guest
|
Idea detail description
The customers who have a central IT component monitoring process (Operation Center concept) would benefit from including critical events from automated labs in the their monitoring platforms (examples are Grafana, Nagios, windows server monitoring, PRTG, among others). This is generally done via Interface/api/open database to share events. |
