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

Pipeline overview showing 0 events emitted rate on recent Last N minutes timepicker selection #23455

Open
ppf2 opened this issue Sep 24, 2018 · 6 comments
Labels
bug Fixes for quality problems that affect the customer experience Feature:Logstash Pipelines Logstash Pipeline UI related Team:Logstash Team:Monitoring Stack Monitoring team

Comments

@ppf2
Copy link
Member

ppf2 commented Sep 24, 2018

Not sure if this has the same underlying cause as #19429.

The issue reported here is the opposite behavior of 19429.

In the pipeline overview screen, it shows all pipelines having 0 e/s emitted rate:

image

But when clicking into a pipeline to look at the "version active now", it does show positive e/s:

image

If we switch the pipeline overview screen to show Last 30 minutes instead of Last 15 minutes, then positive e/s metrics started showing up.

This suggests that looking at a longer time range with larger buckets is the key to allow metrics to show up in the pipeline overview screen. Is this the expected behavior? If so, can we add a mouseover indicator letting the end user know that they will have to increase the time range in order to see e/s, etc..?

@ppf2 ppf2 added the Feature:Logstash Pipelines Logstash Pipeline UI related label Sep 24, 2018
@iShiBin
Copy link

iShiBin commented Sep 30, 2018

I encountered the same issue today. Any solution?

@justinkambic
Copy link
Contributor

@iShiBin if you check the last few sentences, we have discovered that changing the bucket size from 15 minutes to 30 minutes does cause e/s metrics to start appearing. More work will be needed to figure out why this bug takes place, but that is the workaround we're employing at the moment. cc @ppf2

@iShiBin
Copy link

iShiBin commented Oct 1, 2018

I figured it out later on. Thanks for the feedback. Have a good day.

@fdartayre
Copy link

Hey @justinkambic, do you have any update on this bug?

@justinkambic
Copy link
Contributor

Hi - I am generally not working on Logstash issues as much these days as I have been assigned to a different team, which has obviously reduced my bandwidth. As far as I know there hasn't been much movement here, maybe @elastic/logstash or @elastic/stack-monitoring has a better update?

@ycombinator ycombinator added Team:Monitoring Stack Monitoring team bug Fixes for quality problems that affect the customer experience labels May 2, 2019
@cachedout
Copy link
Contributor

We (@elastic/stack-monitoring) will take this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Logstash Pipelines Logstash Pipeline UI related Team:Logstash Team:Monitoring Stack Monitoring team
Projects
None yet
Development

No branches or pull requests

7 participants