APM CE (CEM) Defects FAQ

Document ID : KB000019297
Last Modified Date : 14/02/2018
Show Technical Document Details


Various questions and answers about APM CE (CEM) Defects.


How often are user defects reported by APM CE (CEM)?

Defects are shown in the CEM>Incident Management> Defects screen in real time.

APM CE automatically rolls up defects into impact events (Incidents). Can I see a defect before it is part of an event?

Yes, that is the purpose of the Defects screen. The default menu option of Defects without Incident to see the defect.

I know that a defect was generated but I am not seeing it. What can I do?

Go to the Defects screen and select All Defects instead of the default Defects without incidents

I see something in the logs called BizEvent. What is this?

Just another name for an APM CE Incident

How does the "search defects by username" feature work?

You can search for all the Defects associated with a user by login name or any combination of first and last name. Wildcards are supported so that Joh* Doe will match John Doe, Johnny Doe, Johnson Doe, etc.

What is the maximum time I can expect to wait between a user having a slow response time defect and that user's username appearing in such a search?

This usually appears within seconds not minutes. The speed of appearance may be release-dependent. One can change this value in a configuration file rather than the APM CE UI.

The downside to a shorter time is increased communications overhead.

Under what circumstances does a transaction generate an Incomplete Transaction defect?

In CEM, there is no defect named "Incomplete Transaction," but there are several defects showing the equivalent where not all of the required components are delivered:

  • Missing response defect: The request to the web server is observed, but no response is received from server.

  • Partial response defect: The request to the web server is observed, but only a partial response is received, based on the content length field in the HTTP response header.

  • Missing component: A transaction is defined as having X components and Y of them are marked as non-cacheable. The first component of the transaction is observed, but one of the Y components is missing.

  • Missing transaction: A business transaction has been defined as having N transactions, with M transactions marked as non-cacheable. The first transaction is observed, and one of the M transactions is missing.