Skip to main content

AppDynamics

Reading time: 0 minute(s) (0 words)

AppDynamics is a performance management program for applications. It helps users to gain a comprehensive understanding of the impact of technical difficulties on business goals, allowing IT teams to prioritize their efforts in a way that improves ROI.

AppDynamics parameters and supported features in Nobl9
General support:
Release channel: Stable, Beta
Connection method: Agent, Direct
Replay and SLI Analyzer: Supported
Event logs: Supported
Query checker: Not supported
Query parameters retrieval: Supported
Timestamp cache persistence: Supported
Query parameters:
Query interval: 1 min
Query delay: 1 min
Jitter: 15 sec
Timeout: 30 sec
Agent details and minimum required versions for supported features:
Environment variable: APPD_QUERY_DELAY
Plugin name: n9appd
Replay and SLI Analyzer: 0.68.0
Maximum historical data retrieval period: 30 days
Query parameters retrieval: 0.73.2
Timestamp cache persistence: 0.65.0
Additional notes:
No support for metric paths with Wild Cards
Learn more Opens in a new tab

Prerequisites​

  1. The Nobl9 agent has firewall access to http://<controller_host>:<controller_port>/controller/rest/<REST_URI>.

  2. To connect to AppDynamics, your AppDynamics API client needs at least the Applications and Dashboards Viewer permissions.

Authentication​

Nobl9 agent calls the Metric and Snapshot API | AppDynamics documentation. The agent and direct configurations for AppDynamics require the following credentials:

  • Client Name: To retrieve apiClientName, log in to your AppDynamics account, go to Administration (under cog icon) / API Clients tab, select an API client and copy Client Name.

  • Account Name: To retrieve your accountName, log in to your AppDynamics account, go to the License (under cog icon) / License Summary / Account Details section and copy the Name.

  • Controller URL: It is an entry point for Nobl9 to AppDynamics instance. Example: http://yourcompany.saas.appdynamics.com

  • Client Secret: Follow the instructions in the API Clients | AppDynamics documentation section of the AppDynamics documentation to create your Client Secret.

Adding AppDynamics as a data source​

You can add the AppDynamics data source using the direct or agent connection methods.

Direct connection method​

Direct connection to AppDynamics requires users to enter their credentials which Nobl9 stores safely.

Nobl9 Web​

To set up this type of connection:

  1. Navigate to Integrations > Sources.
  2. Click .
  3. Click the required Source button.
  4. Choose Direct.
  1. Select one of the following Release Channels:
    • The stable channel is fully tested by the Nobl9 team. It represents the final product; however, this channel does not contain all the new features of a beta release. Use it to avoid crashes and other limitations.
    • The beta channel is under active development. Here, you can check out new features and improvements without the risk of affecting any viable SLOs. Remember that features in this channel can change.

  2. Enter the Controller URL (required).
    Refer to the Authentication section for detailed instructions.

  3. Enter your AppDynamics Client Name.
    To retrieve the Client Name, log in to your AppDynamics account, go to Administration (under the cog icon) > API Clients tab, select an API client and copy the Client Name:

diagram
Image 1: Retrieving the Client Name in AppDynamics UI
  1. Enter your AppDynamics Account Name.
    To retrieve your Account Name, log in to your AppDynamics account, go to License (under the cog icon) > License Summary > Account Details section and copy the Name:
diagram
Image 2: Retrieving the Account Name in AppDynamics UI
  1. Select a Project.
    Specifying a project is helpful when multiple users are spread across multiple teams or projects. When the Project field is left blank, Nobl9 uses the default project.
  2. Enter a Display Name.
    You can enter a user-friendly name with spaces in this field.
  3. Enter a Name.
    The name is mandatory and can only contain lowercase, alphanumeric characters, and dashes (for example, my-project-1). Nobl9 duplicates the display name here, transforming it into the supported format, but you can edit the result.
  4. Enter a Description.
    Here you can add details such as who is responsible for the integration (team/owner) and the purpose of creating it.
  5. Specify the Query delay to set a customized delay for queries when pulling the data from the data source.
    • The default value in AppDynamics integration for Query delay is 1 minute.
    info
    Changing the Query delay may affect your SLI data. For more details, check the Query delay documentation.
  6. Enter a Maximum Period for Historical Data Retrieval.
    • This value defines how far back in the past your data will be retrieved when replaying your SLO based on this data source.
    • The maximum period value depends on the data source.
      Find the maximum value for your data source.
    • A greater period can extend the loading time when creating an SLO.
      • The value must be a positive integer.
  7. Enter a Default Period for Historical Data Retrieval.
    • It is used by SLOs connected to this data source.
    • The value must be a positive integer or 0.
    • By default, this value is set to 0. When you set it to >0, you will create SLOs with Replay.
  8. Click Add Data Source.
caution

Keep note that AppDynamics Metric and Snapshot API downsamples data differently based on the period of fetched historical data, and it may affect your SLI charts.

Also, the resolution of data points in the Appdynamics UI and what Nobl9 extracts from AppDynamics Metric and Snapshot API may differ. This is because the data's granularity in AppDynamics API differs from the AppDynamics Controller UI. Check this thread for more details.

For more details refer to Data Retention for Metric and Snapshot API | AppDynamics documentation.

sloctl​

The YAML for setting up a direct connection to AppDynamics looks like this:

apiVersion: n9/v1alpha
kind: Direct
metadata:
  name: appdynamics-direct
  displayName: AppDynamics direct
  project: appdynamics-direct
spec:
  description: AppDynamics direct integration
  sourceOf:
    - Metrics
    - Services
  releaseChannel: stable
  queryDelay:
      unit: Minute
      value: 720
  appDynamics:
    url: https://yourcompany.saas.appdynamics.com
    clientName: dev-direct
    accountName: name
    clientSecret: someSecret # secret
  historicalDataRetrieval:
    maxDuration:
      value: 30
      unit: Day
    defaultDuration:
      value: 0
      unit: Day
FieldTypeDescription
queryDelay.unit
mandatory
enumSpecifies the unit for the query delay. Possible values: Second | Minute.
• Check query delay documentation for default unit of query delay for each source.
queryDelay.value
mandatory
numericSpecifies the value for the query delay.
• Must be a number less than 1440 minutes (24 hours).
• Check query delay documentation for default unit of query delay for each source.
logCollectionEnabled
optional
booleanOptional. Defaults to false. Set to true if you'd like your direct to collect event logs. Contact us to activate it.
releaseChannel
mandatory
enumSpecifies the release channel. Accepted values: beta | stable.
Source-specific fields
appDynamics.url
mandatory
stringBase URL to an AppDynamics Controller. For more details, check AppDynamics Concepts.
appDynamics.clientName
mandatory
stringSee authentication section above for more details.
appDynamics.accountName
mandatory
stringSee authentication section above for more details.
appDynamics.clientSecret
mandatory
stringSee authentication section above for more details.
Replay-related fields
historicalDataRetrieval
optional
n/aOptional structure related to configuration related to Replay.
❗ Use only with supported sources.
• If omitted, Nobl9 uses the default values of value: 0 and unit: Day for maxDuration and defaultDuration.
maxDuration.value
optional
numericSpecifies the maximum duration for historical data retrieval. Must be integer ≥ 0. See Replay documentation for values of max duration per data source.
maxDuration.unit
optional
enumSpecifies the unit for the maximum duration of historical data retrieval. Accepted values: Minute | Hour | Day.
defaultDuration.value
optional
numericSpecifies the default duration for historical data retrieval. Must be integer ≥ 0 and ≤ maxDuration.
defaultDuration.unit
optional
enumSpecifies the unit for the default duration of historical data retrieval. Accepted values: Minute | Hour | Day.

Agent connection method​

Nobl9 Web​

Follow the instructions below to create your AppDynamics agent connection.

  1. Navigate to Integrations > Sources.
  2. Click .
  3. Click the required Source button.
  4. Choose Agent.
  1. Select one of the following Release Channels:
    • The stable channel is fully tested by the Nobl9 team. It represents the final product; however, this channel does not contain all the new features of a beta release. Use it to avoid crashes and other limitations.
    • The beta channel is under active development. Here, you can check out new features and improvements without the risk of affecting any viable SLOs. Remember that features in this channel can change.

  2. Enter the Controller URL.

  1. Select a Project.
    Specifying a project is helpful when multiple users are spread across multiple teams or projects. When the Project field is left blank, Nobl9 uses the default project.
  2. Enter a Display Name.
    You can enter a user-friendly name with spaces in this field.
  3. Enter a Name.
    The name is mandatory and can only contain lowercase, alphanumeric characters, and dashes (for example, my-project-1). Nobl9 duplicates the display name here, transforming it into the supported format, but you can edit the result.
  4. Enter a Description.
    Here you can add details such as who is responsible for the integration (team/owner) and the purpose of creating it.
  5. Specify the Query delay to set a customized delay for queries when pulling the data from the data source.
    • The default value in AppDynamics integration for Query delay is 1 minute.
    info
    Changing the Query delay may affect your SLI data. For more details, check the Query delay documentation.
  6. Enter a Maximum Period for Historical Data Retrieval.
    • This value defines how far back in the past your data will be retrieved when replaying your SLO based on this data source.
    • The maximum period value depends on the data source.
      Find the maximum value for your data source.
    • A greater period can extend the loading time when creating an SLO.
      • The value must be a positive integer.
  7. Enter a Default Period for Historical Data Retrieval.
    • It is used by SLOs connected to this data source.
    • The value must be a positive integer or 0.
    • By default, this value is set to 0. When you set it to >0, you will create SLOs with Replay.
  8. Click Add Data Source.

sloctl​

The YAML for setting up an agent connection to AppDynamics looks like this:

apiVersion: n9/v1alpha
kind: Agent
metadata:
  name: appdynamics-agent
  displayName: AppDynamics Agent
  project: default
spec:
  description: Agent settings for appdynamics
  sourceOf:
    - Metrics
    - Services
  releaseChannel: stable
  queryDelay:
      unit: Minute
      value: 720
  historicalDataRetrieval:
    maxDuration:
      value: 30
      unit: Day
    defaultDuration:
      value: 7
      unit: Day
  appDynamics:
    url: https://yourcompany.saas.appdynamics.com
FieldTypeDescription
queryDelay.unit
mandatory
enumSpecifies the unit for the query delay. Possible values: Second | Minute.
• Check query delay documentation for default unit of query delay for each source.
queryDelay.value
mandatory
numericSpecifies the value for the query delay.
• Must be a number less than 1440 minutes (24 hours).
• Check query delay documentation for default unit of query delay for each source.
releaseChannel
mandatory
enumSpecifies the release channel. Accepted values: beta | stable.
Source-specific fields
appDynamics.url
mandatory
stringBase URL to an AppDynamics Controller. For more details, check AppDynamics Concepts.
Replay-related fields
historicalDataRetrieval
optional
n/aOptional structure related to configuration related to Replay.
❗ Use only with supported sources.
• If omitted, Nobl9 uses the default values of value: 0 and unit: Day for maxDuration and defaultDuration.
maxDuration.value
optional
numericSpecifies the maximum duration for historical data retrieval. Must be integer ≥ 0. See Replay documentation for values of max duration per data source.
maxDuration.unit
optional
enumSpecifies the unit for the maximum duration of historical data retrieval. Accepted values: Minute | Hour | Day.
defaultDuration.value
optional
numericSpecifies the default duration for historical data retrieval. Must be integer ≥ 0 and ≤ maxDuration.
defaultDuration.unit
optional
enumSpecifies the unit for the default duration of historical data retrieval. Accepted values: Minute | Hour | Day.
warning

You can deploy only one agent in one YAML file by using the sloctl apply command.

Agent deployment​

When you add the data source, Nobl9 automatically generates a Kubernetes configuration and a Docker command line for you to use to deploy the agent. Both of these are available in the web UI, under the Agent Configuration section. Be sure to swap in your credentials (e.g., replace <APPD_CLIENT_NAME>, <APPD_ACCOUNT_NAME> and <APPD_CLIENT_SECRET> with your organization key).

If you use Kubernetes, you can apply the supplied YAML config file to a Kubernetes cluster to deploy the agent. It will look something like this:

# DISCLAIMER: This deployment description contains only the fields necessary for the purpose of this demo.
# It is not a ready-to-apply k8s deployment description, and the appd_client_name, appd_account_name and appd_client_secret are only exemplary values.

apiVersion: v1
kind: Secret
metadata:
  name: nobl9-agent-nobl9-dev-default-name
  namespace: default
type: Opaque
stringData:
  appd_client_name: "<APPD_CLIENT_NAME>"
  appd_account_name: "<APPD_ACCOUNT_NAME>"
  appd_client_secret: "<APPD_CLIENT_SECRET>"
  client_id: "unique_client_id"
  client_secret: "unique_client_secret"
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: nobl9-agent-nobl9-dev-default-name
  namespace: default
spec:
  replicas: 1
  selector:
    matchLabels:
      nobl9-agent-name: "appdynamics-agent"
      nobl9-agent-project: "appdynamics-project"
      nobl9-agent-organization: "nobl9-dev"
  template:
    metadata:
      labels:
        nobl9-agent-name: "appdynamics-agent"
        nobl9-agent-project: "appdynamics-project"
        nobl9-agent-organization: "nobl9-dev"
    spec:
      containers:
        - name: agent-container
          image: nobl9/agent:0.82.2
          resources:
            requests:
              memory: "350Mi"
              cpu: "0.1"
          env:
            - name: N9_CLIENT_ID
              valueFrom:
                secretKeyRef:
                  key: client_id
                  name: nobl9-agent-nobl9-dev-default-name
            - name: N9_CLIENT_SECRET
              valueFrom:
                secretKeyRef:
                  key: client_secret
                  name: nobl9-agent-nobl9-dev-default-name
            - name: APPD_CLIENT_NAME
              valueFrom:
                secretKeyRef:
                  key: appd_client_name
                  name: nobl9-agent-nobl9-dev-default-name
            - name: APPD_ACCOUNT_NAME
              valueFrom:
                secretKeyRef:
                  key: appd_account_name
                  name: nobl9-agent-nobl9-dev-default-name
            - name: APPD_CLIENT_SECRET
              valueFrom:
                secretKeyRef:
                  key: appd_client_secret
                  name: nobl9-agent-nobl9-dev-appd-agent-test
            # The N9_METRICS_PORT is a variable specifying the port to which the /metrics and /health endpoints are exposed.
            # The 9090 is the default value and can be changed.
            # If you don’t want the metrics to be exposed, comment out or delete the N9_METRICS_PORT variable.
            - name: N9_METRICS_PORT
              value: "9090"

Creating SLOs with AppDynamics​

Nobl9 Web​

Follow the instructions below to create your SLOs with AppDynamics in the UI:

  1. Navigate to Service Level Objectives.

  2. Click .
    The SLO wizard opens.

  3. In step 1, select the Service the SLO will be associated with.

  4. In step 2, select AppDynamics as the data source for your SLO.

    1. Enter the Application Name.

      • The Application Name refers to the name of the logical business application defined in AppDynamics.
      • To ingest Database Metrics, you must enter Database Monitoring in the Application Name field.

    2. Then specify the Metric. You can choose either:

      • A Threshold Metric where a single time series is evaluated against a threshold
      • A Ratio Metric that allows you to enter two-time series to compare. You can choose one of the following metric types:
        • Good Counter, meaning a ratio of good requests and total requests
        • Bad Counter, meaning a ratio of bad requests and total requests
      1. Choose the Data Count Method for your ratio metric:
      • Non-incremental: counts incoming metric values one-by-one. So the resulting SLO graph is pike-shaped.
      • Incremental: counts the incoming metric values incrementally, adding every next value to previous values. It results in a constantly increasing SLO graph.

  5. Configure the metrics for your SLO. The following are query examples:

    1. Threshold metric for AppDynamics:
      Metric Path: End User Experience|App|End User Response Time 95th percentile (ms)

    2. Ratio metric for AppDynamics:
      Metric Path for Good Counter (numerator): End User Experience|App|Very Slow Requests
      Metric Path for Bad Counter (numerator): End User Experience|App|Slow Requests
      Metric Path for Total Counter (denominator): End User Experience|App|Normal Requests

    SLI values for good and total
    When choosing the query for the ratio SLI (countMetrics), keep in mind that the values ​​resulting from that query for both good and total:
    • Must be positive.
    • While we recommend using integers, fractions are also acceptable.
      • If using fractions, we recommend them to be larger than 1e-4 = 0.0001.
    • Shouldn't be larger than 1e+20.

  6. In step 3, define a Time Window for the SLO.

  • Rolling time windows are better for tracking the recent user experience of a service.

  • Calendar-aligned windows are best suited for SLOs that are intended to map to business metrics measured on a calendar-aligned basis, such as every calendar month or every quarter.

  1. In step 4, specify the Error Budget Calculation Method and the expected Objective(s).

  2. In step 5, set the SLO Name and the Alert Policy for your SLO. Optionally, you can mark your SLO with Labels.

  3. When you’re done, click CREATE SLO.

sloctl​

Here’s an example of AppDynamics using a rawMetric (threshold metric)

apiVersion: n9/v1alpha
kind: SLO
metadata:
  name: appdynamics-end-user-response-calendar
  displayName: AppDynamics MyService End User Response Calendar
  project: appdynamics-raw
spec:
  description: 95th percentile of End User Response 1 Week Calendar
  service: appdynamics-myservice-service
  indicator:
    metricSource:
      name: appdynamics-agent
  timeWindows:
    - unit: Day
      count: 7
      calendar:
        startTime: 2020-03-09 00:00:00
        timeZone: Europe/Warsaw
  budgetingMethod: Occurrences
  objectives:
    - displayName: Acceptable
      op: lte
      rawMetric:
        query:
          appDynamics:
            applicationName: "myapp"
            metricPath: "End User Experience|App|End User Response Time 95th percentile (ms)"
      value: 10000
      target: 0.75

Important notes:

Metric specification from AppDynamics has two mandatory fields:

  • applicationName – mandatory, string, Application name, meaning the name of the logical business application defined in AppDynamics.

    • To ingest Database Metrics, you must enter Database Monitoring in the Application Name field.

    For more details, refer to Configuring Agents in Kubernetes | AppDynamics documentation.

    On top of the same validation rules for appDynamics sections as for the rawMetric (threshold metric), there is an additional requirement that all applicationName fields must have the same value within a single SLO.

  • metricPath – mandatory, string, full metric path that can be obtained from AppDynamics Controller UI (dashboard).

    metricPath must refer to a single time series.

    Example: "End User Experience|App|End User Response Time 95th percentile (ms)"

    The list of metrics Full Path and their Application Names can be copied directly from the AppDynamics dashboard.

Querying the AppDynamics server​

The Nobl9 agent leverages the Time Range API parameters. It pulls data at a per-minute interval from the AppDynamics server.

For a more in-depth look, consult additional resources:
WildcardsAppDynamics docsConfiguring Agents in KubernetesAppDynamics docsConfigure Resource URL SegmentsAppDynamics docsAppDynamics ConceptsAppDynamics docsMetric and Snapshot APIAppDynamics docsAgent metricsAgentCreating SLOs via TerraformTerraformCreating agents via TerraformTerraform
Last updated on
On this page