-
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
[docs]: Is the healthcheckv2 extension actually active, or just baked into the release but not available? #33301
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
@diranged, thanks for your report. Only the skeleton exists at this point. The rest of the extension is written, but it's being reviewed and merged in smaller chunks. We can update the readme as you suggest. |
Agreed README needs an update. I've spent most of today building a custom collector that includes this component but it appears it doesn't actually work or do anything as none of the ports are listening. A note on the README to indicate that it shouldn't be used yet would be very helpful. |
…#33313) **Description:** Several users have tried to use this extension as the README makes it appear as though it's ready for use. I've updated the README to include a warning and a note that the README is forward looking. I think it's useful to describe the functionality that the extension will provide when #30673 has been fully decomposed and integrated. cc: @diranged @twistypigeon Let me know if stronger wording is needed. **Link to tracking Issue:** #33301 **Documentation:** README update
Apologies for the confusion. I sincerely hope we can get the extension in a usable form shortly. In the meantime, the readme has been updated to note that it's not currently ready for use. If you'd like any further changes to the readme, comment and I'll address them. |
@mwear I noticed that the |
Component(s)
extension/healthcheckv2
What happened?
Description
The
healthcheckv2
extension doesn't seem active or available in the https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.101.0 or https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.100.0 docker images - even though it was listed as being released in theNew Components
section of the https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.100.0 readme:If it's not available yet - can we update the README to indicate that?
#32523
Collector version
0.101.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
OpenTelemetry Collector configuration
No response
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: