This page applies to an earlier version of the AppDynamics App IQ Platform.
For documentation on the latest version, see the 4.4 Documentation.

On this page:

Related pages:

Your Rating:
54 rates

New in 4.1.4

You can modify automatic backend discovery rules and create custom backend discovery rules.

Modifying Backend Discovery

Modifying backend discovery rules involves specifying different backend naming conventions from the default convention.

This lets you:

  • aggregate similar backends by reducing the number of properties used to name the backend.
  • split backends by increasing the number of properties used to name the backend.

Creating Custom Backend Discovery Rules

Creating custom backend discovery rules allows you to customize identification and names of automatically discovered backends.

If automatic discovery for a backend type is enabled, the agent first processes any custom backend discovery rules for that type and then the automatic backend discovery rules.

If automatic discovery for a backend type is disabled, and one or more custom discovery rules is applied, the agent discovers only backends defined by the custom rules. For example, in this case, if you have a custom discovery rule that matches on “URL contains AppD” and another rule that matches on “Host starts with myHost”,  the agent discovers only backends that match at least one of those criteria. If you have a single custom rule that matches on both “URL contains AppD” and “Host starts with myHost”, the agent discovers only backends that match both of those criteria.

Automatically discovered backends are listed in Python Supported Environments. To enable the Python Agent to discover a backend that is not automatically discovered, use the Python Agent APIs to create a custom exit call. See Python Agent API Reference and Python Agent API Guide.

Accessing Python Backend Detection Rules

  1. In the application, click Configuration > Instrumentation.
  2. Do one of the following:
    • To configure backend detection at the application level, in the left panel of the instrumentation window select the application.
    • To configure transaction detection at the tier level, select the tier for which you want to configure backend detection.
      You can choose to apply the application configuration to the selected tier or to create a custom configuration just for this tier.
  3. Click the Backend Detection tab.
  4. Click the Python tab in the backend detection window

In the Automatic Backend Discovery list, select the backend type that you want to view or modify.

A configuration summary for the selected backend type appears on the right. The Automatic Discovery panel shows which properties the agent uses by default to name the backend. Click Edit Automatic Discovery to modify the naming convention, enable or disable the rule, and (where possible) to enable or disable correlation through the backend to components that are further downstream.

In the Custom <backend type> Discovery Rules panel, click + to create or the pencil icon to modify custom rules for how the Python Agent should discover and name backends of the selected backend type.

Note that the Python Agent does not support getter chains to specify the method on which a match rule is based.