NETWAYS / NETWAYS/support-collector

[Feature]: Collect TLS certificate information

Open
#113 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature to-be-discussed
Dominant language
Go
Stars
0
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Describe the feature request

I'd like to see information about certificates used by services support collector scrapes.

My idea for a first attempt would be to connect to default ports on localhost for all collected services. Just use openssl to get the basic information. Personally I don't see a problem with collecting the public certificate via curl/openssl but I can imagine some people having security concerns (justified or not).

But what I want to see:

  • Certificate matched to service (so that you don't have to guess if it's an Icinga 2 API, Icinga Web 2 or some other service certificate)
  • Expiry time
  • Issuer (important to know whether it's managed by a built in CA or replaced by some self signed or company CA signed certificate)
  • All names and IPs the certificate is valid for

I'd like to see this at least for the following (default ports to make things easier, maybe other ports should be planned for the future):

  • Icinga 2 (5665)
  • Icinga Web 2 (443)
  • Kibana (5601)
  • Elasticsearch (9200)
  • Elasticsearch Cluster Interconnect (9300)
  • Logstash Beats Input (5044)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the existing service collectors and scrape configuration, then determine how certificate data from the listed default ports and openssl would fit; done means reporting the matched service, expiry, issuer, and certificate names and IPs.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
networking, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.