Splunk Log Observer Connect for Cisco AppDynamics enriches the application logs with metadata specific to Splunk AppDynamics SaaS. To view logs in Splunk Platform in context of an application monitored by Splunk AppDynamics SaaS, you must integrate Splunk AppDynamics SaaS with Splunk Cloud Platform or Splunk Enterprise, depending on your deployment. Using the deep links on the Controller UI, you can directly navigate from Splunk AppDynamics SaaS to Splunk Platform with a single sign-on and view the logs corresponding to the application, tier, node, business transaction, and transaction snapshot. With logs, you can further drill down to identify the root cause and the source of an issue and then initiate remediation actions. 

Single sign-on is not enabled by default.  Administrators can enable single sign-on by using the same third party SAML identity provider on Splunk Platform and Splunk AppDynamics SaaS.

License Requirements

Use of the Log Observer Connect Integration between AppDynamics and Splunk Platform is subject to the General Terms and applicable Offer Description(s) or any superseding agreement between Cisco, AppDynamics, or Splunk, as applicable, and you.

To integrate Splunk AppDynamics SaaS with Splunk Platform, you need an active:

  • Splunk AppDynamics SaaS license
  • Splunk Cloud Platform license or Splunk Enterprise license depending on your deployment

For any issues related to Splunk Platform, contact Splunk Support.

Supported Regions

This feature is available to tenants in the following regions:

Americas

LocationZones
North America

aws-us-west-2 (pdx) 

South America

aws-sa-east-1 (gru)

APAC

LocationZones

Mumbai

aws-ap-south-1

Singapore

aws-ap-southeast-1

Sydney

aws-ap-southeast-2

EMEA

LocationZones

Frankfurt

aws-eu-central-1

London

aws- eu-west-2

Integration Steps

To integrate Splunk AppDynamics SaaS with Splunk Platform, perform the following tasks:

SequenceTaskDescription
1Configure Splunk service account user

Create a service account in Splunk Platform for Splunk AppDynamics SaaS integration. This user is used to access the indexes for applications  for application logs are stored.

2

Configure universal forwarder

Configure your existing universal forwarder to send meta data specific to Splunk AppDynamics SaaS and augment them with logs.

3

Configure the Cisco AppDynamics agents

 

Configure Java, .Net, and Node.js agents to enrich the log data with request GUID, business transaction ID, and node ID.

4

Configure the application loggers:

Configure the Java, .NET, and Node.js application loggers to enrich the log data. The configuration of the logger will vary based on whether you are using structured or unstructured logs, as well as the type of logging framework being utilized.

5

Configure Cisco AppDynamics for Splunk Log Observer Connect

 

Configure Cisco AppDynamics Controller to view the logs in Splunk. 

6

Configure allow list in Splunk Platform

Ensure that the IP addresses associated with Splunk AppDynamics SaaS can communicate with Splunk Cloud Platform or Splunk Enterprise.