Bump github.com/aws/aws-sdk-go from 1.36.15 to 1.36.19 in /exporter/datadogexporter #1940
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
Codecov Report
@@ Coverage Diff @@
## master #1940 +/- ##
==========================================
+ Coverage 90.19% 90.20% +0.01%
==========================================
Files 385 385
Lines 19063 19063
==========================================
+ Hits 17193 17195 +2
+ Misses 1398 1397 -1
+ Partials 472 471 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
e4d9dbd to
48c9d95
Compare
Bumps [github.com/aws/aws-sdk-go](https://github.com/aws/aws-sdk-go) from 1.36.15 to 1.36.19. - [Release notes](https://github.com/aws/aws-sdk-go/releases) - [Changelog](https://github.com/aws/aws-sdk-go/blob/master/CHANGELOG.md) - [Commits](aws/aws-sdk-go@v1.36.15...v1.36.19) Signed-off-by: dependabot[bot] <support@github.com>
48c9d95 to
07477bf
Compare
bogdandrutu
approved these changes
Jan 4, 2021
dyladan
referenced
this pull request
in dynatrace-oss-contrib/opentelemetry-collector-contrib
Jan 29, 2021
This is the first of two PRs to add support for filtering `pdata.Metric`s by arbitrary [expr](https://github.com/antonmedv/expr) expressions. The capabilities of the existing `filterprocessor`, which currently filters just metric _names_ by matching against regexes or strings, will be expanded to allow for filtering `pdata.Metric` _structs_ based on expressions such as `MetricName == "foo" && Label("mylabel") == "bar"`. This change adds support for `match_type: expr` while maintaining backward compatibility with existing filterprocessor config yamls. Because the expr filter will be the first one that checks for matches against entire `pdata.Metric`s, rather than just their names, some minor changes are required to the structure of the configs that the filterprocessor uses. For reference, a current filterprocessor config look might like the following: ``` processors: filter/1: metrics: exclude: match_type: regexp metric_names: - prefix/.* ``` After the second PR, the intent is for another possible config to be: ``` processors: filter/1: metrics: exclude: match_type: expr expressions: - "MetricName == 'foo' && Label('mylabel') == 'bar'" ``` This PR just adds support for `match_type: expr`.
ljmsc
referenced
this pull request
in ljmsc/opentelemetry-collector-contrib
Feb 21, 2022
Co-authored-by: Anthony Mirabella <a9@aneurysm9.com>
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.
Bumps github.com/aws/aws-sdk-go from 1.36.15 to 1.36.19.
Release notes
Sourced from github.com/aws/aws-sdk-go's releases.
Changelog
Sourced from github.com/aws/aws-sdk-go's changelog.
Commits
a3494c9Release v1.36.19 (2020-12-31)1c785a4Release v1.36.18 (2020-12-30) (#3719)656f43dRelease v1.36.17 (2020-12-29) (#3716)e79c2ebRelease v1.36.16 (2020-12-28) (#3714)8fac01dRelease v1.36.15 (2020-12-23) (#3709)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)