1.- Go to the CEM UI, verify that the interested page or URL matches a Business Transaction (BT) definition
2.-Verify that the agent is able to monitor the Business Transaction under : <App-hostname> | <Process> | <agent> | Business Segment | <BS> | <BT>
3.- Make sure the below properties have been configured in the IntroscopeAgent.profile:
If Java agent:
Make sure the pages you need to monitor are not being excluded by includeURLsRegex.
If .NET agent:
Changes to the above properties takes effect immediately
4.- Verify that the business transaction match the x-apm-brtm-response-bt-page-<page URL> (for page request) or the x-apm-brtm-response-bt-<uniqueID> cookie (for AJAX request).
In your browser press F12, go to the “Network tab”, open the page you would like to inspect, then click “Cookies” tabs.
Verify that x-apm-brtm-response-bt-page-<you-app-url> is present
In case of Java:
In case of .NET:
If you can't find the cookie, then problem is in inserting the cookie, make sure Cookies are enabled in the browser, see Browser Agent Prerequisites:
a) cookie has already expired :
If Java : increase introscope.agent.browseragent.response.decoration.cookie.expirationTime=3
If .NET: increase introscope.agent.browseragent.responseCookie.expirationTime=3
to some high number, and try again
If Java : open the IntroscopeAgent.profile, set log4j.logger.IntroscopeAgent.BrowserAgent=TRACE#com.wily.util.feedback.Log4JSeverityLevel,logfile
If .NET: open the logging.config.xml, set <level value="DEBUG">, save the IntroscopeAgent.profile so the change in the logging.config.xml is trigger immediately
Reproduce the issue and send the information to CA Support.
5.- Check if POST requests are blocked.