[9.1] (backport #9928) Ingest internal telemetry from the OTel Collector when it is running #10233
+1,471
−14
Conversation
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
![mergify[bot]](https://avatars.githubusercontent.com/in/10562?s=60&v=4){kind=small}
…9928) Add a monitoring component to ingest telemetry values from the collector's prometheus endpoint into the `elastic_agent.collector` dataset. This includes a remapping script processor to convert the collector's metrics to their closest ECS equivalents when possible. This is a temporary approach that will not scale to full collector metrics in a general configuration, but gives us a backwards-compatible stopgap during the initial monitoring-only rollout. (cherry picked from commit a441ebe) # Conflicts: # NOTICE-fips.txt # NOTICE.txt # go.mod # internal/pkg/agent/application/application.go # internal/pkg/agent/application/monitoring/otel_remap.js # internal/pkg/agent/application/monitoring/v1_monitor.go # internal/pkg/agent/application/monitoring/v1_monitor_test.go # internal/pkg/agent/cmd/inspect.go # testing/integration/ess/beat_receivers_test.go
mergify
bot
added
backport
conflicts
mergify
bot
requested review from
michalpristas and
blakerouse
and removed request for
a team
|
Cherry-pick of a441ebe has failed: To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally |
github-actions
bot
added
enhancement
|
Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane) |
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.
Add a monitoring component to ingest telemetry values from the collector's prometheus endpoint into the
elastic_agent.collectordataset. This includes a remapping script processor to convert the collector's metrics to their closest ECS equivalents when possible.This is a temporary approach that will not scale to full collector metrics in a general configuration, but gives us a backwards-compatible stopgap during the initial monitoring-only rollout.
Checklist
./changelog/fragmentsusing the changelog toolHow to test this PR locally
Enable agent monitoring while at least one component (including monitoring itself) uses the otel runtime. Prometheus metrics from the collector should be ingested to the
elastic_agent.collectordataset.Related issues
This is an automatic backport of pull request #9928 done by [Mergify](https://mergify.com).