prometheus.service
file: Here's a brief explanation of the key parts in this prometheus.service
file:User
and Group
specify the Linux user and group under which Prometheus will run.ExecStart
is where you specify the Prometheus binary path, the location of the configuration file (prometheus.yml
), the storage directory, and other settings.web.listen-address
configures Prometheus to listen on all network interfaces on port 9090.web.enable-lifecycle
allows for management of Prometheus through API calls.http://<your-server-ip>:9090
node_exporter.service
file:--collector.logind
with any additional flags as needed.prometheus.yml
file. Here is an example prometheus.yml
configuration for your setup: Make sure to replace <your-jenkins-ip>
and <your-jenkins-port>
with the appropriate values for your Jenkins setup. Check the validity of the configuration file: Reload the Prometheus configuration without restarting: You can access Prometheus targets at: http://<your-prometheus-ip>:9090/targets
http://<your-server-ip>:3000
http://localhost:9090
(assuming Prometheus is running on the same server).Posted Mar 16, 2025
Provisioned EC2, Dockerized Netflix clone, integrated TMDB API, secured with SonarQube & Trivy, automated CI/CD with Jenkins, monitored with Prometheus/Grafana
0
1
Apr 1, 2024 - Apr 3, 2024