Help Center/ Application Performance Management/ User Guide (ME-Abu Dhabi Region)/ Collection Management/ Collection Configuration
Updated on 2022-02-21 GMT+08:00
View PDF

Collection Configuration

To reduce memory, database, and disk space usage, you can implement collection configurations as required. Collection configurations take effect for the selected application.

Procedure

  1. Log in to the Application Performance Management (APM) console.
  2. In the navigation pane, choose Agent > Configuration.
  3. Select an application from the Application drop-down list.

    If different applications have different collection configurations, the collection configuration applied to all applications will overwrite that of a specific application.

  4. Click to enable data collection.

    This function is enabled by default. When you do not need to collect tracing or topology data of a specific application, disable this function to reduce resource usage.

  5. Click to enable the function of collecting normal call chain data.

    To reduce the resources consumed by probes, APM collects one more data record every minute when a transaction is abnormal or the latency is greater than Application Performance Index (Apdex) Threshold. If this function is enabled, normal call chain data is sampled and collected. If this function is disabled, normal call chain data is not collected.

  6. Click to enable memory monitoring.

    To prevent probes from affecting service performance in peak hours, enable memory monitoring. When the instance memory usage is excessively high, probes enter the hibernation state. You can also click to set the duration and memory usage.
    • Memory usage = Memory used by the Java process/Maximum available memory
    • Maximum available memory: Use the smaller value between the available memory quota of the container and the maximum heap memory of the JVM. The maximum heap memory of the JVM is the value of -Xmx. The default value is 25% of the maximum available memory of the JVM.
    • The memory usage during collection suspension must be greater than or equal to that during collection restoration.

  7. Click to enable the function of adding trace IDs to logs.

    A trace ID uniquely identifies a tracing. When this function is enabled, the system adds trace IDs to logs. You can accurately search for logs based on trace IDs, such as ffffffffe1c08cab, ffffffffe1c08cad, and ffffffffe1c08cae.

  8. Click to enable SQL analysis.

    When this function is disabled, no SQL data is affected, but you cannot implement SQL analysis.

  9. Set the HTTP response codes to be ignored.

    To quickly and accurately locate abnormal tracing, and prevent probes from misreporting normal tracing data, such as custom response codes, set the HTTP response codes to be ignored. Such codes will not be recorded in the error record table. Click , enter the HTTP response codes to be ignored, and click . If multiple HTTP response codes exit, separate them by commas (,).

  10. Set the errors and exceptions to be ignored.

    To quickly and accurately locate abnormal tracing, and prevent probes from misreporting normal tracing data, set the errors and exceptions to be ignored. Such errors and exceptions will not be recorded in the error record table. Click , enter the errors and exceptions to be ignored, and click . If multiple Java exception classes exist, separate them by commas (,). The default value is null.

Parent topic: Collection Management