Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Harmonize Self-Monitoring Buffer Fullness Alerts #1772

Open
skhalash opened this issue Jan 20, 2025 · 0 comments
Open

Harmonize Self-Monitoring Buffer Fullness Alerts #1772

skhalash opened this issue Jan 20, 2025 · 0 comments
Labels
area/logs LogPipeline area/metrics MetricPipeline area/traces TracePipeline

Comments

@skhalash
Copy link
Collaborator

skhalash commented Jan 20, 2025 •
edited
Loading

Description

The self-monitoring buffering alerts are inconsistent between OpenTelemetry (OTel) Pipelines and LogPipelines:

OTel Pipelines

Alert Name: QueueAlmostFull
Trigger: Queue size/capacity > 80%
Maps to: BufferFillingUp reason

LogPipelines

Two alerts:
BufferInUse - Trigger: Buffer > 30% full → Maps to BufferFillingUp reason
BufferFull - Trigger: Buffer > 90% full (is this even used?)

Acceptance Criteria

Investigate:

  1. Why do LogPipelines have two separate grades of alerts?
  2. Why are the thresholds different between OTel Pipelines and LogPipelines?
  3. Is the BufferFull alert in LogPipelines used or redundant?

Unify OTel/Log Pipeline alerts.
@skhalash skhalash added area/logs LogPipeline area/metrics MetricPipeline area/traces TracePipeline labels Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/logs LogPipeline area/metrics MetricPipeline area/traces TracePipeline
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@skhalash