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

Clarify lack of support for Serverless environments #24499

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

rmartinez809
Copy link
Contributor

This update is to clarify our lack of support for second primary tags in Serverless environments.

Related to ticket: https://datadog.zendesk.com/agent/tickets/1786704

and the following FRs:

What does this PR do? What is the motivation?

please see details above

Merge instructions

  • Please merge after reviewing

Additional notes

This update is to clarify our lack of support for second primary tags in Serverless environments.

Related to ticket: https://datadog.zendesk.com/agent/tickets/1786704

and the following FRs:
* https://datadoghq.atlassian.net/browse/FRAPMS-3726
* https://datadoghq.atlassian.net/browse/FRAPMS-990
@rmartinez809 rmartinez809 requested a review from a team as a code owner August 6, 2024 20:29
@github-actions github-actions bot added the Guide Content impacting a guide label Aug 6, 2024
@@ -80,6 +80,8 @@ Go to the [APM Settings][6] page to define, change, or remove your primary tags.
* Changes may take up to two hours to be reflected in the UI.
* The tracer always adds `resource`, `name`, and `service` tags to spans. Datadog recommends never adding these as host level tags to avoid confusion.
* The second primary tag supports up to 30 unique values. See [APM Data Volume Guidelines][9] for details.
* Adding second primary tags is currently not supported for Serverless environments.
Copy link
Contributor

Choose a reason for hiding this comment

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

What do you think about making this a callout note at the top of the section? It's not really parallel to the other information in these bullet points, and it makes sense to disclose it before the user can even try to go set a second primary tag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Guide Content impacting a guide
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants