Monitoring#

General information#

The monitoring service allows you to monitor in real time the parameters of instances, volumes, Auto Scaling groups and buckets. By creating alarms, you can setup automatic actions when parameters of a monitored resource fall beyond the pre-defined range.

You can configure monitoring of specific resources via the web interface in the Monitoring section. In the monitoring service, there are two main types of entities: alarms and metrics. Accordingly, the main menu contains two subsections: Alarms and Metrics.

Note

In addition to the web interface, you can also use CloudWatch API to handle metrics and alarms.

Available quotas#

The following default quotas are allocated for the monitoring service:

  • 100 alarms per project in each region;

  • 10 dimensions per an alarm;

  • 5 alarm actions;

  • 5,000 stored alarm records per a project.

Alarm history records and metric values are saved for seven days. Bucket metrics are collected once an hour. The remaining metrics are collected once per minute.

If necessary, you can increase quotas. To do this, contact the support service via the support portal or by email support@k2.cloud.

Access rights#

All users from the InstanceAdministrators group get access to the Monitoring service automatically. If necessary, you can create a separate policy or group to work with the service (or add the respective privilege to the groups or policies you created) and assign it to a user.

To create a policy, go to the Policies subsection in the IAM section, click Create, and select the monitoring service actions allowed for it. You can also use predefined policies CloudWatchFullAccess and CloudWatchReadOnlyAccess . The former grants all permissions to work with the service, while the latter provides read-only access. Then, if necessary, create a group and add the created policy to the group.

For more details on working with groups and policies, see IAM documentation.