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.

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

Report per input metrics for filtered events #42761

Open
AndersonQ opened this issue Feb 19, 2025 · 1 comment · May be fixed by #42618
Open

Report per input metrics for filtered events #42761

AndersonQ opened this issue Feb 19, 2025 · 1 comment · May be fixed by #42618
Labels
needs_team Indicates that the issue/PR needs a Team:* label

Comments

@AndersonQ
Copy link
Member

AndersonQ commented Feb 19, 2025

Describe the enhancement:

The input metrics should contain data about the number of events filtered by each input. This would help narrow down the source of problems to a particular input (and hence a particular integration data stream in the case of Elastic Agent).

Describe a specific use case for the enhancement or feature:

  • Diagnostic dumps from Elastic Agent will contain filtered metrics that are specific to an integration data stream (via input_metrics.json).
  • Input metric dashboards in the Elastic Agent fleet integration can display dropped/filtered charts, providing a visual representation of the issue.
  • Standalone beat users can access detailed information about which input is causing drops through the HTTP monitoring API.
@AndersonQ AndersonQ changed the title Report per input metrics for dropped events Report per input metrics for filtered events Feb 19, 2025
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Feb 19, 2025
@botelastic
Copy link

botelastic bot commented Feb 19, 2025

This issue doesn't have a Team:<team> label.

@AndersonQ AndersonQ linked a pull request Feb 19, 2025 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant