feat: Update Missing AWS Elasticsearch Cluster Handling #1817
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Relevant information
Description:
This PR changes the handling of AWS Elasticsearch clusters when no match is found during a lookup. Previously, no action was taken (NO_OP). Now, an uninstrumented AWS Elasticsearch cluster will be created.
Key Changes:
Action on Miss: Changed from
NO_OPtoCREATE_UNINSTRUMENTED.Entity Type: Creates an uninstrumented
AWSELASTICSEARCHCLUSTER.Implications:
Ensures an entity is always present after a lookup.
May result in uninstrumented entities that are not fully monitored.
Checklist
identifierwill be unique and valid.