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

Feature request for SSL 2 Way [[inputs.ssl]] #3854

Closed
fchiorascu opened this issue Mar 5, 2018 · 8 comments
Closed

Feature request for SSL 2 Way [[inputs.ssl]] #3854

fchiorascu opened this issue Mar 5, 2018 · 8 comments
Labels
feature request Requests for new plugin and for new features to existing plugins

Comments

@fchiorascu
Copy link

fchiorascu commented Mar 5, 2018

Directions

Bug report

Feature request for [[inputs.ssl]]

Relevant telegraf.conf:

System info:

Centos 7.3
telegraf 1.5.2
influxdb 1.4.3

Steps to reproduce:

  1. ...
  2. ...

Expected behavior:

To monitor ssl vs ssl 2 way if possible when you have in a project two components that have certificates and needs to communicate each other.

Actual behavior:

Additional info:

Feature Request

Kindly if possible to have an inputs for ssl vs ssl 2 way.

Proposal:

Current behavior:

Desired behavior:

Use case: [is very useful when you use many components in a project and a secure communication is needed and you cannot test very well and to have a KPI for this connection].

@danielnelson
Copy link
Contributor

I don't understand what you would like this plugin to do, can you add more information?

@fchiorascu
Copy link
Author

Hi Daniel,

The main scope in order to have this compared with Centreon, Nagios monitoring tools and others is the best way to have certificates details and to observe that the certificates applied as "ssl" or "ssl 2 way" are healthy from format point of view, they are not expired and most important in a platform where the communication between many components that have applied on their side a certificate ssl 2 way the communication works fine without loosing any pkt's between that components and in this way there is a need to have an [[inputs.ssl]] that will cover "ssl" certificates or "ssl 2 way" to have metrics that are ok as health, not expired, details about them self signed or not and other aspects if intermediate cert or additional infos, also to detect if they are working fine authorizing the communication proper if there could be implemented a way in telegraf to detect this.

Kind Regards,

@danielnelson
Copy link
Contributor

Got it, by the way we have a couple pull requests right now that are similar, but they don't do 2-way validation, so we will have to make sure this functionality is added:

@danielnelson danielnelson added the feature request Requests for new plugin and for new features to existing plugins label Mar 6, 2018
@fchiorascu
Copy link
Author

Thank you Daniel.
Sounds great.

@fchiorascu
Copy link
Author

Hi Daniel. Any news for this one? I'm very interested in having it. :)

@danielnelson
Copy link
Contributor

Just keep an eye on those two PRs, I'm still hoping this feature will make sense as part of a general certificate plugin.

@fchiorascu
Copy link
Author

Hi Daniel, for sure will make sense. Is widely used as ssl or ssl2way and the need for this plugin in any decent monitoring tool is huge base on the fact that you will use a certificate or multiple certificates in Production for sure.

Thank you.

@sjwang90
Copy link
Contributor

Check out inputs.x509_cert. Closing issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Requests for new plugin and for new features to existing plugins
Projects
None yet
Development

No branches or pull requests

3 participants