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

[EEM] Discrepancy between throughput metric from service entity definition and apm-server #188769

Closed
kpatticha opened this issue Jul 19, 2024 · 3 comments · Fixed by #189065
Closed
Assignees
Labels
Team:obs-knowledge Observability Experience Knowledge team

Comments

@kpatticha
Copy link
Contributor

Issue

name: 'throughput',
equation: 'A',
metrics: [
{
name: 'A',
aggregation: 'doc_count',
filter: serviceTransactionFilter(),
},
],
},

throughput from data transforms 360tpm while from apm-server is only 3tpm for the same service

Screen.Recording.2024-07-19.at.18.52.14.mov
@botelastic botelastic bot added the needs-team Issues missing a team label label Jul 19, 2024
@kpatticha kpatticha added the Team:obs-knowledge Observability Experience Knowledge team label Jul 24, 2024
@elasticmachine
Copy link
Contributor

Pinging @elastic/obs-knowledge-team (Team:obs-knowledge)

@klacabane
Copy link
Contributor

klacabane commented Jul 24, 2024

From my initial testing against oblt clusters I could find discrepancies but not of that order. The testing was mostly focused on history dataset so I wonder if there could be something fishy happening in the latest dataset, I'll have a look.
@kpatticha if you can reproduce this easily, could you check if the throughput in the related history documents is also much higher ? Do the service.name: only-apm-0 history documents also have ~300tpm ?

@klacabane
Copy link
Contributor

klacabane commented Jul 24, 2024

I think the metric is just wrong, we should instead value_count on transaction.duration.summary

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:obs-knowledge Observability Experience Knowledge team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants