AppDynamics switched from Semantic Versioning to Calendar Versioning starting in February 2020 for some agents and March 2020 for the entire product suite.

    Skip to end of metadata
    Go to start of metadata

    Most frequently an instrumented application calls to a message queue as a remote service or backend. However, in cases when an application uses asynchronous message listeners or message-driven beans as the primary trigger for business processing on an originating tier, AppDynamics can intercept the message listener invocations and track them as business transactions.

     AppDynamics discovers the following types of business transaction entry points:

    • Java JMS entry points.
    • .NET Message Queue entry points

    Message queue entry points all have similar naming configuration options for Automatic Transaction Discovery and Custom Match Rules.

    Default Naming

    By default, the AppDynamics auto-detection naming scheme identifies all message queue transactions using the destination name. Otherwise, if the destination name is not available, AppDynamics uses the listener class name.

    Custom Match Rule Options

    When you create a JMS or Message Queue custom match rule, the agent names matching transactions for the custom match rule name. See Custom Match Rules.

    You have the option to specify the following match criteria as a combination of the following entry point properties:

    • The Message Destination as Queue, Topic or Unknown.
    • Message Property. You can match against a property's existence or against a property's value.
    • Message Content.

    • No labels