SAMZA-2788: Add new metric to emit 1 when containers are processing #1678
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This allows dashboards to calculate how many containers are running / not running based on this metric.
The containerRunning metric is set by the callback function
sborya
approved these changes
Jul 27, 2023
|
Please add a comment to the code (similar to one in the PR description). |
|
@sborya added the comment. Can you help approve and merge it? |
|
Done |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
LISAMZA-31001
Symptom: The "Container Not Running" metric is broken when container level metrics is enabled.
Fix: Adding a new gauge metric to report 1 whenever a container is processing. "Container Not Running" can be calculated by total_container_count - sum(container_running)