NoSQL analysis monitors all NoSQL database calls made by your EDAS application. Use it to identify slow commands, track call volume trends, and trace individual requests back to the calling service.
NoSQL analysis provides two views:
| View | Purpose |
|---|---|
| Call statistics | Time series charts that show NoSQL call volume and performance over a selected time period. Use these to spot spikes, identify trends, and compare performance across dates. |
| Command list | A breakdown of every NoSQL command your application ran. Drill into a specific command to view its invocation statistics or trace it back to the calling service. |
Limits
NoSQL analysis is available in EDAS Professional Edition and Platinum Edition only. Standard Edition does not support this feature.
Open NoSQL analysis
Log on to the EDAS console.
In the left-side navigation pane, choose Application Management > Applications.
In the top navigation bar, select a region. In the upper part of the page, select a microservice namespace.
From the Cluster Type drop-down list, select Kubernetes Cluster.
Find the target application and click its name in the Application Name column.
In the left-side navigation pane of the application details page, choose Monitor > Instance Details.
In the left-side pane of the Instance Details page, select the instance that you want to inspect, then click the NoSql Analysis tab on the right side.
View call statistics
The Call statistics section displays a time series curve of NoSQL call metrics for the selected time period.
Interact with the charts:
Hover over any data point to view exact values at that timestamp.
Click the
icon to view metrics for a specific time range, or compare the same metric across different dates.
Analyze commands
The command list shows all NoSQL commands that your application ran during the selected time period.
For each command in the list, use the Actions column to:
Click Invocation Statistics to view detailed NoSQL call data for that command.
Click Interface Snapshot to view the traces associated with that command.
For more information about working with traces, see Query traces.