https://github.com/whoabhisheksah/prom-spike

Analysing the Prometheus and Alert manager stack with CPU Load Alert test
https://github.com/whoabhisheksah/prom-spike

Last synced: 3 months ago
JSON representation

Analysing the Prometheus and Alert manager stack with CPU Load Alert test

• Host: GitHub
• URL: https://github.com/whoabhisheksah/prom-spike
• Owner: whoAbhishekSah
• Created: 2020-12-30T06:11:35.000Z (over 4 years ago)
• Default Branch: main
• Last Pushed: 2020-12-30T07:48:29.000Z (over 4 years ago)
• Last Synced: 2025-01-21T15:28:31.800Z (4 months ago)
• Size: 308 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# prom-spike

Analysing the Prometheus and Alert manager stack with CPU Load Alert test

Prometheus server scapes data from node_exporters running in background.

Example run on 8081 port:

- `./node_exporter --web.listen-address 127.0.0.1:8081`



Run Promteheus with config file:

Example run on given configuration file: `./prometheus --config.file=prometheus.yml`

Promtehus scrapes metrics from the `node_exporter` and you can view it in the built in expression browser or set up grafana on top this.

Obviously, Grafana is the popluar choice here.

![CPU Idle Graph](graph.png)

Alert rules can be defined with prometheus and put in yml files and referenced in config file. (see prometheus config file) and viewed on alerts tab.

Prometheus UI Alert Tab : Default - http://localhost:9090/alerts



The alerts are sent to Alertmanager. The receivers are controllerd via `alertmanager.yml` configuration file.

Example run : `/alertmanager --config.file=alertmanager.yml`