Unix/Linux monitoring is too limited. Need advanced monitoring Rules/Monitors.5 votes
we should focus towrards unix monitoring like we need enhance it for Docker and Linux certificate monitoring. And should also closly work on office 365 momitoring.
I am working with 2 clients and Linux monitoring is not at that par good and office 365 too.4 votes
Could SCOM 2012 monitor the Linux server (CentOS) through SNMP Trap without installing agent on Linux server?
Could we check whether the below MIBs files already included in the existing SCOM server?
- The HOST-RESOURCES_MIB
- Apache web server configuration and status values (APACHE2-MIB).
- disk I/O (UCD-DISKIO-MIB)1 vote
include two new monitors in all of the UX based MP's that does monitoring of memory by percentage used. monitors can be disabled by default. monitor A would calculate percentage free (free / total). Monitor B would calculate the same but include cache1 vote
It would be nice if we could create baselining monitors on any rule that's generating performance data in Operations Manager. Currently, you can only create baselining monitors for Windows Performance Counters.1 vote
Currently admins/users have to look at the Unix/Linux Computers view to see which Resource Pool is monitoring them, and then look at the Resource Pool view, and properties of the resource pool to see its members and the servers responsible for those unix computers.
It'd be great if there were a view that simply showed the management servers in the pool responsible for the unix/linux agent in ONE view. and not have to click in 3 different places to connect the dots.5 votes
You have unix/linux log monitoring deployed on a server.
You put the server on maintenance mode for x hours.
<During Maintenance Mode>
During x hours, there are lines that written to the log which would trigger the alert. But alert not triggered since it's in maintenance mode.
<Maintenance Mode Over/>
Log monitoring policy kicks-in. It scans the log file again using the counter BEFORE the maintenance mode. The lines that written during maintenance mode got scanned and triggered an alert. This should not happened.
- Clean the counter file after maintenance mode over.7 votes
The introduced functions for monitoring MySQL is a great step in the right direction, but to be of any real value in the business this functionality needs to be extended with support for Monitoring MySQL Clusters.
The Pack should discover if the node is configured as a cluster member, identify the remaining partners, and adopt monitoring to expose cluster related health details.1 vote
- Don't see your idea?