Monitor API calls response time

Bug #1855905 reported by Giuseppe Petralia
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Prometheus Openstack Exporter Charm
Triaged
Wishlist
Unassigned
charm-openstack-service-checks
Won't Fix
Wishlist
Unassigned

Bug Description

To improve the OpenStack monitoring,
openstack-service-checks should implement a mechanism to monitor API calls response time.

An alert should be triggered if a response time increases of a certain percentage compared with historical response times collected by the charm.

Thresholds for warning and critical alerts should be configurable.

Revision history for this message
Xav Paice (xavpaice) wrote :

This could be extraordinarily complex to implement given different API calls have different response times, and that can vary depending on the number of results delivered. Possibly a simple resource show, for each API, would be enough. It would be great to have that put into prometheus-openstack-exporter rather than Nagios, so that we can graph the changes over time and potentially alert if the response time increases dramatically quickly.

Changed in charm-openstack-service-checks:
status: New → Triaged
importance: Undecided → Wishlist
Changed in charm-prometheus-openstack-exporter:
status: New → Triaged
importance: Undecided → Wishlist
Revision history for this message
Eric Chen (eric-chen) wrote :

This charm is no longer being actively maintained. Please consider using the new Canonical Observability Stack instead.
(https://charmhub.io/topics/canonical-observability-stack)
I will close this feature request

Changed in charm-openstack-service-checks:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.