[APM] Errors when linking from service map to ML #73755
Assignees
Labels
apm:service-maps
Service Map feature in APM
bug
Fixes for quality problems that affect the customer experience
Team:APM
All issues that need APM UI Team support
v7.9.0
Comments
ogupte
added
7.9.0
bug
|
Pinging @elastic/apm-ui (Team:apm) |
ogupte
added a commit
to ogupte/kibana
that referenced
this issue
Jul 29, 2020
…ges and using correct refreshValue rison types rather than just strings
ogupte
added a commit
that referenced
this issue
Jul 30, 2020
* Closes #73755 by removing the extra uri encoding from time ranges and using correct refreshValue rison types rather than just strings * removes commented out test assertion
kibanamachine
pushed a commit
that referenced
this issue
Jul 30, 2020
* Closes #73755 by removing the extra uri encoding from time ranges and using correct refreshValue rison types rather than just strings * removes commented out test assertion
kibanamachine
pushed a commit
that referenced
this issue
Jul 30, 2020
* Closes #73755 by removing the extra uri encoding from time ranges and using correct refreshValue rison types rather than just strings * removes commented out test assertion
ogupte
added a commit
that referenced
this issue
Jul 30, 2020
* Closes #73755 by removing the extra uri encoding from time ranges and using correct refreshValue rison types rather than just strings * removes commented out test assertion Co-authored-by: Oliver Gupte <[email protected]>
ogupte
added a commit
that referenced
this issue
Jul 30, 2020
* Closes #73755 by removing the extra uri encoding from time ranges and using correct refreshValue rison types rather than just strings * removes commented out test assertion Co-authored-by: Oliver Gupte <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The error
Error: invalid bounds set: [object Object]occurs when clicking a link in service maps to open anomaly detection in ML:This is caused by the time range
fromandtofields not being encoded properly.Also the console show errors when passing refresh interval and paused state:
This is caused by using the incorrect (string) data type for those fields. They should be:
{pause: boolean; value: number}. These errors are also shown when linking to discover from transaction and error pages.The text was updated successfully, but these errors were encountered: