0
3.15.1
Zurich, Yokohama Patch 4, Xanadu, Washington DC, Vancouver Patch 7, Vancouver, Utah
The ITOM Agent Client Collector Monitoring solution provides the ability to monitor your CIs. This application comes with pre-defined monitoring checks and policies that are applied on the agent. The solution is extendable, allowing you to define new checks and monitoring policies.
The ServiceNow® Agent Client Collector (ACC) application offers centralized agent management, allowing you to:
- Monitor service availability and ensure that your infrastructure and applications are running smoothly with minimal server resource consumption.
- Replace manual processes with flexible, centrally administered monitoring policies.
- Simplify operations through streamlined events and metrics processing.
- Detect anomalies and generate anomaly alerts.
- Meet strict security requirements by ensuring data encryption and secure communication over encrypted links.
- Eliminate redundant CI discovery and inconsistencies caused by multiple CI records, reducing dependency on third-party monitoring solutions.
- Collect performance metrics from hosts into the ServiceNow instance, providing a comprehensive view of affected CIs and their directly related components, enabling root cause analysis and improving MTTR (Mean Time to Resolution).
The ACC is available as a complete monitoring solution and integrates seamlessly with existing monitoring tools.
- New
- Changed
- Enhanced GCP proxy checks to include more checks and added customization to add or remove checks from the list.
- Used 'Available memory' in the calculation of the metric check 'os.linux.check-free-physical-memory'
- Fixed
- PRB1854213 - Even though the "Warning" threshold is disabled for a check such as "os.windows.check-system-disk," events are created with a critical threshold despite the threshold not being reached.
- PRB1841263 - [Security Bug] Vulnerable Library golang.org/x/crypto v0.26.0.
- PRB1809845 - Check-windows-service returns Warning for a stopped service but check description states it should return Critical.
- PRB1895643 - 'os.windows.check-event-log-details' check cannot be executed on Windows 2012 / Windows 2012 R2 machines.
- PRB1884616 - When client receives events from Metric Intelligence regarding process memory and process cpu usage but it does not contain info on which process it is.
- PRB1854616 - ACC "os.windows.check-event-log-details" check definition isn't working as expected.
- PRB1868772 - The "Metrics by selected CI filter" is not applied to all metrics on the AIOps Dashboard's Monitoring Technology Dashboard for Windows.
- PRB1862490 - os.windows.metrics-system-disk-ml check for disk.AvgDiskSec/Read does not produce metric registration events.
- PRB1880781 - Certain apps for which Publisher not getting picked up; common trait is that they are installed from Appstore.
- PRB1953044 - ITOM Agent unable to find running process using os.windows.check-windows-process check.
- PRB1910652 - Agents do not honor timeout on background checks, background checks timeout should be 0 to run without timeout.
- Removed
- Known Issues
- PRB1962038 - AWS Metrics Monitoring assigning the wrong sys_id to an event for cloud load balancers and creating binding issues
Agent Client Collector Monitoring requires the following plugins:
- Event Management (installed automatically)
- Metricbase: Request Metricbase (Clotho DB) via HI, as described in KB0816088