You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Resource Health BB is establishing patterns for fetching health checks and trace data (OpenTelemetry) from building blocks.
We need to report any health endpoints to be used for health check.
The text was updated successfully, but these errors were encountered:
We received a more detailed request from @dovydas-an:
Since the upcoming EOEPCA+ release is fast approaching, we (the developers of Resource Health BB) are reaching out in order to obtain necessary information to be able to set up exemplary health checks. At the moment, we are considering a simple health check that would "ping" your BB, receive a response and depending on the response produce a health check outcome. In order to be able to setup such a check, we would need to know:
URL of the endpoint
Expected response code that would correspond to "OK" health check outcome (e.g. 200)
If authentication is needed, authentication credentials and how they should be added to the request (header)
kalxas
added
BR039
Extensible for integration with alternative backends
R17
Setup monitoring for compliance with the to be agreed SLA
and removed
BR039
Extensible for integration with alternative backends
labels
Dec 13, 2024
The Resource Health BB is establishing patterns for fetching health checks and trace data (OpenTelemetry) from building blocks.
We need to report any health endpoints to be used for health check.
The text was updated successfully, but these errors were encountered: