https://github.com/boyvinall/openstack-check-exporter

Prometheus exporter that runs active checks against one/more Openstack systems
https://github.com/boyvinall/openstack-check-exporter

openstack prometheus-exporter

Last synced: 5 days ago
JSON representation

Prometheus exporter that runs active checks against one/more Openstack systems

• Host: GitHub
• URL: https://github.com/boyvinall/openstack-check-exporter
• Owner: boyvinall
• License: mit
• Created: 2023-04-23T07:52:12.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2023-09-08T16:34:35.000Z (about 1 year ago)
• Last Synced: 2024-06-21T19:53:02.172Z (5 months ago)
• Topics: openstack, prometheus-exporter
• Language: Go
• Homepage:
• Size: 88.9 KB
• Stars: 1
• Watchers: 1
• Forks: 0
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.txt

Awesome Lists containing this project

README

        
# openstack-check-exporter

![](docs/wip.jpg)

This exporter runs some active checks against an OpenStack cloud and exposes the results as Prometheus metrics. The checks are inspired by

the (now deprecated) nagios/sensu checks at

[osops-tools-monitoring/monitoring-for-openstack/oschecks](https://github.com/openstack-archive/osops-tools-monitoring/tree/7427ee739296e93f18aed92f7150abf732fd92b3/monitoring-for-openstack/oschecks)

and

[osops-tools-monitoring/nagios-plugins](https://github.com/openstack-archive/osops-tools-monitoring/tree/7427ee739296e93f18aed92f7150abf732fd92b3/nagios-plugins).

By comparison,  does not attempt to create any resources, merely reading from the

API and exposing those details.  It's recommended to run both of these exporters at the same time. There is some overlapping functionality,

though a benefit of the exporter from this repo is that durations are recorded, which can be useful to monitor for performance regressions.

## Notes

* This exporter runs the checks as a background process and then serves up the cached metrics for scraping.  This is contrary to conventions

  with prometheus - but, in this case, has some benefits:

    * It allows multiple prometheus servers to scrape the exporter without resulting in multiple resources being created. Specifically, this

      is important for things like creation of nova instances, which could add unnecessary load to the cloud.  

    * Additionally, the nova instance check ensures that there is not already a VM of the given name running. If the exporter is scraped

      multiple times then this would need to somehow pass the VM name in as a custom scrape query arg - doable, but a bit messy.

## To do

* [ ] CI, unit tests, etc

* [ ] Docs