docs: Enhance docs around metrics #10767
Conversation
Signed-off-by: Tim Collins <tim@thecollins.team>
Signed-off-by: Tim Collins <tim@thecollins.team>
Signed-off-by: Tim Collins <tim@thecollins.team>
Signed-off-by: Tim Collins <tim@thecollins.team>
Signed-off-by: Tim Collins <tim@thecollins.team>
Signed-off-by: Tim Collins <tim@thecollins.team>
|
It took me the afternoon to solve this metric collection issue when running in HA. +1 for this documentation to be updated, especially the headless configuration of the service. Honestly, the fact that the metrics server is starting / running only on the master instance of the workflow controller is really not great. The headless service does the job to avoid to loose some metrics, but it generate tons of error message since the scraper have Another question i have is: what happens if the master instance fall ? Do you loose all the metrics (especially the accumulated ones) or are the metrics replicated across instances, just the server not running on all ? |
Signed-off-by: Tim Collins <tim@thecollins.team> Co-authored-by: Alex Collins <alexec@users.noreply.github.com> Signed-off-by: Elifarley <elifarley@gmail.com>
Signed-off-by: Tim Collins <tim@thecollins.team> Co-authored-by: Alex Collins <alexec@users.noreply.github.com>
The docs didn't explain the basics of the controller metrics endpoint, how to access it or how to handle multiple controllers. Adding this to the docs should reduce questions asked on the topic in Slack.