MongoDB Exit Points
| Name of the Exit Point | Type | Class Match Criteria | Class / Interface / Superclass / Annotation Name | Method Name | Splitting Config / Custom Exit Point Identifier | Snapshot Data Operation on Invoked Object | |
|---|---|---|---|---|---|---|---|
| Collect Data From | Getter Chain Operation on Invoked Object | ||||||
|
MongoDB.Insert |
JDBC |
With a class name that |
com.mongodb.DBCollection | insert |
Invoked Object | getDB().getName() |
Parameter_0.toString() |
|
MongoDB.Find |
JDBC |
With a class name that |
com.mongodb.DBCollection | find |
Invoked Object | getDB().getName() |
Parameter_0.toString() |
|
MongoDB.Update |
JDBC |
With a class name that |
com.mongodb.DBCollection | update |
Invoked Object | getDB().getName() |
Parameter_0.toString() |
|
MongoDB.Remove |
JDBC |
With a class name that |
com.mongodb.DBCollection | remove |
Invoked Object | getDB().getName() |
Parameter_0.toString() |
|
MongoDB.Apply |
JDBC |
With a class name that |
com.mongodb.DBCollection | apply |
Invoked Object | getDB().getName() |
Parameter_0.toString() |
Note: Avoiding high overhead Cisco AppDynamics recommends that you avoid instrumenting highly-used methods, such as the find() method, because the activity around these methods can cause an undesired amount of overhead on the system.