Cherry-pick #22941 to 7.x: Add clusterName, taskName, cloud.region and dashboard to aws fargate #23026
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-pick of PR #22941 to 7.x branch. Original message:
What does this PR do?
This PR is to add extra fields for cluster name, task name, cloud region and an identifier for AWS fargate.
Why is it important?
When creating AWS Fargate tasks with the same container/container name, Kibana dashboard get confused and only displaying part of the data. I would like to introduce an
awsfargate.identifier
=containerName
+ "/" +containerID
to make sure we can distinguish containers from different task or cluster.Checklist
I have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Screenshot