-
Notifications
You must be signed in to change notification settings - Fork 207
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
[DO NOT MERGE] Application Signals GA Tracking #1133
Conversation
d000725
to
94b1f89
Compare
94b1f89
to
6b24d0c
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1133 +/- ##
==========================================
+ Coverage 57.58% 65.43% +7.84%
==========================================
Files 370 357 -13
Lines 17548 18819 +1271
==========================================
+ Hits 10105 12314 +2209
+ Misses 6848 5901 -947
- Partials 595 604 +9 ☔ View full report in Codecov by Sentry. |
plugins/processors/awsappsignals/internal/attributes/attributes.go
Outdated
Show resolved
Hide resolved
plugins/processors/awsappsignals/internal/attributes/attributes.go
Outdated
Show resolved
Hide resolved
plugins/processors/awsappsignals/internal/attributes/attributes.go
Outdated
Show resolved
Hide resolved
plugins/processors/awsappsignals/internal/resolver/attributesresolver.go
Outdated
Show resolved
Hide resolved
72dd500
to
567fe5c
Compare
plugins/processors/awsapplicationsignals/internal/normalizer/attributesnormalizer.go
Outdated
Show resolved
Hide resolved
plugins/processors/awsapplicationsignals/internal/normalizer/attributesnormalizer.go
Show resolved
Hide resolved
plugins/processors/awsapplicationsignals/internal/resolver/attributesresolver.go
Show resolved
Hide resolved
a2a14b9
to
349ce06
Compare
plugins/processors/awsapplicationsignals/internal/cardinalitycontrol/metrics_limiter_test.go
Outdated
Show resolved
Hide resolved
plugins/processors/awsapplicationsignals/internal/normalizer/attributesnormalizer.go
Show resolved
Hide resolved
plugins/processors/awsapplicationsignals/internal/normalizer/attributesnormalizer.go
Outdated
Show resolved
Hide resolved
plugins/processors/awsapplicationsignals/internal/normalizer/attributesnormalizer.go
Outdated
Show resolved
Hide resolved
plugins/processors/awsapplicationsignals/internal/normalizer/attributesnormalizer.go
Show resolved
Hide resolved
} | ||
} | ||
} | ||
if _, ok := attributes.Get(attr.AWSLocalEnvironment); !ok { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: This could be in the block above.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The check is intentionally done outside the previous block to set a default environment wherever the default environment is not set.
plugins/processors/awsapplicationsignals/internal/resolver/attributesresolver.go
Outdated
Show resolved
Hide resolved
plugins/processors/awsapplicationsignals/internal/resolver/attributesresolver_test.go
Outdated
Show resolved
Hide resolved
case config.ModeEC2, config.ModeECS: | ||
return appSignalsConfigGeneric | ||
default: | ||
return appSignalsConfigGeneric |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the difference between these? Do we need to have the config.ModeEC2
, config.ModeECS
checks?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For ECS, it's for putting a placeholder so that we don't miss anything we adding full support for the platform.
@@ -10,6 +10,10 @@ const ( | |||
ModeWithIRSA = "withIRSA" | |||
) | |||
|
|||
const ( | |||
ModeECS = "ECS" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If this is only going to be used in the EMF translator, then keep it there. Want to make sure we don't accidentally set the translator context to ECS since that would break a lot of things.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's used in EMF and applicationsignals translator.
33c86c3
to
4ecf735
Compare
This reverts commit 622dc67.
4ecf735
to
9ee1908
Compare
c6a601e
to
fe56259
Compare
Closed in favor of #1151 |
Please DO NOT MERGE this PR.
Description of the issue
Previous, we introduced different metric schema on different platforms. However, this design involves two major defects:
Description of changes
In this PR, we
/aws/application-signals/data
.HostedIn.
withEnvironment
.K8s.RemoteNamespace
toRemoteEnvironment
to make it consistent with localEnvironment
.RemoteResource*
dimensions.In addition, the
replacement
metric rewriting rule is also updated to allow adding new predefined Application Signals dimensions to the existing metric.This PR needs to work together with other PRs:
License
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Tests
Describe what tests you have done.
Requirements
Before commit the code, please do the following steps.
make fmt
andmake fmt-sh
make lint