This documentation mentions features that are currently in the early access phase. Cisco AppDynamics makes no warranties regarding these features, including performance, quality, or availability, and reserves the right to change the features and its documentation including the content herein at any time before making them generally available as well as never making them generally available. Any buying decisions should be made based on features and products that are currently generally available.

  1. Understand Unified Observability Experience
    2.   
  2. Integrate SaaS Controller with Cisco Cloud Observability
  3. Configure Java Agent And AppDynamics Controller to Push Logs
    4.   
  4. Configure the OpenTelemetry Collector to Push Log Records to Cisco Cloud Observability

  5. Troubleshoot with Application Logs

Configure your Java Agent and AppDynamics Controller to send the application logs to Cisco Cloud Observability.

Before You Begin

Ensure that you have:

  • the Java Agent version >=23.10.0
  • the Controller version >= 23.11.0
  • the Apache Log4j version <= 2.21

Configure Java Agent

Do the following to configure the Java Agent:

  1. To enable OpenTelemetry for Java Agent, add the following system properties in your JVM System Properties. See Enable OpenTelemetry in the Java Agent. 

    -Dappdynamics.opentelemetry.enabled=true
    CODE

    If you have already enabled OpenTelemetry in your Java Agent, ignore this step.

  2. Set the tier name in service.name and application name in service.namespace for the JVM:

    -Dotel.resource.attributes="service.name=<myServiceName>,service.namespace=<myServiceNameSpace>"
    CODE


    You can also set tier and application names in the OTEL_RESOURCE_ATTRIBUTES environment variable. See Configure Resource Attributes.

  3. (Optional) To export only logs and disable export of traces and metrics to Cisco Cloud Observability, add the following system properties:

    -Dotel.traces.exporter=none -Dotel.metrics.exporter=none
    CODE


    You can also add the preceding system properties by using the environment variables OTEL_TRACES_EXPORTER and  OTEL_METRICS_EXPORTER. See OpenTelemetry Documentation.

    For Early Access Program, you can only export logs from AppDynamics SaaS to Cisco Cloud Observability. If you are already exporting traces and metrics to a different backend service, you need to accordingly configure your OpenTelemetry Collector. Java Agent can export data to only one OpenTelemetry Collector at a time.

Configure AppDynamics Controller Node Property

You must configure the following node property in your Controller:

name: opentelemetry-logs-push-enabled
valueType: Boolean
Value: true

The app agent keeps sending logs data to the Cisco Cloud Observability tenant and keeps consuming the tokens, unless the node-property to send logs from the SaaS Controller is set to false.

Configure Log Types 

By default, all types of logs are pushed to Cisco Observability Platform tenant. However, you can configure the verbosity level of logs that you want to push by using following node property in your Controller. For instance, if you set value of property as warn, then agent will only export all warning, error, and fatal messages. 

name: opentelemetry-allowed-log-level
valueType: String
defaultValue: all
Value: one of all,trace,debug,info,warn,error,fatal,off