-
Notifications
You must be signed in to change notification settings - Fork 525
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
[v2] adapt application metrics #1355
Milestone
Comments
simitt
added a commit
to simitt/apm-server
that referenced
this issue
Sep 21, 2018
simitt
added a commit
that referenced
this issue
Sep 24, 2018
roncohen
pushed a commit
to roncohen/apm-server
that referenced
this issue
Oct 7, 2018
roncohen
pushed a commit
to roncohen/apm-server
that referenced
this issue
Oct 15, 2018
roncohen
pushed a commit
to roncohen/apm-server
that referenced
this issue
Oct 15, 2018
roncohen
pushed a commit
to roncohen/apm-server
that referenced
this issue
Oct 15, 2018
roncohen
pushed a commit
to roncohen/apm-server
that referenced
this issue
Oct 15, 2018
roncohen
pushed a commit
to roncohen/apm-server
that referenced
this issue
Oct 15, 2018
roncohen
pushed a commit
to roncohen/apm-server
that referenced
this issue
Oct 16, 2018
roncohen
pushed a commit
that referenced
this issue
Oct 16, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In
v2
error responses are handled differently than inv1
.We have to adapt the collected metrics accordingly and ensure the semantics don't change and/or metrics are shown correctly in the monitoring tab.
see https://github.com/elastic/apm-server/blob/master/beater/handlers.go#L87
The text was updated successfully, but these errors were encountered: