Naas 1315 certificate receiver#1731
Open
vivki wants to merge 2 commits into
Open
Conversation
New OTel receiver emitting nginx.certificate.time_to_expiration (gauge, s) per SSL cert. Collector plugin pre-resolves cert metadata from NginxConfigContext into receiver config — no instance lookup at scrape time. 15s interval, gated on FeatureCertificates, one receiver per NGINX instance. Also: mdatagen stability annotations for existing receivers, fix NginxPlusReceivers multi-instance template condition.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed changes
What
Adds a certificate OTel receiver that emits nginx.certificate.time_to_expiration — a gauge (seconds) until each TLS cert in the NGINX config expires. Negative values = already expired.
Attributes: file_path, public_key_algorithm, serial_number, subject.common_name, resource.instance.id
Why
NGINXaaS customers have no visibility into TLS cert expiry today, so certs can expire silently with no GCM alerting signal.
How
Cert file paths are extracted from the already-parsed NginxConfigContext. Files and stored in the receiver config. The scraper reads and parses each file with crypto/x509 on every 15s scrape; renewals are reflected immediately without a collector restart.
Checklist
Before creating a PR, run through this checklist and mark each as complete.
CONTRIBUTINGdocumentmake install-toolsand have attached any dependency changes to this pull requestREADME.md)