-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[DOCS-13183] Update buffer metrics for 2.13 #34139
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
[DOCS-13183] Update buffer metrics for 2.13 #34139
Conversation
Jansen-w
left a comment
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.
I think I missed the pipelines.source_buffer_utilization_mean and pipelines.transform_buffer_utilization_mean metrics in the slack thread, sorry about that.
These both represent the exponentially weighted moving average (EWMA) of their respective metric
layouts/shortcodes/observability_pipelines/metrics/buffer.en.md
Outdated
Show resolved
Hide resolved
layouts/shortcodes/observability_pipelines/metrics/buffer.en.md
Outdated
Show resolved
Hide resolved
layouts/shortcodes/observability_pipelines/metrics/buffer.en.md
Outdated
Show resolved
Hide resolved
layouts/shortcodes/observability_pipelines/metrics/buffer.en.md
Outdated
Show resolved
Hide resolved
layouts/shortcodes/observability_pipelines/metrics/buffer.en.md
Outdated
Show resolved
Hide resolved
layouts/shortcodes/observability_pipelines/metrics/buffer.en.md
Outdated
Show resolved
Hide resolved
layouts/shortcodes/observability_pipelines/metrics/buffer.en.md
Outdated
Show resolved
Hide resolved
layouts/shortcodes/observability_pipelines/metrics/buffer.en.md
Outdated
Show resolved
Hide resolved
layouts/shortcodes/observability_pipelines/metrics/buffer.en.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Jansen <jansenwenb@gmail.com>
Co-authored-by: Jansen <jansenwenb@gmail.com>
Co-authored-by: Jansen <jansenwenb@gmail.com>
bruceg
left a comment
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.
LGTM
|
|
||
| `pipelines.source_buffer_utilization` | ||
| : The percentage of a source's buffer that is used. | ||
| : Histogram of event count in a source's buffer. Sources ingest events, then write them to this buffer. |
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.
👍🏻
* update doc * small edit * updates * update destinations * Apply suggestions from code review Co-authored-by: Jansen <jansenwenb@gmail.com> * edits * Apply suggestions from code review Co-authored-by: Jansen <jansenwenb@gmail.com> * Apply suggestions from code review * updates * Apply suggestions from code review Co-authored-by: Jansen <jansenwenb@gmail.com> * Apply suggestions from code review * fix link * remove preview box and update links * Apply suggestions from code review Co-authored-by: Bryce Eadie <bryce.eadie@datadoghq.com> * fix link in shortcode * [DOCS-13183] Update buffer metrics for 2.13 (#34139) * update metrics and add new ones * update * Apply suggestions from code review Co-authored-by: Jansen <jansenwenb@gmail.com> * Apply suggestion from @Jansen-w Co-authored-by: Jansen <jansenwenb@gmail.com> * Apply suggestions from code review Co-authored-by: Jansen <jansenwenb@gmail.com> * add metrics --------- Co-authored-by: Jansen <jansenwenb@gmail.com> --------- Co-authored-by: Jansen <jansenwenb@gmail.com> Co-authored-by: Bryce Eadie <bryce.eadie@datadoghq.com>
What does this PR do? What is the motivation?
Update buffer metrics.
Preview: https://docs-staging.datadoghq.com/may/2.13-buffer-metrics/observability_pipelines/monitoring_and_troubleshooting/pipeline_usage_metrics/#buffer-metrics-when-buffering-is-enabled
Merge instructions
Merge readiness:
For Datadog employees:
Your branch name MUST follow the
<name>/<description>convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.If your branch doesn't follow this format, rename it or create a new branch and PR.
[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.
Additional notes