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

Apdex T value not being acknowledged, instead possible falling back to default Apdex T value (0.5) #59

Open
OscarLopezEns opened this issue Dec 31, 2020 · 0 comments
Labels
bug Something isn't working

Comments

@OscarLopezEns
Copy link

Description

For some reason our deployment of "PageView Map" on our Browser app is not acknowledging the Apdex T value correctly and it would seem instead is just taking the default Apdex T value of "0.5", hence all the geo location points on the map are showing a red critical status (since all durations are way over the default Apdex T value of 0.5), which should not be the case.

Steps to Reproduce

Our Apdex T value:
image
image

Example of all geo points showing a critical status.
image

This Browser app is still running a fairly old version of the Browser agent (1071), so not sure that is the reason. Is there a minimum required Browser agent version required for the correct Apdex T value to be acknowledged?

@OscarLopezEns OscarLopezEns added the bug Something isn't working label Dec 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant