Skip to content

Update Logstash single pipeline dashboard with batch byte_size metrics for p50 p90 max#18311

Draft
andsel wants to merge 3 commits intoelastic:mainfrom
andsel:feature/update_logstash_pipeline_dashboard_batch_metrics_p50_p90_max
Draft

Update Logstash single pipeline dashboard with batch byte_size metrics for p50 p90 max#18311
andsel wants to merge 3 commits intoelastic:mainfrom
andsel:feature/update_logstash_pipeline_dashboard_batch_metrics_p50_p90_max

Conversation

@andsel
Copy link
Copy Markdown
Contributor

@andsel andsel commented Apr 9, 2026

Proposed commit message

Update the cel script to store p50 p90 and max byte size metrics of the batch for the last minute.
Update the Single Pipeline View to include these new values.

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

  • [ ]

How to test this PR locally

Follow the test plan shaped in #17009

Related issues

Screenshots

Screenshot 2026-04-09 at 14 15 39

@andsel andsel self-assigned this Apr 9, 2026
@andsel andsel added the enhancement New feature or request label Apr 9, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 9, 2026

✅ Vale Linting Results

No issues found on modified lines!


The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

@elastic-vault-github-plugin-prod
Copy link
Copy Markdown

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@elasticmachine
Copy link
Copy Markdown

💚 Build Succeeded

cc @andsel

@andrewkroh andrewkroh added documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. Integration:logstash Logstash dashboard Relates to a Kibana dashboard bug, enhancement, or modification. labels Apr 9, 2026
@robbavey robbavey requested a review from perk April 10, 2026 14:31
@robbavey
Copy link
Copy Markdown
Member

Couple of concerns about presentation:

Screenshot 2026-04-10 at 4 29 00 PM

I'm not sure about having multiple areas, and why p50 and p90 are represented by areas, but max is not. WDYT about only p50 being represented by area, or nothing?

average lifetime is difficult to read on this graph too

@andsel
Copy link
Copy Markdown
Contributor Author

andsel commented Apr 13, 2026

I imagined p50 an p90 as areas because those make immediately visible the where the current and max are respect to the range that should contains the majority of the measures.
I tried to add also max as an area, but the graph became too much cluttered, because max is an upper limit, I think it's fine to be a line.

If we keep all percentiles plus current and average as lines, the graph it's hard to understand, you have to consider 5 lines and understanding the relationship it's not easy.
The areas permit an immediate separation between percentiles and current, average values.
Let me know if you think that we are presenting too much information in a single graph. I think that the idea of the graph is to provide how current and average relates to percentiles in a glipse.

@robbavey
Copy link
Copy Markdown
Member

@perk @jsvd Do you have any thoughts here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dashboard Relates to a Kibana dashboard bug, enhancement, or modification. documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. enhancement New feature or request Integration:logstash Logstash

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update the Elastic integration to present p50 p90 and max batch byte size metrics

4 participants