
- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 09-09-2021 05:46 AM
Hello Experts,
The article gives brief knowledge on Agent Client Collector (ACC) which is built on a Sensu framework that enables you to adapt and extend monitoring checks. Monitoring collects data on your infrastructure. Checks and policies run on the agent’s client to retrieve the relevant data, which is transformed into events or metrics. Events and metrics are sent from the agent to your ServiceNow instance through a pre-installed MID Server and are stored in the relevant database.
Agent Client Collector for Visibility (ACC-V)
Agent Client Collector for Monitoring(ACC-M)
Prerequisites:
Verify supported OS from list of supported OS versions
- Configure resource limits for the agent in the /usr/lib/systemd/system/acc.service file:
-
- CPUShares=128
- CPUQuota=10%
- MemoryLimit=192M
- BlockIOWeight=10
- LimitNICE=+15
- Ensure that you have configured the Agent Client Collector web server
- If possible, configure yum as it helps to install missing packages or dependencies, here I took an example for CentOS.
- Ensure that you have the openssl and dgst (for RHEL/Centos/SUSE installation)
- Following plugins needs to be installed on the instance (System Definitions > Plugins)
- Agent Client Collector Framework
- Agent Client Collector Monitoring
- Discovery and Service Mapping patterns
- Event Management and Service Mapping Core
- Operational Intelligence - WS Scoped App
- Agent Client Collector Framework
- Discovery [com.snc.discovery] plugin
- Configure the WebSocket server on MID Servers to enable connections from agents to the MID Server. Only one WebSocket server per MID server.
- Configure WebSocket endpoint
Installation:
CentOS:
Download both the installation files for Agent Client Collector to your local machine: from Agent Client Collector --> Deployment --> Agent Downloads
[root@new]#wget https://install.service-now.com/glide/distribution/builds/package/app-signed/agent-client-collector-2.5.0-el7-x86_64.rpm
[root@new]#wget https://install.service-now.com/glide/distribution/builds/package/app-signed/agent-client-collector-2.5.0-el7-x86_64-rpm-rpm.zip
[root@new]# unzip agent-client-collector-2.5.0-el7-x86_64-rpm-rpm.zip
[root@new]# openssl dgst -sha256 -verify ServiceNow_Digicert_DGST.pem -signature agent-client-collector-2.5.0-el7-x86_64.bin agent-client-collector-2.5.0-el7-x86_64.rpm
Verified OK
[root@new]# rpm -vi agent-client-collector-2.5.0-el7-x86_64.rpm
Preparing packages...
agent-client-collector-1:2.5.0-1.el7.x86_64
[root@new]# cp -p /etc/servicenow/agent-client-collector/acc.yml.example /etc/servicenow/agent-client-collector/acc.yml
[root@agent-client-collector]# systemctl enable acc
Created symlink from /etc/systemd/system/network-online.target.wants/acc.service to /usr/lib/systemd/system/acc.service.
[root@new]# systemctl start acc
[root@new]# systemctl status acc
Active: active (running)
Windows:
Before proceeding we will turn off the IE Enhanced Security Configuration
- Navigate to Server Manager > Local Server.
- Turn off IE Enhanced Security Configuration.
- Download the installation files for Agent Client Collector to Windows machine: from Agent Client Collector --> Deployment --> Agent Downloads
- As we know windows is use friendly while installing application, follow the prompts until we get following prompt.
above are the details for MID server which we will be using for the Agent client connector.
Mid Server name/IP, Port, API Key can be copied from the instance.
API Key can be found under, Agent Client Collector --> Deployment --> MID Web Server API Key
Post-installation:
- Click on "Setup Agent Client Collector Listener" from the MID Server form.
- Ensure Websocket Endpoint and MID Web Server is started
Agent Client Collector --> Deployment --> Websocket Endpoint
Agent Client Collector --> Deployment --> MID Web Server
Note: ACC for Monitoring is only the data source of events and metrics, it needs ITOM Health to receive and process these events and metrics
- Once the above configuration is completed. We need to activate the policies plugins.
(Agent Client Collector --> Configuration --> Policies. (Depending on the requirement we can enable the policies)
- Once policies are enabled, we start seeing the events from ACC in All Events (Source as ITOM Agent).
Then the Event rules, Alert Management Rules, Sub-Flows come into the picture.
For me the scripts were not found on CentOS, here are the steps which I followed:
- Downloaded the plugins from Agent Client Collector --> Configuration -- > ACC Plugins. (monitoring-plugin-linux)
- Filename: monitoring-plugin-linux.tar.gz
- Extract and place the scripts ( ps1, rb, sh) depending on the OS under plugins/bin directory on the server where the ACC is installed.
(Content is from ServiceNow and from the personal instance. No copyrights are claimed)
More details:
Thanks,
Raj Esh
- 2,256 Views