When your application makes NoSQL calls, you can use Application Real-Time Monitoring Service (ARMS) Application Monitoring to track and analyze these calls. The NoSql Analysis tab presents NoSQL call data in two sections:
Call statistics: Time series charts that show NoSQL data over a selected time period.
Command list: A table of individual NoSQL commands with drill-down access to per-command statistics and traces.
Use the call statistics to spot performance trends or anomalies, and the command list to isolate specific slow or high-frequency commands.
Prerequisites
Before you begin, make sure that the application is monitored by Application Monitoring. For more information, see Overview.
Open the NoSql Analysis tab
Log on to the ARMS console. In the left-side navigation pane, choose Application Monitoring > Applications.
On the Applications page, select a region in the top navigation bar and click the name of the application that you want to manage.
If the
icon is displayed in the Language column, the application is connected to Application Monitoring. If a hyphen (-) is displayed, the application is connected to Tracing Analysis.In the left-side navigation pane, click Application Details.
On the Application Details page, select an application instance, set the time period, and then click the NoSql Analysis tab.
Call statistics
The Call statistics section displays a time series curve for the NoSQL data of your application within the selected time period.
To explore the data:
Hover over a chart to view detailed statistics at that point in time.
Click the
icon to view metric statistics for a specific time period or compare the same metric across different dates.Click the
icon to view the API details of a metric.
Command list
The Command list section lists all NoSQL commands executed by the application within the selected time period.
Each command supports the following actions:
| Action | Description |
|---|---|
| Invocation Statistics | View the NoSQL data of a specific command. |
| Interface Snapshot | View traces of a specific command. |
To diagnose a slow command, click Invocation Statistics to review its call data, and then click Interface Snapshot to drill down into individual traces. For more information about traces, see Query traces.