Licensing for resource checks

• Related Articles

• Resource checks that support monitoring of remote and shared disk partition

  Please note that most of the file and directory resource checks might not work when you are trying to monitor remote and shared disk partitions. This is due to the restrictions in the Linux subsystem "inotify" while listening for disk access events ...

• Average resource utilization by AppLogs agent

  Metrics Windows Linux CPU < 1% 0.3% Memory 40 MB 25 MB Peak network 2 MB in 30 seconds 2 MB in 30 seconds Disk 100 MB 100 MB This resource utilization is subject to change when more log types are associated with a single server or the same AppLogs ...

• Different types of resources/checks that can be added and monitored

  There are 14 different types of resource checks in total. They allow you to monitor: Ports  URLs Windows event log Linux syslog File access File modification File Content File Size File Permissions change Directory size Directory access Directory ...

• Troubleshooting steps if a resource check is not added or when no alerts are received when a check fails

  Common points to be remembered: Ensure the option Alert when a resource check fails is set to Yes in the associated server's threshold profile to trigger a TROUBLE alert for the configured check.   Check if you have sufficient licensing. The total ...

• Licensing for Kubernetes monitoring

   The main Kubernetes cluster is considered one basic monitor. For the other components, the licensing is done as follows:  Component Licensing Nodes 1 monitor consumes one basic license Pods 5 monitors consume one basic license Containers 5 monitors ...