Closed itsderek23 closed 6 years ago
And using Firefox 59.0.2 (64-bit), if I try to click the drop-down for the timeframe's endpoint list, the list dismisses. This doesn't happen on Chrome.
Node CPU usage % doesn't appear to change Apdex - goes to zero
I haven't been able to reproduce this.
When I change the timeframe (either a longer timeframe, like 3 hours, or to a prior day):
The node metrics at the bottom of the page:
...do change. Same with Apdex.
To confirm, these are NOT changing for you @zdrummond ?
The timeframe control works.
The highlight a time window in that time frame does not.
From: Derek Haynes notifications@github.com Sent: Tuesday, May 1, 2018 4:39:19 PM To: scoutapp/roadmap Cc: Zachary Drummond; Mention Subject: Re: [scoutapp/roadmap] Time window quirks with node CPU usage and Apdex (#55)
Node CPU usage % doesn't appear to change Apdex - goes to zero
I haven't been able to reproduce this.
When I change the timeframe (either a longer timeframe, like 3 hours, or to a prior day):
[image]https://user-images.githubusercontent.com/7880/39498634-7230506a-4d66-11e8-80d7-0504d982ccf3.png
The node metrics at the bottom of the page:
[image]https://user-images.githubusercontent.com/7880/39498641-81834248-4d66-11e8-8c6c-72e18ddd31e2.png
...do change. Same with Apdex.
To confirm, these are NOT changing for you @zdrummondhttps://github.com/zdrummond ?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/scoutapp/roadmap/issues/55#issuecomment-385821853, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABjVh-hiCfl0-yhrmAXtlecuGUxr2bp8ks5tuPIngaJpZM4TtUet.
Ah yes - I'm able to reproduce. Thanks @zdrummond!
And using Firefox 59.0.2 (64-bit), if I try to click the drop-down for the timeframe's endpoint list, the list dismisses. This doesn't happen on Chrome.
Reproduced:
And using Firefox 59.0.2 (64-bit), if I try to click the drop-down for the timeframe's endpoint list, the list dismisses. This doesn't happen on Chrome.
I turned this into a separate issue - #57 - as it is an unrelated bug.
Node CPU usage % doesn't appear to change
This will now change, but it does require a page refresh as we aren't yet updating the page as part of the zoom interaction. We wanted to get this in place as the zoom interaction update is more involved.
You can verify if the zoom timeframe is being used:
Apdex - goes to zero
Fixed.
Thanks for reporting @zdrummond!
@zdrummond reports two issues when applying a zoom timeframe: