AppDynamics Application Intelligence Platform

3.8.x Documentation



Release Notes

Skip to end of metadata
Go to start of metadata

To review general information about monitoring databases and remote services (collectively known as backends) and for an overview of backend configuration see Backend Monitoring.

Types of Exit Points

Each automatically discovered backend type has a default discovery rule and a set of configurable properties. See the following:

For information on All Other Traffic transactions, see Backend Monitoring.


View the Discovery Rules

To view the discovery rules for an automatically discovered backend, access the backend configuration screen using these steps:

1. Select the application.
2. In the left navigation pane, click Configure -> Instrumentation.
3. Select the Backend Detection tab.
4. Select the application and the tab corresponding to your agent platform (Java, .NET, PHP).

The Automatic Backend Discovery default configurations for that agent are listed.

5. In the Automatic Backend Discovery list, click the backend type to view.
A summary of the configuration appears on the right. For example, the following figure shows that JMS backends are auto-discovered using the Destination, Destination Type, and Vendor.

Revise Backend Discovery Rules

If the default settings don't give you exactly what you need, you can refine the configuration in the following ways:

  • Change the default discovery rules:
    • Enable or disable one or more of the properties
    • Use one or more specified segments of a property
    • Run a regular expression on a property
    • Execute a method on a property

The precise configurations vary according to the backend type. These general features are configurable:

  • Discovery Enabled - You can enable and disable automatic discovery for the backend type. Undiscovered backends are not monitored.
  • Correlation Enabled - You can enable and disable correlation. Correlation enables AppDynamics to tag, trace, and learn about application calls to and through the backend to other remote services or tiers. For example, if a call is made from Tier1 -> Backend1 -> Tier2, Tier2 knows about the transaction flow because the agent "tags" the outbound call from Backend1 to identify it as related to the same transaction that called Backend1 from Tier1. If you do not care about activity downstream from the backend, you may want to disable correlation.
  • Backend Naming - You can configure how backends are named.

Change the Default Discovery Rules

When you need to revise the default set of discovery rules, in many cases, you can achieve the visibility you need by making adjustments to the default automatic discovery rules. For some scenarios, you might want to disable some or all of the default rules and create custom rules for detecting all your backends. AppDynamics provides flexibility for configuring backend detection.

For example, detection of HTTP backends is enabled by default. In Java environments, HTTP backends are identified by the host and port and correlation with the application is enabled. To change the discovery rule for HTTP backends in some way, such as disabling correlation, omitting a property from the detected name, or using only certain segments of a property in the name, you edit the HTTP automatic discovery rule. 

Review the rules for each exit point to determine the best course of action for your application if the default discovery rules do not give the results you need for your monitoring strategy.

To change default backend automatic discovery rules

1. From the left-hand navigation panel, select Configure -> Instrumentation. Then select the Backend Detection tab and the application or tier you want to configure.

2. In the Automatic Backend Discovery list, select the backend type to modify.
The rule summary appears in the Automatic Discovery panel on the right.

3. Click Edit Automatic Discovery.
The Edit Automatic Backend Discovery Rule window appears.

4. For each property that you want to configure:

  • Select the property in the property list.
  • Check the property check box to use the property for detection; clear the check box to omit it.
  • If you are using the property, choose how the property is used from the drop-down list.

  • If you have a complex property, such as the URL, destination, or a query string, and you want to eliminate some parts of it or need some additional  manipulation you can use an option from the second drop-down list such as Run a Regular Expression on it or Execute methods on it (getter chain). Each option has associated configuration parameters. For example, you have options for manipulating the segments of the URL.

5. Check Enabled to enable the rule; clear the check box to disable it.

6. Check Correlation Enabled to enable correlation.

7. Click OK.

Add Backend Discovery Rules

AppDynamics provides the additional flexibility to create new custom discovery rules for the automatically discovered backend types. Custom rules include the following settings:

  • Name for the custom rule.
  • Priority used to set precedence for custom rules.
  • Match Conditions used to identify which backends are subject to the custom naming rules.
  • Backend Naming Configuration used to name the backends matching the match conditions.

The window for adding custom discovery rules looks like this:

To create a custom discovery rule for an automatically discovered backend type, use these steps:

1. In the Automatic Backend Discovery list, select the backend type.
The Custom Discovery Rules editor appears in the right panel below the Automatic Discovery panel.

2. Click Add (the + icon) to create a new rule or select an existing rule from the list and click the edit icon to modify one.

3. Enter a name for the custom rule.

4. Confirm the settings for Enabled and Correlation Enabled (if applicable).

4. Enter the priority for the custom rule compared to other custom rules for this backend type. The higher the number, the higher the priority. A value of 0 (zero) indicates that the default rule should be used.

5. In the next section, configure the match conditions.
Match conditions are used to identify which backends should use the custom rule. Backends that do not meet all the defined match conditions are discovered according to the default rule. 

7. In the next section, configure the naming for the backends matching the rule. The naming configuration must include the property used by the match condition.

8. Save the configuration.
See specific exit points for examples.

Add Custom Exit Points

When your application has backends that are not automatically discovered, you can enable discovery using custom exit points. To do this, you need to know the class and method used to identify the backend. See Configure Custom Exit Points for Java.

Propagate Changes to Other Tiers or Applications

When you have made changes to the backend detection rules, you may want to propagate your changes to other tiers or applications.

To copy an entire backend detection configuration to all tiers 

1. Access the backend detection window. See View the Discovery Rules.

2. In the left panel select the application or tier whose configuration you want to copy.

3. Click Configure all Tiers to use this Configuration.

To copy an entire backend detection configuration to another tier or application 

1. Access the backend detection window. See View the Discovery Rules.

2. In the left panel select the application or tier whose configuration you want to copy.

3. Click Copy.

4. In the Application/Tier browser, choose the application or tier to copy the configuration to.

5. Click OK.

Learn More

  • No labels