-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[mdatagen] Add ability to specify additional warnings in metadata.yaml #17180
Merged
dmitryax
merged 1 commit into
open-telemetry:main
from
dmitryax:add-warning-ifenablednotset
Dec 22, 2022
Merged
[mdatagen] Add ability to specify additional warnings in metadata.yaml #17180
dmitryax
merged 1 commit into
open-telemetry:main
from
dmitryax:add-warning-ifenablednotset
Dec 22, 2022
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
dmitryax
requested review from
djaglowski,
dashpole,
codeboten and
MovieStoreGuy
as code owners
December 20, 2022 20:24
github-actions
bot
added
cmd/mdatagen
mdatagen command
receiver/activedirectoryds
receiver/aerospike
receiver/apache
receiver/bigip
receiver/chrony
receiver/couchdb
receiver/dockerstats
receiver/elasticsearch
receiver/expvar
receiver/flinkmetrics
receiver/haproxy
receiver/hostmetrics
receiver/httpcheck
HTTP Check receiver
receiver/iis
receiver/kafkametrics
receiver/kubeletstats
receiver/memcached
receiver/mongodb
receiver/mongodbatlas
receiver/mysql
receiver/nginx
receiver/nsxt
NSXT Receiver
labels
Dec 20, 2022
github-actions
bot
requested review from
atoulme,
BinaryFissionGames,
jamesmoessis,
JonathanWamsley,
Mrod1598,
pmcollins,
rmfitzpatrick,
schmikei,
StefanKurek and
zenmoto
December 20, 2022 20:25
dmitryax
force-pushed
the
add-warning-ifenablednotset
branch
from
December 20, 2022 20:25
c209568
to
62c3597
Compare
Foresight Summary
View More Details⭕ build-and-test-windows workflow has finished in 3 seconds (43 minutes 36 seconds less than
|
Job | Failed Steps | Tests | |
---|---|---|---|
windows-unittest-matrix | - 🔗 | N/A | See Details |
windows-unittest | - 🔗 | N/A | See Details |
✅ tracegen workflow has finished in 1 minute 5 seconds (2 minutes 46 seconds less than main
branch avg.) and finished at 20th Dec, 2022.
Job | Failed Steps | Tests | |
---|---|---|---|
build-dev | - 🔗 | N/A | See Details |
publish-latest | - 🔗 | N/A | See Details |
publish-stable | - 🔗 | N/A | See Details |
✅ check-links workflow has finished in 1 minute 19 seconds (2 minutes 12 seconds less than main
branch avg.) and finished at 20th Dec, 2022.
Job | Failed Steps | Tests | |
---|---|---|---|
changed files | - 🔗 | N/A | See Details |
check-links | - 🔗 | N/A | See Details |
✅ changelog workflow has finished in 1 minute 41 seconds (7 minutes 21 seconds less than main
branch avg.) and finished at 20th Dec, 2022.
Job | Failed Steps | Tests | |
---|---|---|---|
changelog | - 🔗 | N/A | See Details |
✅ prometheus-compliance-tests workflow has finished in 3 minutes 25 seconds (6 minutes 33 seconds less than main
branch avg.) and finished at 20th Dec, 2022.
Job | Failed Steps | Tests | |
---|---|---|---|
prometheus-compliance-tests | - 🔗 | ✅ 21 ❌ 0 ⏭ 0 🔗 | See Details |
✅ build-and-test workflow has finished in 34 minutes 41 seconds (25 minutes 16 seconds less than main
branch avg.) and finished at 21st Dec, 2022.
Job | Failed Steps | Tests | |
---|---|---|---|
unittest-matrix (1.19, internal) | - 🔗 | ✅ 592 ❌ 0 ⏭ 0 🔗 | See Details |
unittest-matrix (1.18, extension) | - 🔗 | ✅ 528 ❌ 0 ⏭ 0 🔗 | See Details |
unittest-matrix (1.19, processor) | - 🔗 | ✅ 1474 ❌ 0 ⏭ 0 🔗 | See Details |
unittest-matrix (1.18, internal) | - 🔗 | ✅ 592 ❌ 0 ⏭ 0 🔗 | See Details |
correctness-metrics | - 🔗 | ✅ 2 ❌ 0 ⏭ 0 🔗 | See Details |
unittest-matrix (1.19, extension) | - 🔗 | ✅ 528 ❌ 0 ⏭ 0 🔗 | See Details |
unittest-matrix (1.18, processor) | - 🔗 | ✅ 1474 ❌ 0 ⏭ 0 🔗 | See Details |
correctness-traces | - 🔗 | ✅ 17 ❌ 0 ⏭ 0 🔗 | See Details |
unittest-matrix (1.18, receiver-0) | - 🔗 | ✅ 2539 ❌ 0 ⏭ 0 🔗 | See Details |
unittest-matrix (1.19, receiver-0) | - 🔗 | ✅ 2539 ❌ 0 ⏭ 0 🔗 | See Details |
unittest-matrix (1.19, exporter) | - 🔗 | ✅ 2456 ❌ 0 ⏭ 0 🔗 | See Details |
unittest-matrix (1.18, exporter) | - 🔗 | ✅ 2456 ❌ 0 ⏭ 0 🔗 | See Details |
unittest-matrix (1.18, other) | - 🔗 | ✅ 4394 ❌ 0 ⏭ 0 🔗 | See Details |
unittest-matrix (1.18, receiver-1) | - 🔗 | ✅ 1871 ❌ 0 ⏭ 0 🔗 | See Details |
unittest-matrix (1.19, receiver-1) | - 🔗 | ✅ 1871 ❌ 0 ⏭ 0 🔗 | See Details |
unittest-matrix (1.19, other) | - 🔗 | ✅ 4394 ❌ 0 ⏭ 0 🔗 | See Details |
integration-tests | - 🔗 | ✅ 55 ❌ 0 ⏭ 0 🔗 | See Details |
setup-environment | - 🔗 | N/A | See Details |
check-collector-module-version | - 🔗 | N/A | See Details |
checks | - 🔗 | N/A | See Details |
lint-matrix (receiver-0) | - 🔗 | N/A | See Details |
lint-matrix (receiver-1) | - 🔗 | N/A | See Details |
lint-matrix (processor) | - 🔗 | N/A | See Details |
lint-matrix (exporter) | - 🔗 | N/A | See Details |
lint-matrix (extension) | - 🔗 | N/A | See Details |
lint-matrix (internal) | - 🔗 | N/A | See Details |
lint-matrix (other) | - 🔗 | N/A | See Details |
check-codeowners | - 🔗 | N/A | See Details |
build-examples | - 🔗 | N/A | See Details |
lint | - 🔗 | N/A | See Details |
unittest (1.19) | - 🔗 | N/A | See Details |
unittest (1.18) | - 🔗 | N/A | See Details |
cross-compile (darwin, amd64) | - 🔗 | N/A | See Details |
cross-compile (darwin, arm64) | - 🔗 | N/A | See Details |
cross-compile (linux, 386) | - 🔗 | N/A | See Details |
cross-compile (linux, amd64) | - 🔗 | N/A | See Details |
cross-compile (linux, arm) | - 🔗 | N/A | See Details |
cross-compile (linux, arm64) | - 🔗 | N/A | See Details |
cross-compile (linux, ppc64le) | - 🔗 | N/A | See Details |
cross-compile (windows, 386) | - 🔗 | N/A | See Details |
cross-compile (windows, amd64) | - 🔗 | N/A | See Details |
build-package (deb) | - 🔗 | N/A | See Details |
build-package (rpm) | - 🔗 | N/A | See Details |
windows-msi | - 🔗 | N/A | See Details |
publish-check | - 🔗 | N/A | See Details |
publish-dev | - 🔗 | N/A | See Details |
publish-stable | - 🔗 | N/A | See Details |
✅ load-tests workflow has finished in 8 minutes 30 seconds (8 minutes 59 seconds less than main
branch avg.) and finished at 21st Dec, 2022.
Job | Failed Steps | Tests | |
---|---|---|---|
loadtest (TestIdleMode) | - 🔗 | ✅ 1 ❌ 0 ⏭ 0 🔗 | See Details |
loadtest (TestTraceAttributesProcessor) | - 🔗 | ✅ 3 ❌ 0 ⏭ 0 🔗 | See Details |
loadtest (TestTraceNoBackend10kSPS|TestTrace1kSPSWithAttrs) | - 🔗 | ✅ 8 ❌ 0 ⏭ 0 🔗 | See Details |
loadtest (TestTraceBallast1kSPSWithAttrs|TestTraceBallast1kSPSAddAttrs) | - 🔗 | ✅ 10 ❌ 0 ⏭ 0 🔗 | See Details |
loadtest (TestMetric10kDPS|TestMetricsFromFile) | - 🔗 | ✅ 6 ❌ 0 ⏭ 0 🔗 | See Details |
loadtest (TestMetricResourceProcessor|TestTrace10kSPS) | - 🔗 | ✅ 12 ❌ 0 ⏭ 0 🔗 | See Details |
loadtest (TestBallastMemory|TestLog10kDPS) | - 🔗 | ✅ 19 ❌ 0 ⏭ 0 🔗 | See Details |
setup-environment | - 🔗 | N/A | See Details |
*You can configure Foresight comments in your organization settings page.
dmitryax
force-pushed
the
add-warning-ifenablednotset
branch
from
December 20, 2022 20:27
62c3597
to
3d634b0
Compare
@astencel-sumo PTAL since you asked about it in #16536 |
dmitryax
force-pushed
the
add-warning-ifenablednotset
branch
3 times, most recently
from
December 20, 2022 21:57
beee647
to
527c90f
Compare
- if_enabled_not_set: to require `enabled` field to be explicitly set by user in case if metric is going to be turned from optional to default and vice versa. - if_configured: to make sure that metric is not configured by user. Should be used for deprecated optional metrics that will be removed soon. This change also adds more test coverage for the metrics config unmarshaling
dmitryax
force-pushed
the
add-warning-ifenablednotset
branch
from
December 20, 2022 23:52
527c90f
to
e6ad59b
Compare
MovieStoreGuy
approved these changes
Dec 22, 2022
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
cmd/mdatagen
mdatagen command
receiver/activedirectoryds
receiver/aerospike
receiver/apache
receiver/bigip
receiver/chrony
receiver/couchdb
receiver/dockerstats
receiver/elasticsearch
receiver/expvar
receiver/flinkmetrics
receiver/haproxy
receiver/hostmetrics
receiver/httpcheck
HTTP Check receiver
receiver/iis
receiver/kafkametrics
receiver/kubeletstats
receiver/memcached
receiver/mongodb
receiver/mongodbatlas
receiver/mysql
receiver/nginx
receiver/nsxt
NSXT Receiver
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.
This is a follow-up change to #16536 adding the following warnings:
if_enabled_not_set
: to requireenabled
field to be explicitly set by users in case if the metric is going to be turned from optional to default and vice versa.if_configured
: to ensure that users do not configure the metric. It should be used for deprecated optional metrics that will be removed soon.This change also adds more test coverage for the metrics config unmarshaling