Storage - CAS Metrics

CAS metrics may be routed to varying types of databases for storage and analytics. The following options are available:

Simple (In Memory)
Graphite
Ganglia
JMX
Atlas
Signal FX
Statsd
InfluxDb
Prometheus
Wavefront
New Relic
CloudWatch
…

Atlas

By default, metrics are exported to Atlas running on your local machine. The location of the Atlas server to use can be provided using:

The following settings and properties are available from the CAS configuration catalog:

Third Party
Notes

_{The configuration settings listed below are tagged as Optional in the CAS configuration metadata. This
flag indicates that the presence of the setting
is not immediately necessary in the end-user CAS configuration, because a default value is assigned or
the activation of the feature is not conditionally controlled by the setting value. In other words, you should only include this field in your
configuration if you need to modify the default value or if you need to turn on the feature controlled by the setting.}


No data available in table

_{The configuration settings listed below are tagged as Third Party in the CAS configuration metadata. This flag indicates that the configuration setting is not controlled, owned or managed by the CAS ecosystem, and affects functionality that is offered by a third-party library, such as Spring Boot or Spring Cloud to CAS. For additional info, you might have to visit the third-party source to find more details.}

Show entries

Search:

management.metrics.export.atlas.batch-size=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

When possible, properties should be stored in lower-case kebab format, such as cas.property-name=value. The only possible exception to this rule is when naming actuator endpoints; The name of the actuator endpoints (i.e. ssoSessions) MUST remain in camelCase mode.

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.atlas.batch-size=...

This is the most common form of property configuration that is recognized by CAS, regardless of the actual property source, which might in fact be managed separately outside the CAS environment, by another system or cloud framework.

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      atlas: 
        batch-size: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.atlas.batch-size="..." -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory. Note the placement of the system property which must be specified before the CAS web application is launched.

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_ATLAS_BATCH_SIZE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.atlas.batch-size="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.atlas.metrics.export.batch-size.

management.metrics.export.atlas.config-refresh-frequency=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.atlas.config-refresh-frequency=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      atlas: 
        config-refresh-frequency: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.atlas.config-refresh-frequency="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_ATLAS_CONFIG_REFRESH_FREQUENCY="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.atlas.config-refresh-frequency="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.atlas.metrics.export.config-refresh-frequency.

management.metrics.export.atlas.config-time-to-live=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.atlas.config-time-to-live=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      atlas: 
        config-time-to-live: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.atlas.config-time-to-live="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_ATLAS_CONFIG_TIME_TO_LIVE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.atlas.config-time-to-live="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.atlas.metrics.export.config-time-to-live.

management.metrics.export.atlas.config-uri=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.atlas.config-uri=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      atlas: 
        config-uri: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.atlas.config-uri="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_ATLAS_CONFIG_URI="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.atlas.config-uri="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.atlas.metrics.export.config-uri.

management.metrics.export.atlas.connect-timeout=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.atlas.connect-timeout=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      atlas: 
        connect-timeout: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.atlas.connect-timeout="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_ATLAS_CONNECT_TIMEOUT="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.atlas.connect-timeout="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.atlas.metrics.export.connect-timeout.

Showing 1 to 5 of 13 entries

Previous1 2 3Next

Configuration Metadata

The collection of configuration properties listed in this section are automatically generated from the CAS source and components that contain the actual field definitions, types, descriptions, modules, etc. This metadata may not always be 100% accurate, or could be lacking details and sufficient explanations.

Be Selective

This section is meant as a guide only. Do NOT copy/paste the entire collection of settings into your CAS configuration; rather pick only the properties that you need. Do NOT enable settings unless you are certain of their purpose and do NOT copy settings into your configuration only to keep them as reference. All these ideas lead to upgrade headaches, maintenance nightmares and premature aging.

YAGNI

Note that for nearly ALL use cases, declaring and configuring properties listed here is sufficient. You should NOT have to explicitly massage a CAS XML/Java/etc configuration file to design an authentication handler, create attribute release policies, etc. CAS at runtime will auto-configure all required changes for you. If you are unsure about the meaning of a given CAS setting, do NOT turn it on without hesitation. Review the codebase or better yet, ask questions to clarify the intended behavior.

Naming Convention

Property names can be specified in very relaxed terms. For instance cas.someProperty, cas.some-property, cas.some_property are all valid names. While all forms are accepted by CAS, there are certain components (in CAS and other frameworks used) whose activation at runtime is conditional on a property value, where this property is required to have been specified in CAS configuration using kebab case. This is both true for properties that are owned by CAS as well as those that might be presented to the system via an external library or framework such as Spring Boot, etc.

Note

Settings and properties that are controlled by the CAS platform directly always begin with the prefix cas. All other settings are controlled and provided to CAS via other underlying frameworks and may have their own schemas and syntax. BE CAREFUL with the distinction. Unrecognized properties are rejected by CAS and/or frameworks upon which CAS depends. This means if you somehow misspell a property definition or fail to adhere to the dot-notation syntax and such, your setting is entirely refused by CAS and likely the feature it controls will never be activated in the way you intend.

Validation

Configuration properties are automatically validated on CAS startup to report issues with configuration binding, specially if defined CAS settings cannot be recognized or validated by the configuration schema. Additional validation processes are also handled via Configuration Metadata and property migrations applied automatically on startup by Spring Boot and family.

Indexed Settings

CAS settings able to accept multiple values are typically documented with an index, such as cas.some.setting[0]=value. The index [0] is meant to be incremented by the adopter to allow for distinct multiple configuration blocks.

Datadog

Datadog registry pushes metrics to datadoghq periodically. To export metrics to Datadog, your API key must be provided:

The following settings and properties are available from the CAS configuration catalog:

Third Party
Notes


No data available in table

Show entries

Search:

management.metrics.export.datadog.api-key=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.datadog.api-key=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      datadog: 
        api-key: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.datadog.api-key="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_DATADOG_API_KEY="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.datadog.api-key="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.datadog.metrics.export.api-key.

management.metrics.export.datadog.application-key=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.datadog.application-key=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      datadog: 
        application-key: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.datadog.application-key="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_DATADOG_APPLICATION_KEY="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.datadog.application-key="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.datadog.metrics.export.application-key.

management.metrics.export.datadog.batch-size=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.datadog.batch-size=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      datadog: 
        batch-size: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.datadog.batch-size="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_DATADOG_BATCH_SIZE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.datadog.batch-size="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.datadog.metrics.export.batch-size.

management.metrics.export.datadog.connect-timeout=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.datadog.connect-timeout=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      datadog: 
        connect-timeout: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.datadog.connect-timeout="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_DATADOG_CONNECT_TIMEOUT="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.datadog.connect-timeout="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.datadog.metrics.export.connect-timeout.

management.metrics.export.datadog.descriptions=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.datadog.descriptions=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      datadog: 
        descriptions: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.datadog.descriptions="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_DATADOG_DESCRIPTIONS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.datadog.descriptions="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.datadog.metrics.export.descriptions.

Showing 1 to 5 of 11 entries

Previous1 2 3Next

Configuration Metadata

Be Selective

YAGNI

Naming Convention

Note

Validation

Indexed Settings

Ganglia

By default, metrics are exported to Ganglia running on your local machine. The Ganglia server host and port to use can be provided using:

The following settings and properties are available from the CAS configuration catalog:

Third Party
Notes

Show entries

Search:

management.metrics.export.ganglia.addressing-mode=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.ganglia.addressing-mode=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      ganglia: 
        addressing-mode: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.ganglia.addressing-mode="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_GANGLIA_ADDRESSING_MODE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.ganglia.addressing-mode="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.ganglia.metrics.export.addressing-mode.

management.metrics.export.ganglia.duration-units=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.ganglia.duration-units=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      ganglia: 
        duration-units: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.ganglia.duration-units="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_GANGLIA_DURATION_UNITS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.ganglia.duration-units="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.ganglia.metrics.export.duration-units.

management.metrics.export.ganglia.enabled=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.ganglia.enabled=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      ganglia: 
        enabled: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.ganglia.enabled="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_GANGLIA_ENABLED="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.ganglia.enabled="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.ganglia.metrics.export.enabled.

management.metrics.export.ganglia.host=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.ganglia.host=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      ganglia: 
        host: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.ganglia.host="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_GANGLIA_HOST="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.ganglia.host="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.ganglia.metrics.export.host.

management.metrics.export.ganglia.port=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.ganglia.port=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      ganglia: 
        port: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.ganglia.port="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_GANGLIA_PORT="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.ganglia.port="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.ganglia.metrics.export.port.

Showing 1 to 5 of 8 entries

Previous1 2Next

Configuration Metadata

Be Selective

YAGNI

Naming Convention

Note

Validation

Indexed Settings

Graphite

By default, metrics are exported to Graphite running on your local machine. The Graphite server host and port to use can be provided using:

The following settings and properties are available from the CAS configuration catalog:

Third Party
Notes

Show entries

Search:

management.metrics.export.graphite.duration-units=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.graphite.duration-units=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      graphite: 
        duration-units: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.graphite.duration-units="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_GRAPHITE_DURATION_UNITS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.graphite.duration-units="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.graphite.metrics.export.duration-units.

management.metrics.export.graphite.enabled=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.graphite.enabled=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      graphite: 
        enabled: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.graphite.enabled="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_GRAPHITE_ENABLED="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.graphite.enabled="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.graphite.metrics.export.enabled.

management.metrics.export.graphite.graphite-tags-enabled=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.graphite.graphite-tags-enabled=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      graphite: 
        graphite-tags-enabled: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.graphite.graphite-tags-enabled="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_GRAPHITE_GRAPHITE_TAGS_ENABLED="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.graphite.graphite-tags-enabled="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.graphite.metrics.export.graphite-tags-enabled.

management.metrics.export.graphite.host=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.graphite.host=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      graphite: 
        host: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.graphite.host="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_GRAPHITE_HOST="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.graphite.host="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.graphite.metrics.export.host.

management.metrics.export.graphite.port=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.graphite.port=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      graphite: 
        port: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.graphite.port="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_GRAPHITE_PORT="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.graphite.port="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.graphite.metrics.export.port.

Showing 1 to 5 of 9 entries

Previous1 2Next

Configuration Metadata

Be Selective

YAGNI

Naming Convention

Note

Validation

Indexed Settings

InfluxDb

By default, metrics are exported to Influx running on your local machine. The location of the Influx server to use can be provided using:

The following settings and properties are available from the CAS configuration catalog:

Third Party
Notes

Show entries

Search:

management.metrics.export.influx.api-version=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.influx.api-version=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      influx: 
        api-version: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.influx.api-version="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_INFLUX_API_VERSION="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.influx.api-version="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.influx.metrics.export.api-version.

management.metrics.export.influx.auto-create-db=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.influx.auto-create-db=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      influx: 
        auto-create-db: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.influx.auto-create-db="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_INFLUX_AUTO_CREATE_DB="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.influx.auto-create-db="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.influx.metrics.export.auto-create-db.

management.metrics.export.influx.batch-size=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.influx.batch-size=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      influx: 
        batch-size: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.influx.batch-size="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_INFLUX_BATCH_SIZE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.influx.batch-size="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.influx.metrics.export.batch-size.

management.metrics.export.influx.bucket=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.influx.bucket=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      influx: 
        bucket: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.influx.bucket="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_INFLUX_BUCKET="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.influx.bucket="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.influx.metrics.export.bucket.

management.metrics.export.influx.compressed=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.influx.compressed=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      influx: 
        compressed: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.influx.compressed="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_INFLUX_COMPRESSED="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.influx.compressed="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.influx.metrics.export.compressed.

Showing 1 to 5 of 21 entries

Previous1 2 3 4 5Next

# 
# management.metrics.export.influx.api-version=

# 
# management.metrics.export.influx.auto-create-db=

# 
# management.metrics.export.influx.batch-size=

# 
# management.metrics.export.influx.bucket=

# 
# management.metrics.export.influx.compressed=

# 
# management.metrics.export.influx.connect-timeout=

# 
# management.metrics.export.influx.consistency=

# 
# management.metrics.export.influx.db=

# 
# management.metrics.export.influx.enabled=

# 
# management.metrics.export.influx.num-threads=

# 
# management.metrics.export.influx.org=

# 
# management.metrics.export.influx.password=

# 
# management.metrics.export.influx.read-timeout=

# 
# management.metrics.export.influx.retention-duration=

# 
# management.metrics.export.influx.retention-policy=

# 
# management.metrics.export.influx.retention-replication-factor=

# 
# management.metrics.export.influx.retention-shard-duration=

# 
# management.metrics.export.influx.step=

# 
# management.metrics.export.influx.token=

# 
# management.metrics.export.influx.uri=

# 
# management.metrics.export.influx.user-name=

Configuration Metadata

Be Selective

YAGNI

Naming Convention

Note

Validation

Indexed Settings

JMX

Micrometer provides a hierarchical mapping to JMX, primarily as a cheap and portable way to view metrics locally.

New Relic

New Relic registry pushes metrics to New Relic periodically. To export metrics to New Relic, your API key and account id must be provided:

The following settings and properties are available from the CAS configuration catalog:

Third Party
Notes

Show entries

Search:

management.metrics.export.newrelic.account-id=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.newrelic.account-id=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      newrelic: 
        account-id: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.newrelic.account-id="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_NEWRELIC_ACCOUNT_ID="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.newrelic.account-id="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.newrelic.metrics.export.account-id.

management.metrics.export.newrelic.api-key=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.newrelic.api-key=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      newrelic: 
        api-key: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.newrelic.api-key="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_NEWRELIC_API_KEY="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.newrelic.api-key="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.newrelic.metrics.export.api-key.

management.metrics.export.newrelic.batch-size=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.newrelic.batch-size=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      newrelic: 
        batch-size: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.newrelic.batch-size="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_NEWRELIC_BATCH_SIZE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.newrelic.batch-size="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.newrelic.metrics.export.batch-size.

management.metrics.export.newrelic.client-provider-type=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.newrelic.client-provider-type=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      newrelic: 
        client-provider-type: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.newrelic.client-provider-type="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_NEWRELIC_CLIENT_PROVIDER_TYPE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.newrelic.client-provider-type="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.newrelic.metrics.export.client-provider-type.

management.metrics.export.newrelic.connect-timeout=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.newrelic.connect-timeout=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      newrelic: 
        connect-timeout: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.newrelic.connect-timeout="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_NEWRELIC_CONNECT_TIMEOUT="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.newrelic.connect-timeout="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.newrelic.metrics.export.connect-timeout.

Showing 1 to 5 of 12 entries

Previous1 2 3Next

Configuration Metadata

Be Selective

YAGNI

Naming Convention

Note

Validation

Indexed Settings

Prometheus

Prometheus expects to scrape or poll individual app instances for metrics. Spring Boot provides an actuator endpoint available at /actuator/prometheus to present a Prometheus scrape with the appropriate format.

Here is an example scrape_config to add to prometheus.yml:

scrape_configs:
  - job_name: 'spring'
    metrics_path: '/actuator/prometheus'
    static_configs:
      - targets: ['HOST:PORT']

SignalFx

SignalFx registry pushes metrics to SignalFx periodically. To export metrics to SignalFx, your access token must be provided:

The following settings and properties are available from the CAS configuration catalog:

Third Party
Notes

Show entries

Search:

management.metrics.export.signalfx.access-token=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.signalfx.access-token=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      signalfx: 
        access-token: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.signalfx.access-token="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_SIGNALFX_ACCESS_TOKEN="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.signalfx.access-token="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.signalfx.metrics.export.access-token.

management.metrics.export.signalfx.batch-size=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.signalfx.batch-size=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      signalfx: 
        batch-size: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.signalfx.batch-size="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_SIGNALFX_BATCH_SIZE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.signalfx.batch-size="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.signalfx.metrics.export.batch-size.

management.metrics.export.signalfx.connect-timeout=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.signalfx.connect-timeout=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      signalfx: 
        connect-timeout: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.signalfx.connect-timeout="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_SIGNALFX_CONNECT_TIMEOUT="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.signalfx.connect-timeout="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.signalfx.metrics.export.connect-timeout.

management.metrics.export.signalfx.enabled=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.signalfx.enabled=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      signalfx: 
        enabled: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.signalfx.enabled="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_SIGNALFX_ENABLED="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.signalfx.enabled="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.signalfx.metrics.export.enabled.

management.metrics.export.signalfx.num-threads=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.signalfx.num-threads=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      signalfx: 
        num-threads: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.signalfx.num-threads="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_SIGNALFX_NUM_THREADS="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.signalfx.num-threads="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwithout a replacement setting.

Showing 1 to 5 of 10 entries

Previous1 2Next

Configuration Metadata

Be Selective

YAGNI

Naming Convention

Note

Validation

Indexed Settings

Memory

Micrometer ships with a simple, in-memory backend that is automatically used as a fallback if no other registry is configured. This allows you to see what metrics are collected in the metrics endpoint.

The in-memory backend disables itself as soon as you’re using any of the other available backend. You can also disable it explicitly:

The following settings and properties are available from the CAS configuration catalog:

Third Party
Notes

Show entries

Search:

management.metrics.export.simple.enabled=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.simple.enabled=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      simple: 
        enabled: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.simple.enabled="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_SIMPLE_ENABLED="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.simple.enabled="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.simple.metrics.export.enabled.

management.metrics.export.simple.mode=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.simple.mode=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      simple: 
        mode: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.simple.mode="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_SIMPLE_MODE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.simple.mode="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.simple.metrics.export.mode.

management.metrics.export.simple.step=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.simple.step=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      simple: 
        step: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.simple.step="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_SIMPLE_STEP="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.simple.step="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.simple.metrics.export.step.

Showing 1 to 3 of 3 entries

Previous1Next

Configuration Metadata

Be Selective

YAGNI

Naming Convention

Note

Validation

Indexed Settings

StatsD

The StatsD registry pushes metrics over UDP to a StatsD agent eagerly. By default, metrics are exported to a StatsD agent running on your local machine. The StatsD agent host and port to use can be provided using:

The following settings and properties are available from the CAS configuration catalog:

Third Party
Notes

Show entries

Search:

management.metrics.export.statsd.enabled=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.statsd.enabled=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      statsd: 
        enabled: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.statsd.enabled="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_STATSD_ENABLED="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.statsd.enabled="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.statsd.metrics.export.enabled.

management.metrics.export.statsd.flavor=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.statsd.flavor=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      statsd: 
        flavor: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.statsd.flavor="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_STATSD_FLAVOR="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.statsd.flavor="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.statsd.metrics.export.flavor.

management.metrics.export.statsd.host=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.statsd.host=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      statsd: 
        host: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.statsd.host="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_STATSD_HOST="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.statsd.host="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.statsd.metrics.export.host.

management.metrics.export.statsd.max-packet-length=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.statsd.max-packet-length=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      statsd: 
        max-packet-length: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.statsd.max-packet-length="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_STATSD_MAX_PACKET_LENGTH="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.statsd.max-packet-length="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.statsd.metrics.export.max-packet-length.

management.metrics.export.statsd.polling-frequency=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.statsd.polling-frequency=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      statsd: 
        polling-frequency: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.statsd.polling-frequency="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_STATSD_POLLING_FREQUENCY="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.statsd.polling-frequency="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.statsd.metrics.export.polling-frequency.

Showing 1 to 5 of 9 entries

Previous1 2Next

Configuration Metadata

Be Selective

YAGNI

Naming Convention

Note

Validation

Indexed Settings

Wavefront

Wavefront registry pushes metrics to Wavefront periodically. If you are exporting metrics to Wavefront directly, your API token must be provided:

The following settings and properties are available from the CAS configuration catalog:

Third Party
Notes

Show entries

Search:

management.metrics.export.wavefront.api-token=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.wavefront.api-token=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      wavefront: 
        api-token: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.wavefront.api-token="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_WAVEFRONT_API_TOKEN="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.wavefront.api-token="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.wavefront.api-token.

management.metrics.export.wavefront.batch-size=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.wavefront.batch-size=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      wavefront: 
        batch-size: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.wavefront.batch-size="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_WAVEFRONT_BATCH_SIZE="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.wavefront.batch-size="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.wavefront.sender.batch-size.

management.metrics.export.wavefront.connect-timeout=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.wavefront.connect-timeout=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      wavefront: 
        connect-timeout: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.wavefront.connect-timeout="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_WAVEFRONT_CONNECT_TIMEOUT="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.wavefront.connect-timeout="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwithout a replacement setting.

management.metrics.export.wavefront.enabled=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.wavefront.enabled=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      wavefront: 
        enabled: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.wavefront.enabled="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_WAVEFRONT_ENABLED="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.wavefront.enabled="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.wavefront.metrics.export.enabled.

management.metrics.export.wavefront.global-prefix=

_{How can I configure this property?}

Configuration properties can be included and activated using the following strategies.

Note

CAS properties can be specified using the Java configuration property syntax in any and all .properties files:


1

management.metrics.export.wavefront.global-prefix=...

CAS properties can be specified using the YAML syntax:

management: 
  metrics: 
    export: 
      wavefront: 
        global-prefix: "..."

Note that YAML is very specific about structure and indentation. Be sure to verify the correctness of the final result with your YAML validator of choice.

CAS properties can be passed to the CAS web application as system properties, when the application is launched:

java -Dmanagement.metrics.export.wavefront.global-prefix="..." -jar build/libs/cas.war

CAS properties can specified as system environment variables before the CAS web application is launched:

export MANAGEMENT_METRICS_EXPORT_WAVEFRONT_GLOBAL_PREFIX="..."

java -jar build/libs/cas.war

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

CAS properties can be passed to the CAS web application as command-line arguments, when the application is launched:

java -jar build/libs/cas.war --management.metrics.export.wavefront.global-prefix="..."

The above example assumes that the CAS web application is packaged as cas.war with an embedded server container and can be found in the build/libs directory.

Deprecation status is ERRORwith a replacement setting: management.wavefront.metrics.export.global-prefix.

Showing 1 to 5 of 13 entries

Previous1 2 3Next

Configuration Metadata

Be Selective

YAGNI

Naming Convention

Note