Skip to content
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

[receiver/httpcheck] Support log pipeline for httpcheck events #31933

Closed
smithclay opened this issue Mar 25, 2024 · 4 comments
Closed

[receiver/httpcheck] Support log pipeline for httpcheck events #31933

smithclay opened this issue Mar 25, 2024 · 4 comments
Labels
closed as inactive enhancement New feature or request needs triage New item requiring triage receiver/httpcheck HTTP Check receiver Stale

Comments

@smithclay
Copy link
Contributor

Component(s)

receiver/httpcheck

Is your feature request related to a problem? Please describe.

When the httpcheck receiver runs a check, optionally allow users to capture the result of the check as an OTLP log, optionally with the response body.

Describe the solution you'd like

Support for emitting log related to the status of checks in the httpcheck receiver. Attributes should be consistent with https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/httpcheckreceiver/documentation.md

Describe alternatives you've considered

This could be done via a connector (turn the metrics from httpcheck into logs), but this seems more appropriate as a native capability of the http check to emit OTLP logs.

Additional context

No response

@smithclay smithclay added enhancement New feature or request needs triage New item requiring triage labels Mar 25, 2024
@github-actions github-actions bot added the receiver/httpcheck HTTP Check receiver label Mar 25, 2024
Copy link
Contributor

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@carlosalberto
Copy link
Contributor

I have a draft PR on how this could be supported: carlosalberto#2

Please provide feedback on whether this is a feasible approach ;) @codeboten

Copy link
Contributor

github-actions bot commented Jul 9, 2024

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

See Adding Labels via Comments if you do not have permissions to add labels yourself.

@github-actions github-actions bot added the Stale label Jul 9, 2024
Copy link
Contributor

github-actions bot commented Sep 7, 2024

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed as inactive enhancement New feature or request needs triage New item requiring triage receiver/httpcheck HTTP Check receiver Stale
Projects
None yet
Development

No branches or pull requests

2 participants