Performance metrics

Once you've received access to your Operational Dashboards, you'll see different sections that give visibility to requests made by your app to various PubNub APIs. Read on to understand how to interpret each metrics section on your static dashboard.

Summary

This section provides an overview of the last hour’s traffic. You can see the number of requests received in the previous hour, a breakdown of requests via region, and a graph that shows the total requests per five-minute interval.

The charts on top allow you to see how your requests are distributed across PubNub data centers and see your app usage by API over the last hour.

At the bottom, there is a graph that compares the current hour's requests against the same time period as the day before, a view that shows the max requests per second for the top 5 APIs that were called in the last hour, and the number of clients that disconnected every five minutes during the previous hour.

Client errors

This section provides insights to determine if your application is working correctly. It gives a count of API calls that resulted in a 4XX (error) response code and the percentage of API calls that returned an error.

The two tables break the 4XX responses into two categories.

• The table on the left shows all non-403 error response codes. Typically these types of responses are caused by invalid API calls, so you may wish to see if there are any clients with coding errors in them.
• The table on the right shows 403 “Not Authorized” errors. If you use Access Manager in your app, this may indicate an error in the logic that is used to provide clients with appropriate tokens or it might mean that unauthorized users are attempting to make API calls using their keys.

Messaging

This section provides call count details for each of the messaging API and shows a graph of successful API requests per five-minute interval for each of the APIs.

Presence, Access Manager, and channels

This section provides details on Presence, Access Manager, and channel group usage. The first graph shows the count of Presence calls to the hereNow, and whereNow endpoints, along with any Presence heartbeat calls. The second graph shows the count of Access Manager token grants (for users of the Access Manager v3 API). The last table provides the count of calls to APIs that manage channel groups: addChannels, listChannels, and removeChannels.

Server errors

This graph provides a count of API calls that returned a 5XX (server error) response code. If you see multiple 5XX errors, you may wish to contact support or check our platform status board as this may indicate the platform is currently operating at less than 100% efficiency.

Functions

View availability

This view is provided in the operational metrics dashboard, but not available through the export offer.

If you configured your keyset with functions, this section can help you monitor their behavior.

The first table provides the count of function executions triggered by a publish event or a call to the function’s public URL. The second table shows the number of outbound XHR requests performed in the functions. The final table shows the errors that occurred in the functions.

If you see errors in your functions, you may inspect either the functions' code or any endpoints to which the functions make XHR requests to ensure they are working as expected. Some functions return errors by design, so depending on your function logic, errors on this table may or may not be a cause for concern.

Push notifications

View availability

This view is provided in the operational metrics dashboard but not available through the export offer.

If you configured your keyset with push notifications, this section can help you monitor their behavior.

The first graph shows a count of attempts that the PubNub service made to send push requests. The second two graphs show the number of errors returned by the Apple and Android notification service platforms.

Errors are typically due to improper token configuration. You may wish to check their logic and ensure that the tokens you have configured PubNub with are valid and non-expired.