Studio captures metrics logging, including all log entries from the com.endeca.portal.instrumentation classes.
bdd-studio-metrics.log, which is in Log4j format.bdd-studio-metrics-odl.log, which is in ODL format.Both metrics log files are created in the same directory as bdd-studio.log.
| Column Name | Description |
|---|---|
| Total duration (msec) | The total time for this entry (End time minus Start time). |
| Start time (msec since epoch) | The time when this entry started.
For Dgraph Gateway queries and server executions, uses the server's clock. For client executions, uses the client's clock. |
| End time (msec since epoch) | The time when this entry was finished.
For Dgraph Gateway queries and server executions, uses the server's clock. For client executions, uses the client's clock. |
| Session ID | The session ID for the client. |
| Page ID | If client instrumentation is enabled, the number of full page refreshes or actions the user has performed. Used to help determine how long it takes to load a complete page.
Some actions that do not affect the overall state of a page, such as displaying attributes on the Available Refinements panel, do not increment this counter. |
| Gesture ID | The full count of requests to the server. |
| Portlet ID | This is the ID associated with an individual instance of a component.
It generally includes:
For example, if a page includes two Chart components, the ID can be used to differentiate them. |
| Entry Type | The type of entry. For example:
|
| Miscellaneous | A URL encoded JSON object containing miscellaneous information about the entry. |