VictoriaMetrics service management via ADCM

Lisa Vaysman

The ADCM UI provides actions to manage the VictoriaMetrics service and its components. For information on how to run service actions, refer to Service actions.

The actions available for the VictoriaMetrics service are listed in the table below.

Action Description

Check

Runs service-specific tests to check the health of the service and its components

Restart

Restarts the service. When you run this action, the option Apply configs from ADCM is available. If it is set to true, all service configurations defined in ADCM settings will be applied during the service restart. Otherwise, the service restarts without applying configurations from ADCM

Start

Starts the VictoriaMetrics service. When you run this action, the option Apply configs from ADCM is available. If it is set to true, all service configurations defined in ADCM settings will be applied at service startup. Otherwise, the service starts without applying configurations from ADCM

Stop

Stops the VictoriaMetrics service

Uninstall

Uninstalls the VictoriaMetrics service. VictoriaMetrics Storage data is not deleted from the host where it was stored (see section VictoriaMetrics → Storage Settings of Configuration parameters)

VictoriaMetrics components actions

The following actions are supported for all VictoriaMetrics components.

Action Description

Restart

Restarts the component on all cluster hosts

Start

Starts the component on all cluster hosts

Stop

Stops the component on all cluster hosts

Restart VictoriaMetrics components

If you need to restart VictoriaMetrics components individually via component actions, trigger their Restart actions in the following order:

  1. Restart the VictoriaMetrics Storage component.

    NOTE

    On large data volumes, the VictoriaMetrics Storage component may take a significant amount of time to restart (see the VictoriaMetrics documentation). Data ingestion and querying are completely unavailable during the restart. Although the VictoriaMetrics Insert and VictoriaMetrics Select components remain running, they cannot process data until the VictoriaMetrics Storage component is up and running.

  2. Restart the VictoriaMetrics Insert component. The restart finishes almost instantly because the component is stateless, so data ingestion stops only for a brief moment.

  3. Restart the VictoriaMetrics Select component. The restart completes almost instantly, so metrics visualization in Grafana is interrupted only for a brief moment.

Found a mistake? Seleсt text and press Ctrl+Enter to report it