Bug 1956912

Summary:	[RFE] Store API status stats in Prometheus instead of ElasticSearch
Product:	Service Telemetry Framework	Reporter:	Leif Madsen <lmadsen>
Component:	sg-core-container	Assignee:	Paul Leimer <pleimer>
Status:	CLOSED ERRATA	QA Contact:	Leonid Natapov <lnatapov>
Severity:	medium	Docs Contact:
Priority:	urgent
Version:	1.3	CC:	swilber
Target Milestone:	z1	Keywords:	FutureFeature, Triaged
Target Release:	1.3 (STF)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-19 14:16:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1940181

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