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
[O11y][Apache Spark] Resolve the conflicts in host.ip field #7468
[O11y][Apache Spark] Resolve the conflicts in host.ip field #7468
Conversation
🌐 Coverage report
|
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.
LGTM
@harnish-elastic - Update the description on the reason for adding additional ECS fields and the context for renaming a few ECS fields. |
@muthu-mps Updated the description here. Also regarding renaming of ecs fields, I have just sorted the ecs.yml file in the alphabetical order and not renamed any ecs fields! |
@@ -63,6 +63,100 @@ Restart Spark master. | |||
|
|||
Follow the same set of steps for Spark Worker, Driver and Executor. | |||
|
|||
### Troubleshooting | |||
|
|||
If host.ip is shown conflicted under ``metrics-*`` data view, then this issue can be solved by reindexing the ``Application``, ``Driver``, ``Executor`` and ``Node`` data stream's indices. |
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.
The reindexing step is important for this change, but I am discussing it within team if we need to give this long troubleshooting steps in the README.
cc: @lalit-satapathy
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.
The reindexing step is important for this change, but I am discussing it within team if we need to give this long troubleshooting steps in the README.
Long term, we can explore remove such repetitive sections in the package Readme and capture in a different way?
- external: ecs | ||
name: tags |
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.
any advantage of changing the ordering of this mapping ?
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.
This is one of the best practices to have field names in the alphabetical order for readability.
…into apache_spark-host-ip-conflicts Conflicts: packages/apache_spark/changelog.yml
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.
Looks good!
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.
Looks good!
Package apache_spark - 0.6.2 containing this change is available at https://epr.elastic.co/search?package=apache_spark |
* resolve the conflicts in host.ip field * update pr link in changelog.yml * address review comments * remove re-indexing steps and provided the re-indexing steps link * address review comments
What does this PR do?
Checklist
changelog.yml
file.Related issues