Real User Monitoring (RUM) resources that use the pay-as-you-go billing method are subject to overdue payment rules. This topic describes how an overdue payment is determined, how it affects your applications and monitoring data, how to settle an overdue payment, and how to avoid a service suspension.
Overdue payment criteria, notifications, and impact
With the pay-as-you-go billing method, your payment becomes overdue if your account balance is insufficient for the deduction and you do not settle the amount on the same day.
On the day of the failed deduction, ARMS notifies you by email, text message, or internal message.
After a payment becomes overdue, Real User Monitoring stops receiving data. Your applications and existing data are not deleted.
Settle an overdue payment
Settle an overdue payment promptly to keep the gap in your monitoring data short. Log on to Expenses and Costs and settle the overdue amount. Real User Monitoring starts receiving data again automatically after you settle the overdue payment.
Reaching the daily write limit of a usage quota also stops Real User Monitoring from receiving data. If data is still missing after you settle the overdue payment, check your quota configuration as described in Set a usage quota.
Avoid a service suspension
Real User Monitoring offers the following safeguards, which are complementary rather than alternatives. A low balance alert tells you when to top up your account. A usage quota caps the volume of data that Real User Monitoring receives each day, so that a traffic spike cannot consume your balance unexpectedly. As a best practice, configure both a low balance alert and a usage quota.
Set a low balance alert
Log on to Expenses and Costs.
On the Account Overview page, set a low balance alert.
If your available balance falls below the alert threshold, the system sends you a text message.
Set a usage quota
Log on to the ARMS console.
Go to the Real User Monitoring > Usage Statistics page and click Configure Quota.
In the dialog box that appears, configure the parameters described in the following table.
| Parameter | Description |
| Write limit | The maximum data volume that can be written to Real User Monitoring each day. |
| On quota reached | Specifies what happens after the write limit is reached. Automatically stop the application and restart it at 00:00 the next day: Real User Monitoring immediately stops receiving data for the corresponding service and region, and starts receiving data again automatically at 00:00 the next day. Select this option when monitoring continuity matters more than strict cost control. Automatically stop the application and do not restart it the next day: monitoring stays off until you resume data reporting manually. Real User Monitoring immediately stops receiving data for the corresponding service and region and does not start receiving data again automatically. Select this option when cost control is a hard constraint. |
| Usage alert threshold | Sends an alert notification after the written data volume reaches the specified percentage of the write limit. |
| Notification Recipient | For information about how to create a notification recipient, see Notification Contacts. |
| Notification period | Alert notifications are sent only during the specified period. |
If you selected Automatically stop the application and do not restart it the next day, use the following steps to make Real User Monitoring receive data again:
Go to the Real User Monitoring > Application List page.
Choose
> Application start-stop to the right of the application.In the dialog box that appears, enable monitoring.