App Agent Node Properties (S)

Set this property to true to hide the sensitive runtime data in the transaction snapshots. Add the filters in the XML format specified in app-agent-config.xml. This node property does not override sensitive filter configuration from app-agent-config.xml.

Example

<sensitive-data-filters>
        <sensitive-data-filter applies-to="environment-variables,system-properties,jmx-mbeans"
                               match-type="CONTAINS"
                               match-pattern="password"/>
    </sensitive-data-filters>

Set this property to true to hide the runtime messages containing sensitive data in the transaction snapshots. Add the filters in the XML format specified in app-agent-config.xml. This node property does not override other node properties.

Example

<sensitive-message-filters>
        <sensitive-message-filter message-type="throwable,logger-message,all"
                                  match-type="EQUALS|CONTAINS|STARTSWITH|ENDSWITH|REGEX"
                                  match-pattern="CASESENSITIVE_PATTERN"
                                  redaction-regex="SENSITIVE_INFO_REGEX_GROUP"/>
     </sensitive-message-filters>

Set this property to true to hide the sensitive URLs in the transaction snapshots. Add the filters in the XML format specified in app-agent-config.xml. This node property does not override sensitive filter configuration from app-agent-config.xml.

Example

<sensitive-url-filters>
        <sensitive-url-filter delimiter="/"
                                  segment="2,3"
                                  match-filter="EQUALS|INLIST|STARTSWITH|ENDSWITH|CONTAINS|REGEX|NOT_EMPTY"
                                  match-pattern="pattern"
                                  param-pattern=""/>
    </sensitive-url-filters>

For the call graphs captured on this node, show the specified packages or class names in addition to the ones configured in the global call graph configuration. Does not need a restart.

The value in milliseconds for the deviation from the current average response time. This setting is used for evaluation of slow in-flight transactions. Also, see the slow-request-threshold property for more details.

In-flight requests are checked for slowness in the interval specified by this property. The value is specified in milliseconds.

In-flight requests taking more time than this threshold (in ms) with a deviation greater than the slow-request-deviation property from the current average response time are monitored to capture hot spots.

Use this property to enable NetViz monitoring of .NET and Java applications.

Use this property to enable or disable OOTB BT Detection for Spring Batch.

Use this property to specify the class and method you have identified as suitable POJO entry points for Spring Integration.

Based on the MessageHandler interface, the App Agent for Java by default automatically discovers exits for all channels except DirectChannel. In cases where a lot of application flow happens before the first MessageHandler is executed,

• Set enable-spring-integration-entry-points=false
• Configure suitable POJO entry points,
• Declare each suitable POJO entry point class/method in this property spring-integration-receive-marker-classes

If the application code polls for messages in a loop, the span of each loop iteration is tracked as a transaction. Tracking begins when the loop begins and end it when the iteration ends. To safeguard against cases where pollableChannel.receive() is not called inside a loop, specify this property for each class/method combination that polls messages in a loop.

After setting this property, restart the application server for changes to this property to take effect.

Examples

For example, to enable tracking for the following:

class MessageProcessor
{
void process()
{
   while(true)
   {
          Message message = pollableChannel.receive()
   }
}
}

set this property as follows:

spring-integration-receive-marker-classes = MessageProcesser/process

See also Spring Integrationサポート.

Register this node property to modify the naming scheme for Spring MVC transactions. Bean ID cannot be used as a global naming type. Use the bean ID and method name for global.