Skip to content
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

feat: Upcoming Ec2 keep legacy metadata configuration option details #4508

Merged

Conversation

ismahernandez
Copy link
Contributor

@ismahernandez ismahernandez commented Oct 25, 2021

Update from @zuluecho9: This will go live sometime soon after October 26 and when it does, we want to update the doc w/ the new date.

Hello! Ismael here from the Beyond team. This is some documentation for a soon to be live new option in the EC2 Integration configuration panel. Feedback/changes welcome if you have them.
Talk to me in slack @ ihernandez

Documenting an upcoming configuration option for EC2 integrations: the Keep legacy metadata format option.
adding examples and attribute formats
@CLAassistant
Copy link

CLAassistant commented Oct 25, 2021

CLA assistant check
All committers have signed the CLA.

@github-actions github-actions bot added this to Hero to triage in Docs PRs and Issues Oct 25, 2021
@github-actions
Copy link

Hi @ismahernandez 👋
Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days.

@gatsby-cloud
Copy link

gatsby-cloud bot commented Oct 25, 2021

Gatsby Cloud Build Report

docs-website-develop

🎉 Your build was successful! See the Deploy preview here.

Build Details

View the build logs here.

🕐 Build time: 27m

@zuluecho9 zuluecho9 self-assigned this Oct 25, 2021
@zuluecho9 zuluecho9 self-requested a review October 25, 2021 16:33
@zuluecho9 zuluecho9 moved this from Hero to triage to In progress/being reviewed (by Hero or any TW) in Docs PRs and Issues Oct 25, 2021
@zuluecho9
Copy link
Contributor

zuluecho9 commented Oct 25, 2021

Some details from SME:

To learn more about this, search in atlassian for 'Duplicated EC2 metadata and tags' and you'll find a description of the problem and fix.

Summary of issue:

"We are gonna be adding a toggle button under infrastructure - aws - ec2 - configure. It is gonna be called keep legacy metadata format, should be live in staging at least for the frontend and we are planning to release this tomorrow or the day after. We are planning on keeping this for the time being because some customers use these legacy tag and attribute names and don't want to break them. It is possible this setting could be removed in the future and instead use aliases through shimming. Let me explain a lil better what they are.
We've had for a long time duplicate data under the ec2 metrics for the computesample data type. So ec2 custom tags and some attributes were present with thr same value under different keys.

These consume bandwidth, the same value duplicated 3 times with different names, and we have decided to remove them. For current customers they will be keeping these as is but they will be able to turn that off and only keep the values that are not legacy. New integrations will be having that value off, even for old customers."

@zuluecho9 zuluecho9 added content requests related to docs site content from_internal Identifies issues/PRs from Relics (except writers) labels Oct 25, 2021
zuluecho9
zuluecho9 previously approved these changes Oct 26, 2021
Copy link
Contributor

@x8a x8a left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👏🏻

@x8a x8a moved this from In progress/being reviewed (by Hero or any TW) to Waiting on TW to merge in Docs PRs and Issues Oct 27, 2021
@x8a x8a merged commit e8c3204 into newrelic:develop Oct 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content requests related to docs site content from_internal Identifies issues/PRs from Relics (except writers)
Projects
Docs PRs and Issues
Waiting on TW to merge
Development

Successfully merging this pull request may close these issues.

None yet

4 participants