Bug: Global Targets need to be handled properly by Checks
y-eight opened this issue · 0 comments
y-eight commented
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
Currently eg. the health check is using the global targets provided by the target manager directly.
Registered global target https://sparrow-b.telekom.de will be used as it is. Every sparrow will provide its health check endpoint at /checks/health. The result is that the endpoint seems unhealthy.
Expected Behavior
The sparrow should use the global targets for its checks correctly. Therefore it should append the check's health endpoint (similar to other checks that are using the global targets).
Eg.: https://sparrow-b.telekom.de/checks/health
Steps To Reproduce
No response
Relevant logs and/or screenshots, environment information, etc.
No response
Who can address the issue?
No response
Anything else?
No response