Skip to main content

1C server cluster monitoring

Last update:

In cloud ready 1C, you can monitor the status of the cluster.

For more detailed analysis, some metrics can be viewed as graphs in the dashboard:

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

The time in the control panel corresponds to the time set on your device and is independent of the region where the cluster is hosted.

note

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

View 1C server cluster metrics

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

Cluster metrics in the dashboard

vCPUCluster node utilization in percentage or number of nodes
MemoryOccupied memory without cache and temporary data in percent or megabytes
DiskUsed disk space in percent or gigabytes. It takes into account the part of disk space reserved for service needs and not available for database placement
BandwidthThe amount of data that is received (Egress) or transmitted (Ingress) over the network link in kilobytes per second

Export metrics in Prometheus format

Historical information for clusters is not available - metrics are collected once a minute. The list of all metrics supported in 1C server clusters and their description can be viewed in the Metrics table in Prometheus format.

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

1. Get a token

The token gives access to metrics for all project clusters and databases in a single pool.

  1. In the control panel, in the top menu, click Products and select 1C Ready 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. Copy the token. To do this, click in the token line.

2. Get metrics in Prometheus format

  1. Add 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 to call the API. This is the part of the URL without https:// for example metrics.ru-9.1c.selcloud.ru. You can copy it in control panel: in the top menu click Products and select Ready 1C Cloud → 1c Server Clusters → Cluster page → tab Monitoring → in the block Tokens for Prometheus click next to the URL;
    • <token> - the token that you copied in step 5 when you token that you copied in step 5 when you received the token in step 1.

  2. Open a page in your browser where Prometheus-formatted metrics will be available:

    http://<ip_address>:9090/targets

    Specify <ip_address> - the IP address where Prometheus is installed.

  3. Self-configure monitoring and alerts for a cluster of 1C servers.

Metrics in Prometheus format

Metrics in Prometheus format are provided for all clusters of the project. A specific cluster can be found by 1C cluster identifier in the cluster_id label.

go1c_cluster_infoInformation about the cluster
go1c_cluster_config_infoInformation about static cluster settings
go1c_cluster_maintenance_timestamp_secondsA timestamp (Unix) of the last or upcoming cluster maintenance. Status indicates the status of the maintenance
go1c_cluster_proxy_infoInformation about the proxy configuration of the cluster
go1c_cluster_cpu_usage_coresNumber of CPUs in use per cluster node
go1c_cluster_cpu_limit_coresConfigured limitation of the number of CPUs per cluster node
go1c_cluster_memory_usage_bytesCurrent utilization of the working memory set 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 used CPUs by process on the cluster node
go1c_cluster_proc_open_filedescNumber of file descriptors by process on the cluster node
go1c_cluster_proc_num_threadsNumber of threads of all processes on the cluster node
go1c_cluster_proc_thread_cpu_usage_coresNumber of utilized CPUs by process and thread subset on the cluster node
go1c_cluster_proc_resident_memory_bytesRAM utilization in bytes by process on the cluster node
go1c_cluster_proc_virtual_memory_bytesVirtual memory utilization in bytes by process on the cluster node
go1c_cluster_network_receive_bytes_rateNetwork data acceptance rate in bytes per second per cluster node
go1c_cluster_network_transmit_bytes_rateNetwork data transfer rate in bytes per second per cluster node
go1c_cluster_network_receive_packets_rateNumber of received network packets per cluster node
go1c_cluster_network_transmit_packets_rateNumber of network packets transmitted per cluster node
go1c_cluster_network_receive_packets_dropped_rateNumber of unreceived network packets per cluster node
go1c_cluster_network_transmit_packets_dropped_rateNumber of untransmitted 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_rateRead speed from the file system 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: e.g. 1CV8, WebClient and others
go1c_cluster_session_infoInformation about the active session: user, application and session ID
go1c_cluster_licensesTotal number of licenses per cluster
go1c_cluster_seatsTotal number of client licenses or workstations 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_cluster_health_issues1C cloud ready problem indication
go1c_cluster_session_cpu_time_totalCPU time consumption by server calls within one session in seconds
go1c_cluster_session_memory_bytesThe difference between the occupied memory and the free memory from threads that have been executing requests since the beginning of the session, in bytes
go1c_cluster_session_callsTotal number of server calls during the session
go1c_cluster_session_server_time_secondsTotal duration of server calls during the session in seconds
go1c_cluster_session_write_bytesAmount of data written to disk since the beginning of the current call, in bytes
go1c_cluster_session_read_bytesAmount of data read from the disk since the start of the session, in bytes
go1c_cluster_session_dbms_time_secondsTotal duration of database calls since the beginning of the first call in seconds
go1c_cluster_session_dbms_transmitted_bytesAmount of data transferred between the 1C server and the database since the beginning of the session, in bytes