Draft
Conversation
c668ee5 to
4f6bceb
Compare
|
✨ Fix all issues with BitsAI or with Cursor
|
This file contains hidden or 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
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.
What does this PR do?
Emit a
datadog.kafka_consumer.context_limit_budgetmetric in the Kafka Consumer integration that represents the number of contexts remaining before the context/partition limit is hit. The metric will be negative is the limit is exceeded. It is tagged bykafka_cluster_id.Motivation
We use the Kafka Consumer metrics in various UIs in Data Streams Monitoring. When the context limit is exceeded, the check starts to drop data, which is not at all obvious to users looking at those metrics. I want to display a warning in the UI whenever the user is near or beyond their configured context limit along with instructions on how to raise it.
Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged