-
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
New component: X.509 Certificate Monitoring #33215
Comments
Will you be using a scraper approach for this? Did you build a metadata.yaml? Would you please share it? Which attributes do you want always enabled? Are attributes based off the fields of the cert? |
Yes the software will scrape, the implementation is pretty much the same of telegraf and you can find it here. The plan as I said is to wrap their code and include their license, we have a first implementation ready but it's not based on this repo but built following https://opentelemetry.io/docs/collector/building/receiver/. If there is interest we will change the code and add the metadata.yaml |
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 |
We're still looking for sponsors here! |
alright, happy to be the sponsor. |
The purpose and use-cases of the new component
This will be a receiver based on the telegraf x509cert plugin code following their license requirement and build and interface on top of it to match the collector interface.
Example configuration for the component
Telemetry data types supported
For each certificate in the
sources
list we will extract all properties of the certificate and use the remaining validity duration in seconds as value.Is this a vendor-specific component?
Code Owner(s)
LucaLanziani, zimny
Sponsor (optional)
@atoulme
Additional context
No response
The text was updated successfully, but these errors were encountered: