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
[APM] Add time range to event metadata API #167132
[APM] Add time range to event metadata API #167132
Conversation
Pinging @elastic/apm-ui (Team:APM) |
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
3045014
to
8138fb2
Compare
8138fb2
to
be998ab
Compare
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: |
// @ts-expect-error | ||
id: doc[processorEvent].id as string, | ||
timestamp: doc['@timestamp'], | ||
}; | ||
} | ||
|
||
registry.when('Event metadata', { config: 'basic', archives: ['apm_8.0.0'] }, () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: We will have to start adhering to the new API guidelines, which Dario is creating where if someone works on an API test which use Archives, then we should migrate it to Synthtrace or Index using ES. This way we will soon get rid of all Archives without spending dedicate time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a good point. I'll convert this asap
Closes #166424