Skip to main content
Atoti APM (Application Performance Monitoring) is a solution for monitoring the healthiness and performance of an application. It provides several features easing the support work, and reducing the burden of maintaining and troubleshooting Atoti Server.

Configuration

Adding APM in an Atoti project

You can use the APM starter to setup APM in our project.

Logging

APM relies on SLF4J with a Logback binding for the logging part.

Configuration

Logback supports custom conversion specifiers allowing to display specific information properly within the logs. APM defines three custom converter detailed below: Then, Logback configuration example can make use of these converters as follows:

Loggers Categorization

APM loggers could be categorized as follows:

Data loading

The MonitoredDataLoadingConfig class provides the bean messageHandler() which creates the implementation of the IMessageHandler. In your source Spring config class you could do the following:
Depending on the properties, the bean allows to:
  • log start/end processing of some input data, as well as the errors, through the logger com.activeviam.apm.source
  • log the rejections of the input data through the logger com.activeviam.apm.source.rejection
  • specify the property feed.loading.message.handler.type to select the type of the message handler: ** if set to DEFAULT, simply logs detailed information about loading file ** if set to LOG, logs the feed loading in an external file (CSV style) upon completion using the logger com.activeviam.apm.loaded.feed ** if set to WEBHOOK, call a webhook (external service) upon completion of the file loading

Properties exposed

List of the properties exposed as well as their default value