JavaMelody Monitoring

Use JavaMelody to monitor CAS in QA and production environments.

Usage Warning!

This functionality is not yet compatible with the CAS ecosystem of libraries, and/or Spring Boot. As a result, support for this feature is dropped. Please consider using alternatives and keep an eye on future releases of CAS to see if support for this feature is re-introduced.

Support is added by including the following dependency in the WAR overlay:

<dependency>
    <groupId>org.apereo.cas</groupId>
    <artifactId>cas-server-support-javamelody</artifactId>
    <version>${cas.version}</version>
</dependency>

implementation "org.apereo.cas:cas-server-support-javamelody:${project.'cas.version'}"

dependencyManagement {
    imports {
        mavenBom "org.apereo.cas:cas-server-support-bom:${project.'cas.version'}"
    }
}

dependencies {
    implementation "org.apereo.cas:cas-server-support-javamelody"
}

dependencies {
    /*
        The following platform references are included automatically and are listed for reference only.

        implementation enforcedPlatform("org.apereo.cas:cas-server-support-bom:${project.'cas.version'}")
        implementation platform(org.springframework.boot.gradle.plugin.SpringBootPlugin.BOM_COORDINATES)
        
    */
    implementation "org.apereo.cas:cas-server-support-javamelody"
}

JavaMelody monitoring is by default exposed at ${context-path}/monitoring where ${context-path} is typically set to /cas.

Configuration

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

javamelody.enabledIf JavaMelody should be enabled within the application.

true

Third party

If JavaMelody should be enabled within the application.

Type: Boolean
Default: true
Defined by: JavaMelodyConfigurationProperties

javamelody.excluded-datasourcesComma-separated list of data source names which should be excluded from monitoring.

no default

Third party

Comma-separated list of data source names which should be excluded from monitoring.

Type: String
Default: none
Defined by: JavaMelodyConfigurationProperties

javamelody.init-parametersMap of initialization parameters to be passed to the JavaMelody monitoring filter.

no default

Third party

Map of initialization parameters to be passed to the JavaMelody monitoring filter. The available parameters are listed here: https://github.com/javamelody/javamelody/wiki/UserGuide#6-optional-parameters

Type: Map<String,String>
Default: none
Defined by: JavaMelodyConfigurationProperties

javamelody.management-endpoint-monitoring-enabledIf /monitoring should be enabled for reports in the management http port instead of on the application http port.

false

Third party

If /monitoring should be enabled for reports in the management http port instead of on the application http port.

Type: Boolean
Default: false
Defined by: JavaMelodyConfigurationProperties

javamelody.spring-monitoring-enabledIf monitoring based on @RestController, @Controller, @Service, @Async, @Scheduled, @MonitoredWithSpring, @FeignClient or on RestTemplate, MongoDatabaseFactory or ElasticsearchOperations should be enabled.

true

Third party

If monitoring based on @RestController, @Controller, @Service, @Async, @Scheduled, @MonitoredWithSpring, @FeignClient or on RestTemplate, MongoDatabaseFactory or ElasticsearchOperations should be enabled.

Type: Boolean
Default: true
Defined by: JavaMelodyConfigurationProperties

Required settings may be needed to activate or affect the feature; review them even when they have a default. Optional settings only need to be set to change a default or to turn on the behavior they control. Third party settings belong to libraries such as Spring Boot that CAS builds on; their own documentation may have more detail.

Notes on configuration

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

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.

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, especially 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.