Comments (1)
Hey, I've also noticed that the metrics only show when there is at least one Certificate resource in the cluster. Without any certificates, it shows this:
$ kubectl get --raw /api/v1/namespaces/cert-manager/services/cert-manager:9402/proxy/metrics
# HELP certmanager_clock_time_seconds DEPRECATED: use clock_time_seconds_gauge instead. The clock time given in seconds (from 1970/01/01 UTC).
# TYPE certmanager_clock_time_seconds counter
certmanager_clock_time_seconds 1.7114653e+09
# HELP certmanager_clock_time_seconds_gauge The clock time given in seconds (from 1970/01/01 UTC).
# TYPE certmanager_clock_time_seconds_gauge gauge
certmanager_clock_time_seconds_gauge 1.7114653e+09
# HELP certmanager_controller_sync_call_count The number of sync() calls made by a controller.
# TYPE certmanager_controller_sync_call_count counter
certmanager_controller_sync_call_count{controller="certificaterequests-approver"} 4
certmanager_controller_sync_call_count{controller="certificaterequests-issuer-acme"} 4
certmanager_controller_sync_call_count{controller="certificaterequests-issuer-ca"} 4
certmanager_controller_sync_call_count{controller="certificaterequests-issuer-selfsigned"} 4
certmanager_controller_sync_call_count{controller="certificaterequests-issuer-vault"} 4
certmanager_controller_sync_call_count{controller="certificaterequests-issuer-venafi"} 4
certmanager_controller_sync_call_count{controller="certificates-issuing"} 4
certmanager_controller_sync_call_count{controller="certificates-key-manager"} 4
certmanager_controller_sync_call_count{controller="certificates-metrics"} 4
certmanager_controller_sync_call_count{controller="certificates-readiness"} 4
certmanager_controller_sync_call_count{controller="certificates-request-manager"} 4
certmanager_controller_sync_call_count{controller="certificates-revision-manager"} 4
certmanager_controller_sync_call_count{controller="certificates-trigger"} 4
certmanager_controller_sync_call_count{controller="clusterissuers"} 2
certmanager_controller_sync_call_count{controller="issuers"} 3
Then, I add one certificate:
kubectl apply -f - <<EOF
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
name: test
spec:
secretName: test
issuerRef:
name: test
kind: Issuer
dnsNames:
- test
EOF
The metrics are now showing:
$ k get --raw /api/v1/namespaces/cert-manager/services/cert-manager:9402/proxy/metrics
# HELP certmanager_certificate_expiration_timestamp_seconds The date after which the certificate expires. Expressed as a Unix Epoch Time.
# TYPE certmanager_certificate_expiration_timestamp_seconds gauge
certmanager_certificate_expiration_timestamp_seconds{issuer_group="",issuer_kind="Issuer",issuer_name="test",name="test",namespace="default"} 0
# HELP certmanager_certificate_ready_status The ready status of the certificate.
# TYPE certmanager_certificate_ready_status gauge
certmanager_certificate_ready_status{condition="False",issuer_group="",issuer_kind="Issuer",issuer_name="test",name="test",namespace="default"} 1
certmanager_certificate_ready_status{condition="True",issuer_group="",issuer_kind="Issuer",issuer_name="test",name="test",namespace="default"} 0
certmanager_certificate_ready_status{condition="Unknown",issuer_group="",issuer_kind="Issuer",issuer_name="test",name="test",namespace="default"} 0
# HELP certmanager_certificate_renewal_timestamp_seconds The number of seconds before expiration time the certificate should renew.
# TYPE certmanager_certificate_renewal_timestamp_seconds gauge
certmanager_certificate_renewal_timestamp_seconds{issuer_group="",issuer_kind="Issuer",issuer_name="test",name="test",namespace="default"} 0
# HELP certmanager_clock_time_seconds DEPRECATED: use clock_time_seconds_gauge instead. The clock time given in seconds (from 1970/01/01 UTC).
# TYPE certmanager_clock_time_seconds counter
certmanager_clock_time_seconds 1.711465478e+09
# HELP certmanager_clock_time_seconds_gauge The clock time given in seconds (from 1970/01/01 UTC).
# TYPE certmanager_clock_time_seconds_gauge gauge
certmanager_clock_time_seconds_gauge 1.711465478e+09
# HELP certmanager_controller_sync_call_count The number of sync() calls made by a controller.
# TYPE certmanager_controller_sync_call_count counter
certmanager_controller_sync_call_count{controller="certificaterequests-approver"} 7
certmanager_controller_sync_call_count{controller="certificaterequests-issuer-acme"} 7
certmanager_controller_sync_call_count{controller="certificaterequests-issuer-ca"} 7
certmanager_controller_sync_call_count{controller="certificaterequests-issuer-selfsigned"} 7
certmanager_controller_sync_call_count{controller="certificaterequests-issuer-vault"} 7
certmanager_controller_sync_call_count{controller="certificaterequests-issuer-venafi"} 7
certmanager_controller_sync_call_count{controller="certificates-issuing"} 11
certmanager_controller_sync_call_count{controller="certificates-key-manager"} 9
certmanager_controller_sync_call_count{controller="certificates-metrics"} 8
certmanager_controller_sync_call_count{controller="certificates-readiness"} 12
certmanager_controller_sync_call_count{controller="certificates-request-manager"} 12
certmanager_controller_sync_call_count{controller="certificates-revision-manager"} 11
certmanager_controller_sync_call_count{controller="certificates-trigger"} 11
certmanager_controller_sync_call_count{controller="clusterissuers"} 2
certmanager_controller_sync_call_count{controller="issuers"} 3
from cert-manager.
Related Issues (20)
- Adding custom annotation to cm ingress resources HOT 2
- clusterlint claims that webhook timeoutSeconds of 30 is too high HOT 2
- Make Route53 dns01 work with EKS pod identity HOT 1
- Securing Gateway in GKE is failing
- Preselection in field Server not accepted on save. Manual selection required
- add template for creating cluster issuer and issuer HOT 3
- Certificate resource not updated after ingress annotation is changed HOT 1
- Should upgrade status managed fields from CSA to SSA when ServerSideApply feature gate enabled HOT 1
- Missing `cmctl` and `kubectl-cert_manager` binaries in GitHub releases HOT 5
- Incomplete regular expression for hostnames HOT 3
- cert manager not issuing certs for one ingress (in work queue no longer exists) HOT 1
- Gateway: Combining HTTPS listener with TLS-termination and TLS listener with TLS-passthrough HOT 4
- Race Condition: Cert-Manager Generates Endless Certificate Requests on Openshift HOT 6
- Web Hook in cert-manager is not working properly. Can anyone please me out. HOT 8
- Solver pod returns 404 error during http01 challenge HOT 5
- v1.12.X release Infinite loop with 2 certs with different keystore settings HOT 4
- Report the use of components with vulnerabilities in cert-manager HOT 3
- I don't understand the purpose of the new tests.
- Confusing messaging when certificate secret name already exist HOT 1
- Optionally write ca.crt to ConfigMap
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cert-manager.