There's a number of available metrics (CAS can be configured to emit metrics in Prometheus format) which we should collect in Prometheus setup.
https://apereo.github.io/cas/development/monitoring/Configuring-Metrics.html
management.metrics.export.prometheus.enabled=true in cas.properties
Maybe we also need additional, site-specific ones which we could add via mtail.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T233921 Further steps for CAS/web SSO | |||
| Resolved | jbond | T233934 Collects metrics for CAS |
Change 551209 had a related patch set uploaded (by Jbond; owner: John Bond):
[operations/software/cas-overlay-template@master] promethus: add the metrics overlay to provide prometheus support
Change 551212 had a related patch set uploaded (by Jbond; owner: John Bond):
[operations/puppet@production] apereo_cas: add prometheus actuator
Change 551209 merged by Jbond:
[operations/software/cas-overlay-template@master] promethus: add the metrics overlay to provide prometheus support
Change 551212 merged by Jbond:
[operations/puppet@production] apereo_cas: add prometheus actuator
Change 553743 had a related patch set uploaded (by Jbond; owner: John Bond):
[operations/puppet@production] profile::prometheus::ops: add scraper for apero_cas idp service
Change 553750 had a related patch set uploaded (by Jbond; owner: John Bond):
[operations/puppet@production] apereo_cas: add localhost to list of allowed prometheus scrappers
Change 553750 merged by Jbond:
[operations/puppet@production] apereo_cas: add localhost to list of allowed prometheus scrappers
Change 553743 merged by Jbond:
[operations/puppet@production] profile::prometheus::ops: add scraper for apero_cas idp service
Change 554045 had a related patch set uploaded (by Jbond; owner: John Bond):
[operations/puppet@production] profile::prometheus::ops: add tls cname
Change 554045 merged by Jbond:
[operations/puppet@production] profile::prometheus::ops: add tls server name
While talking metrics and such for java, please consider also adding jmx_exporter (in addition to the native metrics) to CAS' jvm as we are doing for other JVMs across the fleet in T177197: Export Prometheus-compatible JVM metrics from JVMs in production
Change 554097 had a related patch set uploaded (by Jbond; owner: John Bond):
[operations/puppet@production] profile::idp: add jmx prometheus exporter
Change 554097 merged by Jbond:
[operations/puppet@production] profile::idp: add jmx prometheus exporter