-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Heartbeat report TLS details #3741
Comments
Also requested on Discuss: https://discuss.elastic.co/t/capture-https-certificate-expiration-dates-using-heartbeat/77865?u=andrewkroh |
There is a date to include this feature on Heartbeat? |
@RobertoFlores There is no specific date. |
Pinging @elastic/uptime |
As an update we now support the expiration dates. I'm on the fence WRT the other info as that crosses into security scanning tools when we're thinking about auditing things like cipher suites and TLS versions. On the other hand, these are simple tiny fields. |
I propose we close this for now unless there are any objections. TLS version and cipher suite are usually in the realm of vulnerability scanning tools. I'm not sure they belong in heartbeat. |
When heartbeat is connecting via TLS, report information on server certificate and connection details if possible:
The text was updated successfully, but these errors were encountered: