-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Remove agent.hostname field from libbeat #18328
Remove agent.hostname field from libbeat #18328
Conversation
Pinging @elastic/siem (Team:SIEM) |
agent.hostname is not part of ECS so this removes the field. Instead the agent.name field can be used for this purpose and it it part of ECS. This add a migration alias pointing from agent.hostname to agent.name. Closes elastic#16377
8463d27
to
4af663b
Compare
💚 Build SucceededExpand to view the summary
Build stats
Test stats 🧪
Steps errorsExpand to view the steps failures
|
I created #18329 to track removing the old 6.x-to-7.0 migration aliases. |
Pinging @elastic/integrations-services (Team:Services) |
@@ -0,0 +1,17 @@ | |||
# The ECS migration file contains the information about all the Beats fields |
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.
nice!
libbeat/_meta/fields.common.yml
Outdated
type: alias | ||
path: agent.name | ||
migration: true |
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.
I wonder if we want to keep an alias, is this used by any UI?
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.
There is at least one place using agent.hostname
in Kibana. There may be more instances. So I'll remove the migration tag so that the alias always exists (at least until we can confirm all of Kibana is updated in 8.0).
I'll ask the uptime team if they can update 8.0 to use agent.name
.
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.
cc @andrewvc
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.
Thank you for tackling this! PR is looking good to me, just left a question on keeping the alias or not
Remove migration: true from beat.hostname alias. We can add it back after we are sure that Kibana has been updated to use beat.name for 8.0.
run tests |
We are considering removing |
@kaiyan-sheng We are not using |
Thank you!! @simianhacker We will add removing |
What does this PR do?
agent.hostname
is not part of ECS so this removes the field. Instead theagent.name
field can be used for this purpose and it it part of ECS.This add an alias pointing from
agent.hostname
toagent.name
. The aliascan be removed once we confirm all the Kibana apps are migrated to
agent.name
for 8.0.
This will not be part of 7.x.
Why is it important?
From #16377
Checklist
[ ] I have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues
Closes #16377