-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
[feature request] SSL Certificate Input #1971
Comments
Telegraf is used for capturing time series data. Values that change. Most of those values do not change. The only one that does is the expiry time. For that see #1762 |
@phemmer Fair, enough I am unsure how I missed that. Thanks! I will leave this here for now but I have no objection to closing this and using the above mentioned input if no one else can think of a good use for this data. |
Perhaps a mixture of the two might be best. I think all that data is overkill, but some of it might be useful for tagging & filtering if you're monitoring a large number of servers with different certificates. |
Speaking to the above about the timeseries data, I completely agree. My reason for pulling everything is because data is cheap, if I am going to pull one thing I might as well pull it all. Who knows in the future how it could be used or what other inputs I could cross reference with it. I do agree on the overkill but I also believe when it comes to metrics, within reason, anything worth doing is worth overdoing. ;) |
Perhaps. For frequently polled data, that extra information can be detrimental though. It's a lot of data to have to store when you're really just after a single 4 or 8 byte number. More work for the time series DB (e.g. InfluxDB). It's also a lot of data to have to ignore when you're manually poking through the DB. But if I were to throw out a feature list, I would expect such a plugin to provide the following:
In the case that a host name is used to connect to, I would expect the plugin to connect to all of the resolved IPs, instead of having to resort to random chance each time it runs. |
+1 on this functionality Just to comment on the idea that Telegraf is only used for capturing time-series data: Yep, and it's a shame, because it means people are either:
I believe InfluxDB itself has had various issues over time asking for implementation of a generic key-value store for exactly this reason. Kapacitor has related issues to this as well. |
We have the |
Feature Request
A telegraf input for SSL certificates and associated values.
Proposal:
I would like to write a telegraf input that could pull fields/values from a SSL certificate. I see the following data as useful:
Current behavior:
Nothing currently exists that I am aware of
Desired behavior:
All reasonable stats for the certificate tree for a given certificate
Use case:
I want alerts on my certificates expiring. I would like the dates to be in influx along with the expire date and then using kapacitor I could say something along the lines of:
The text was updated successfully, but these errors were encountered: