Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Identify health check to run in the Resource Health BB #104

Closed
kalxas opened this issue Dec 13, 2024 · 3 comments
Closed

Identify health check to run in the Resource Health BB #104

kalxas opened this issue Dec 13, 2024 · 3 comments
Assignees
Labels
R17 Setup monitoring for compliance with the to be agreed SLA

Comments

@kalxas
Copy link
Member

kalxas commented 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.

@kalxas kalxas added this to the Q3 - Release 2.0 Beta2 milestone Dec 13, 2024
@kalxas
Copy link
Member Author

kalxas commented Dec 13, 2024

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
Copy link
Member Author

kalxas commented Dec 13, 2024

eoAPI already has provided some feedback based on this data access bb discussion:
EOEPCA/data-access#106 (comment)

@kalxas kalxas self-assigned this Dec 13, 2024
@kalxas 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
@kalxas
Copy link
Member Author

kalxas commented Dec 18, 2024

Feedback provided in EOEPCA/data-access#106 (comment)

@kalxas kalxas closed this as completed Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
R17 Setup monitoring for compliance with the to be agreed SLA
Projects
None yet
Development

No branches or pull requests

1 participant