Managing Collectors

Question 1

Service endpoints

Answer 1

provide key performance indicators, metrics, and snapshots, exclusively in the context of that service, omitting business transaction context or downstream performance data

Question 2

Filter endpoints

Answer 2

1. Response time > X
2. Calls/min > X
3. Type: Async / Web Service …
4. Name matches
5. Tier matches
6. Service endpoints with performance data

Question 3

Automatic service endpoint detection

Answer 3

1. Select tiers
2. Type of entry points

Question 4

Type of entry points JAVA

Answer 4

1. Servelet (configure naming)
2. Struts action
3. Web Service
4. POJO
5. Spring Bean
6. EJB
7. JMS (Java message service)

Question 5

Custom service endpoint creation

Answer 5

1. Select tier
2. Select type
3. Agent type
4. Include / exclude rule
5. Priority
6. HTTP request match criteria
7. Split transaction using request data

Question 6

Data collectors

Answer 6

1. used to supplement business transaction and transaction analytics data with application data.
2. shows values of particular parameters or return values for business transactions
3. shows the business context affected by performance issues, such as the specific user, order, or product.
4. data collectors supplement the information shown in transaction snapshots

Question 7

Types of data collectors

Answer 7

1. Method invocation data collectors - Capture code data, such as method arguments, variables, and return values.
2. HTTP data collectors - Capture the URLs, parameter values, headers, and cookies of HTTP messages exchanged in a business transaction.

Question 8

Data collector permission

Answer 8

Configure Diagnostic Data Collectors permission

Question 9

HTTP Data Collectors

Answer 9

1. Name
2. Apply to new BTs
3. Enable data collection for: transaction snapshots / transaction analytics
4. HTTP requests attributes: URL / Session / User Principal
5. HTTP parameters
6. Cookies
7. Session keys
8. Headers