-
Notifications
You must be signed in to change notification settings - Fork 457
feat(aws): enhance service representation for serverless #14055
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
Merged
Merged
Changes from 8 commits
Commits
Show all changes
20 commits
Select commit
Hold shift + click to select a range
b70cdca
add peer.hostname tags
zarirhamza dceba8e
remove hostname
zarirhamza f506423
apply peer.service in aws.lambda
zarirhamza 2eca6e0
Merge branch 'main' into zarir/SSR-tracer
zarirhamza c02aaf4
add release note
zarirhamza 1ca706c
linter
zarirhamza a6b1f2c
add tests
zarirhamza 009bc1d
Merge branch 'main' into zarir/SSR-tracer
zarirhamza b70b7ed
add feature note
zarirhamza 41b77bf
Merge branch 'main' into zarir/SSR-tracer
zarirhamza c559da4
Merge branch 'main' into zarir/SSR-tracer
zarirhamza d3a3e77
simplify base_service changes
zarirhamza c51fda4
update base_service tag in serverless environments
zarirhamza e7188d2
focus changes only on aws
zarirhamza 53c52d1
linter
zarirhamza db0f830
Merge branch 'main' into zarir/SSR-tracer
zarirhamza fbac06e
cleanup fixes
zarirhamza 4e0ef09
improve SLO
zarirhamza 2ae4f2f
Merge branch 'main' into zarir/SSR-tracer
zarirhamza b7090b8
linter
zarirhamza File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
65 changes: 65 additions & 0 deletions
65
releasenotes/notes/fix-serverless-service-representation-b1f81fe0553a7a45.yaml
This file contains hidden or 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,65 @@ | ||
--- | ||
#instructions: | ||
# The style guide below provides explanations, instructions, and templates to write your own release note. | ||
# Once finished, all irrelevant sections (including this instruction section) should be removed, | ||
# and the release note should be committed with the rest of the changes. | ||
# | ||
# The main goal of a release note is to provide a brief overview of a change and provide actionable steps to the user. | ||
# The release note should clearly communicate what the change is, why the change was made, and how a user can migrate their code. | ||
# | ||
# The release note should also clearly distinguish between announcements and user instructions. Use: | ||
# * Past tense for previous/existing behavior (ex: ``resulted, caused, failed``) | ||
# * Third person present tense for the change itself (ex: ``adds, fixes, upgrades``) | ||
# * Active present infinitive for user instructions (ex: ``set, use, add``) | ||
# | ||
# Release notes should: | ||
# * Use plain language | ||
# * Be concise | ||
# * Include actionable steps with the necessary code changes | ||
# * Include relevant links (bug issues, upstream issues or release notes, documentation pages) | ||
# * Use full sentences with sentence-casing and punctuation. | ||
# * Before using Datadog specific acronyms/terminology, a release note must first introduce them with a definition. | ||
# | ||
# Release notes should not: | ||
# * Be vague. Example: ``fixes an issue in tracing``. | ||
# * Use overly technical language | ||
# * Use dynamic links (``stable/latest/1.x`` URLs). Instead, use static links (specific version, commit hash) whenever possible so that they don't break in the future. | ||
prelude: > | ||
Usually in tandem with a new feature or major change, meant to provide context or background for a major change. | ||
No specific format other than a required scope is provided and the author is requested to use their best judgment. | ||
Format: <scope>: <add_prelude_and_context_here>. | ||
features: | ||
zarirhamza marked this conversation as resolved.
Show resolved
Hide resolved
|
||
- | | ||
For new features such as a new integration or component. Use present tense with the following format: | ||
Format: <scope>: This introduces <new_feature_or_component>. | ||
issues: | ||
- | | ||
For known issues. Use present tense with the following format: | ||
Format: <scope>: There is a known <symptom_of_issue> issue with <affected_code>. | ||
<provide_actionable_workaround_here>. | ||
upgrade: | ||
- | | ||
For enhanced functionality or if package dependencies are upgraded. If applicable, include instructions | ||
for how a user can migrate their code. | ||
Use present tense with the following formats, respectively for enhancements or removals: | ||
Format: <scope>: This upgrades <present_tense_explanation>. With this upgrade, you can <actionable_step_for_user>. | ||
- | | ||
Format: <scope>: <affected_code> is now removed. As an alternative to <affected_code>, you can use <alternative> instead. | ||
deprecations: | ||
- | | ||
Warning of a component or member of the public API being removed in the future. | ||
Use present tense for when deprecation actually happens and future tense for when removal is planned to happen. | ||
Include deprecation/removal timeline, as well as workarounds and alternatives in the following format: | ||
Format: <scope>: <affected_code> is deprecated and will be removed in <version_to_be_removed>. | ||
As an alternative to <affected_code>, you can use <alternative> instead. | ||
fixes: | ||
- | | ||
For reporting bug fixes. | ||
Use past tense for the problem and present tense for the fix and solution in the following format: | ||
Format: <scope>: This fix resolves an issue where <ABC_bug> caused <XYZ_situation>. | ||
other: | ||
- | | ||
For any change which does not fall into any of the above categories. Since changes falling into this category are | ||
likely rare and not very similar to each other, no specific format other than a required scope is provided. | ||
The author is requested to use their best judgment to ensure a quality release note. | ||
Format: <scope>: <add_release_note_here>. |
This file contains hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.