-
Notifications
You must be signed in to change notification settings - Fork 25.6k
plugin(apm-data): amend logs-apm component template #115778
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
Conversation
Restore standard mode after LogsDB took precedence. Related: #114501
x-pack/plugin/apm-data/src/main/resources/component-templates/logs-apm@settings.yaml
Outdated
Show resolved
Hide resolved
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.
🎉
|
What's the right labels sorcery here? |
|
Pinging @elastic/es-data-management (Team:Data Management) |
|
@inge4pres Do we need to backport this? Seems to only affect serverless so not needed I think but maybe we should backport. |
@lahsivjar do you know which labels need to be added for the backport? |
Restore standard mode after LogsDB took precedence. Related: elastic#114501 (cherry picked from commit 2b1dc5a)
Restore standard mode after LogsDB took precedence. Related: elastic#114501
Restore standard mode after LogsDB took precedence. Related: elastic#114501
Restore standard mode after LogsDB took precedence. Related: #114501
gradle check? 🚫