Bug 1956912 - [RFE] Store API status stats in Prometheus instead of ElasticSearch
Summary: [RFE] Store API status stats in Prometheus instead of ElasticSearch
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Service Telemetry Framework
Classification: Red Hat
Component: sg-core-container
Version: 1.3
Hardware: Unspecified
OS: Unspecified
urgent
medium
Target Milestone: z1
: 1.3 (STF)
Assignee: Paul Leimer
QA Contact: Leonid Natapov
URL:
Whiteboard:
Depends On:
Blocks: 1940181
TreeView+ depends on / blocked
 
Reported: 2021-05-04 16:07 UTC by Leif Madsen
Modified: 2021-07-19 14:16 UTC (History)
1 user (show)

Fixed In Version: sg-core-container-4.0.3-1
Doc Type: Enhancement
Doc Text:
Feature: OSP API health checks in STF 1.3 are now stored in Prometheus. Result: API health checks are no longer stored in ElasticSearch. The STF 1.3 dashboards have been updated to reflect this change.
Clone Of:
Environment:
Last Closed: 2021-07-19 14:16:01 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github infrawatch sg-core pull 60 0 None open Separate plugin for handling sensubility events. Store events as metrics in Prometheus rather than Elasticsearch 2021-07-05 14:56:28 UTC
Red Hat Product Errata RHBA-2021:2771 0 None None None 2021-07-19 14:16:23 UTC

Description Leif Madsen 2021-05-04 16:07:39 UTC
Description of problem:

Information about API status in OSP is being written to ElasticSearch for storage in an STF domain. As this information is more a metric as a boolean, it would be more appropriate to expose this data as a scrape point for Prometheus to store.


Version-Release number of selected component (if applicable):

STF 1.2 and STF 1.3. Request is only to change this for STF 1.3.


How reproducible:

Always.

Comment 1 Paul Leimer 2021-05-04 16:20:13 UTC
This will require a dashboard update as well

Comment 10 errata-xmlrpc 2021-07-19 14:16:01 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Release of components for Service Telemetry Framework v1.3.1), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:2771


Note You need to log in before you can comment on or make changes to this bug.