Skip to main content

Monitoring an 1C server cluster

Last update:

In a ready-to-use 1C cloud, you can monitor the cluster status.

For a more detailed analysis, some metrics can be viewed as charts in the control panel:

A full set of available metrics can be exported in Prometheus format.

The time in the control panel matches the time set on your device and does not depend on the region where the cluster is hosted.

note

For example, you created a cluster in Novosibirsk, in the ru-8 pool. The device from which you accessed the control panel is set to the Moscow time zone. The time on the metrics charts will be displayed in the Moscow time zone.

Viewing 1C server cluster metrics

  1. In the control panel, on the top menu, click Products and select 1C Managed Cloud.
  2. Go to the 1C Server Clusters section.
  3. Open the cluster page → Monitoring tab.
  4. Optional: in the Cluster monitoring block, filter metrics by date.
  5. View the available cluster metrics.

Cluster metrics in the control panel

vCPUCluster node core utilization as a percentage or by count
MemoryMemory used excluding cache and temporary data, as a percentage or in megabytes
VolumeDisk space used as a percentage or in gigabytes. This takes into account the disk space reserved for administrative purposes and unavailable for databases
BandwidthAmount of data received (Egress) or transmitted (Ingress) over the network channel in kilobytes per second

Export metrics in Prometheus format

Historical information for clusters is not available — metrics are collected once per minute. A list of all metrics that are supported in 1C server clusters, and their descriptions, can be viewed in the Metrics in Prometheus format table.

  1. Get a token.
  2. Get metrics in Prometheus format.

1. Get a token

The token provides access to the metrics of all clusters in a project and databases in one pool.

  1. In the control panel, on the top menu, click Products and select Managed 1C Cloud.

  2. Go to the 1C Server Clusters section.

  3. Open the cluster page → Monitoring tab.

  4. In the Tokens for Prometheus block, click Create. The token will be generated automatically.

  5. In the token row, click and save it.

2. Get metrics in Prometheus format

  1. Add the following to the Prometheus configuration file:

    scrape_configs:
      - job_name: get-metrics-from-1c
        scrape_interval: 1m
        static_configs:
          - targets:
            - '<domain>'
        scheme: https
        authorization:
          type: Bearer
          credentials: <token>

    Specify:

    • <domain> — the domain for API requests. This is the URL part without https://, for example, metrics.ru-9.1c.selcloud.ru. It can be copied in the control panel: in the top menu, click Products → Managed 1C Cloud → 1C Server Clusters → cluster page → Monitoring tab → in the Tokens for Prometheus block, click next to the URL;
    • <token> — the token you saved in step 5 when getting the token in step 1.

  2. Open the page in your browser where metrics in Prometheus format will be available:

    http://<ip_address>:9090/targets

    Specify <ip_address> — the IP address of the server where Prometheus is installed.

  3. Set up monitoring and alerts for the 1C server cluster yourself.

Metrics in Prometheus format

metrics in Prometheus format are provided for all project clusters. a specific cluster can be found by its 1C cluster ID in the cluster_id label.

You can use a preconfigured dashboard template in Grafana.

go1c_cluster_infoCluster information
go1c_cluster_config_infoInformation on static cluster configuration
go1c_cluster_maintenance_timestamp_secondsUnix timestamp (Unix) of the last or upcoming cluster maintenance. The status reflects the maintenance state
go1c_cluster_proxy_infoInformation on the cluster proxy configuration
go1c_cluster_cpu_usage_coresNumber of CPUs used per cluster node
go1c_cluster_cpu_limit_coresConfigured CPU limit per cluster node
go1c_cluster_memory_usage_bytesCurrent working set memory usage in bytes per cluster node
go1c_cluster_memory_limit_bytesConfigured memory limit in bytes per cluster node
go1c_cluster_disk_usage_bytesCurrent disk usage in bytes per cluster node
go1c_cluster_disk_capacity_bytesTotal disk size in bytes per cluster node
go1c_cluster_proc_cpu_usage_coresNumber of CPUs used by processes per cluster node
go1c_cluster_proc_open_filedescNumber of file descriptors by processes per cluster node
go1c_cluster_proc_num_threadsNumber of threads for all processes per cluster node
go1c_cluster_proc_thread_cpu_usage_coresNumber of CPUs used by processes and thread subgroups per cluster node
go1c_cluster_proc_resident_memory_bytesRAM usage in bytes by processes per cluster node
go1c_cluster_proc_virtual_memory_bytesVirtual memory usage in bytes by processes per cluster node
go1c_cluster_network_receive_bytes_rateNetwork data receive rate in bytes per second per cluster node
go1c_cluster_network_transmit_bytes_rateNetwork data transmit rate in bytes per second per cluster node
go1c_cluster_network_receive_packets_rateNumber of network packets received per cluster node
go1c_cluster_network_transmit_packets_rateNumber of network packets transmitted per cluster node
go1c_cluster_network_receive_packets_dropped_rateNumber of dropped received network packets per cluster node
go1c_cluster_network_transmit_packets_dropped_rateNumber of dropped transmitted network packets per cluster node
go1c_cluster_fs_reads_rateNumber of file system read operations per second (IOPS) per cluster node
go1c_cluster_fs_writes_rateNumber of file system write operations per second (IOPS) per cluster node
go1c_cluster_fs_read_bytes_rateFile system read rate in bytes per second per cluster node
go1c_cluster_fs_write_bytes_rateFile system write rate in bytes per second per cluster node
go1c_cluster_sessionsTotal number of 1C sessions by application type: for example, 1CV8, WebClient and others
go1c_cluster_session_infoInformation about an active session: user, application, and session ID
go1c_cluster_licensesTotal number of licenses per cluster
go1c_cluster_seatsTotal number of client licenses or seats for activated licenses
go1c_cluster_activated_license_infoInformation about activated licenses: type, number, and product
go1c_cluster_1c_rnmgr_infoInformation about the rnmgr process: process ID, host, and port
go1c_cluster_1c_rphost_infoInformation about the rphost process: process ID, host, port, and status
go1c_cluster_1c_process_available_performanceAvailable performance of the rphost process
go1c_cluster_1c_process_connectionsCurrent number of active connections to the rphost process
go1c_cluster_1c_process_connections_per_appCurrent number of active connections to the rphost process, grouped by application type
go1c_cluster_1c_process_memory_excess_duration_secondsDuration in seconds during which the process exceeded the allowed memory usage
go1c_health_issuesIndication of 1C Managed Cloud issues. If the metric is missing, the Managed Cloud is operating correctly
go1c_cluster_session_cpu_time_totalCPU time consumed by server calls within a single session, in seconds
go1c_cluster_session_memory_bytesDifference in bytes between used memory and memory freed by threads executing requests since the beginning of the session
go1c_cluster_session_callsTotal number of server calls during a session
go1c_cluster_session_server_time_secondsTotal duration of server calls during a session, in seconds
go1c_cluster_session_write_bytesVolume of data written to disk since the start of the current call, in bytes
go1c_cluster_session_read_bytesVolume of data read from disk since the beginning of the session, in bytes
go1c_cluster_session_dbms_time_secondsTotal duration of database calls since the first call, in seconds
go1c_cluster_session_dbms_transmitted_bytesVolume of data transferred between the 1C server and the database since the beginning of the session, in bytes