2 Replies

You should not be required to manually place sensors in the processes calling this 'observed tier'. OOTB Auto sensors should detect any request coming out of an instrumented tier. You will, however, have to define your observed tier in terms of either hostname/IP address, host:port, or JMS destination (queue name). Then AppMon can associate those requests with the observed tier.

We were trying to add a 'Load Balancer' as an observed tier and followed the documented instructions but LB isn't appearing in the transaction flow, we tried almost all the 'Match' and 'Patterns' combinations.

When we enabled the 'W3C Resource Timing' to capture resource information then we found the 'LB' as First Party Content.

One more information required about the 'Service Name' and 'Instance Name' whether we can use any meaningful name or there is some specific information required for both.

The service name is a user-chosen identifier string that becomes the caption of all collected calls in the transaction flow.

The instance name is also a user-chosen identifier string, but with some special features. It can be filled with captured arguments and return values, the method name and the service name.

How to configure the proper rule to show the 'LB' in the transaction flow?