-
Notifications
You must be signed in to change notification settings - Fork 1
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
Feature/component monitoring #118
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the BBMRI case, the monitoring app is not added to the Beam-Proxy apps.
The Monitoring components for both projects are missing a container_name
directive
Sidenote: Please ensure, that your application can deal with a delayed-started beam Proxy. depends_on
is not sufficient, as the container might be running but the Beam Proxy not yet fully operational.
I made sure that this component is very silent on startup when it is not able to reach the proxy yet. No beam-connect type of endless retrying spamming the logs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, before we merge, we need to communicate these changes in the individual projects
Co-authored-by: Martin Lablans <[email protected]>
This PR adds the bridgehead monitoring component.
It allows Monitoring tools like icinga2 to check running component.