Operational Monitoring
Using Prometheus end-point in ZebClient for Grafana monitoring
- A running Prometheus and Grafana server
- 1.Make sure the
telemetrypart of the ZebClient agent is enabled and configured to listen to all IP addresses on the agent node:
telemetry:
prometheus:
addr: 0.0.0.0:9090
- 2.Update the EC2 security groups' inbound rules to allow access to the instance running the ZebClient agent on port 9090.
- 3.Add the public IP address of the ZebClient agent instance to the Prometheus server scrape targets.
Let say, you already have a Prometheus server up and running where the configuration file is
/etc/prometheus/prometheus.yml and the location of the scrap target JSON file is in /etc/prometheus/targetsIn order to add the ZebClient agent as the scrape target, first add the following job into your Prometheus config file, i.e.
prometheus.yml- job_name: 'aws'
scrape_interval: 10s
file_sd_configs:
- files:
- '/etc/prometheus/targets/aws/*.json'
Create the targets directory if is not exist yet:
sudo mkdir -p /etc/prometheus/targets/aws
Then, create a JSON file with the following content and save it as
ZebClient-agent-IP-address.json[
{
"targets": [
"<the ZebClient agent public IP address>:9090"
]
}
]
- 4.Restart Prometheus service
- 5.Verify that the target is available and in the state
UP
- 6.Then, you create a dashboard in Grafana to visualize the metrics.