[Draft] Add docker_otel_input package #15739
Open
+343
−0
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
This package implements a Docker Stats input using the OpenTelemetry Collector's dockerstats receiver, following the pattern established in PR elastic#14315. Key features: - Type: integration with otelcol input (not content package) - Configurable collection interval, endpoint, and filtering - Comprehensive field definitions for container metrics - Full documentation and test policy Resolves: elastic#15731 Co-authored-by: William Easton <strawgate@users.noreply.github.com>
strawgate
commented
Oct 23, 2025
andrewkroh
added
New Integration
cmacknz
reviewed
Oct 24, 2025
| processors: | ||
| resourcedetection: | ||
| # Modify the list of detectors to match the cloud environment | ||
| detectors: [env, system, gcp, ec2, azure] |
Member
There was a problem hiding this comment.
This needs to be configurable as long as it lives here. In the long term this neeeds to not be in each package.
Member
There was a problem hiding this comment.
In the long term this neeeds to not be in each package.
I guess we could inject this from Fleet, and make it configurable there.
Contributor
Author
There was a problem hiding this comment.
Does this actually need to be configurable for now?
jsoriano
reviewed
Oct 27, 2025
Co-authored-by: Jaime Soriano Pastor <jaime.soriano@elastic.co>
💔 Build Failed
Failed CI StepsHistory
|
5 tasks
2 tasks
criamico
added a commit
to elastic/kibana
that referenced
this pull request
Nov 25, 2025
Fixes #243720 ## Summary Integration input health reports otelcol inputs with `receiver id` instead of input type `otelcol`. Currently the input health show input name "otelcol" for any receiver, making it difficult to diagnose which input has issues in case of multiple inputs. This PR addresses it, showing the receiver id instead of the generic type. Note that this change is done only for "otelcol" inputs and not for any other type of inputs, they'll keep showing the type instead; the link ref stays the same, it's just the text that has been changed. ### Before <img width="951" height="638" alt="Screenshot 2025-11-24 at 15 57 20" src="https://github.com/user-attachments/assets/9e67c70b-4e73-45c6-8bc4-ba0c5de70b91" /> ### After <img width="1771" height="996" alt="Screenshot 2025-11-24 at 15 51 36" src="https://github.com/user-attachments/assets/84a3ef3f-8895-405c-8417-dda772964d09" /> ### Testing - Locally build this package: elastic/integrations#15739 - Install it into Fleet with ``` curl -XPOST -H 'content-type: application/zip' -H 'kbn-xsrf: true' http://localhost:5601/<PATH>/api/fleet/epm/packages -u elastic:changeme --data-binary @docker_otel_input-0.2.0.zip ``` - Add it to an agent policy and enroll an agent into that policy - Verify the input health in agent view. The input name should correspond to the receiver id and the link should correctly navigate to the logs. ### Checklist - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
adcoelho
pushed a commit
to adcoelho/kibana
that referenced
this pull request
Nov 25, 2025
…ic#244013) Fixes elastic#243720 ## Summary Integration input health reports otelcol inputs with `receiver id` instead of input type `otelcol`. Currently the input health show input name "otelcol" for any receiver, making it difficult to diagnose which input has issues in case of multiple inputs. This PR addresses it, showing the receiver id instead of the generic type. Note that this change is done only for "otelcol" inputs and not for any other type of inputs, they'll keep showing the type instead; the link ref stays the same, it's just the text that has been changed. ### Before <img width="951" height="638" alt="Screenshot 2025-11-24 at 15 57 20" src="https://github.com/user-attachments/assets/9e67c70b-4e73-45c6-8bc4-ba0c5de70b91" /> ### After <img width="1771" height="996" alt="Screenshot 2025-11-24 at 15 51 36" src="https://github.com/user-attachments/assets/84a3ef3f-8895-405c-8417-dda772964d09" /> ### Testing - Locally build this package: elastic/integrations#15739 - Install it into Fleet with ``` curl -XPOST -H 'content-type: application/zip' -H 'kbn-xsrf: true' http://localhost:5601/<PATH>/api/fleet/epm/packages -u elastic:changeme --data-binary @docker_otel_input-0.2.0.zip ``` - Add it to an agent policy and enroll an agent into that policy - Verify the input health in agent view. The input name should correspond to the receiver id and the link should correctly navigate to the logs. ### Checklist - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
eokoneyo
pushed a commit
to eokoneyo/kibana
that referenced
this pull request
Dec 2, 2025
…ic#244013) Fixes elastic#243720 ## Summary Integration input health reports otelcol inputs with `receiver id` instead of input type `otelcol`. Currently the input health show input name "otelcol" for any receiver, making it difficult to diagnose which input has issues in case of multiple inputs. This PR addresses it, showing the receiver id instead of the generic type. Note that this change is done only for "otelcol" inputs and not for any other type of inputs, they'll keep showing the type instead; the link ref stays the same, it's just the text that has been changed. ### Before <img width="951" height="638" alt="Screenshot 2025-11-24 at 15 57 20" src="https://github.com/user-attachments/assets/9e67c70b-4e73-45c6-8bc4-ba0c5de70b91" /> ### After <img width="1771" height="996" alt="Screenshot 2025-11-24 at 15 51 36" src="https://github.com/user-attachments/assets/84a3ef3f-8895-405c-8417-dda772964d09" /> ### Testing - Locally build this package: elastic/integrations#15739 - Install it into Fleet with ``` curl -XPOST -H 'content-type: application/zip' -H 'kbn-xsrf: true' http://localhost:5601/<PATH>/api/fleet/epm/packages -u elastic:changeme --data-binary @docker_otel_input-0.2.0.zip ``` - Add it to an agent policy and enroll an agent into that policy - Verify the input health in agent view. The input name should correspond to the receiver id and the link should correctly navigate to the logs. ### Checklist - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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 package implements a Docker Stats input using the OpenTelemetry
Collector's dockerstats receiver, following the pattern established
in PR #14315.
Key features:
Resolves: #15731