Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Manage Time Series Database Settings

You can use the Paragon Automation GUI to configure the time series database (TSDB) settings.

To configure TSDB settings:


Selecting, deleting, or dedicating TSDB nodes must be done during a maintenance window because some services will be restarted and the Paragon Automation GUI will likely be unresponsive.

  1. Select Configuration > Insights Settings.

    The Insights Settings page appears.

  2. Click Time Series Database.

    The TSDB Settings tabbed page appears.

  3. From the TSDB Settings tabbed page, you can:
    1. Select one or more nodes (from the TSDB Nodes list) to be used as TSDB nodes.

      (The TSDB Nodes list displays the available nodes in the Paragon Automation installation that you can select as TSDB nodes. By default, Paragon Automation automatically selects one node as a TSDB node.)

    2. Set the replication factor by typing a value (or by using the arrows to specify a value) in the Replication Factor text box.

      (The replication factor determines how many copies of the database are needed. The replication factor is set to 1 by default.)

    3. Dedicate nodes as TSDB nodes by clicking the Dedicate toggle to turn it on.

      A TSDB node might have more than one microservice running. However, when you dedicate a node as TSDB node, it runs only the TSDB microservice, and stops running all other microservices.

      • If the node is associated to a persistent volume (storage in a cluster), then you cannot use that node as a dedicated TSDB node.

      • A fail-safe mechanism ensures that you cannot dedicate all Paragon Automation nodes as as TSDB nodes.

    4. Ignore system errors (when you remove or replace a failed TSDB node from Paragon Automation) by clicking the Force toggle to turn it on.

      For example, when a TSDB node fails and the replication factor for that node is set to one, the TSDB data for that node is lost. In this scenario, the failed TSDB node must be removed from Paragon Automation. However, when you try to replace the failed node with a new node, the backup of the node fails with a system error because the replication factor was set to one. If you want to proceed with replacing the node, you must turn the Force toggle on.

    5. Delete a node that was previously assigned as a TSDB node by clicking X next to the name of the TSDB node.

      The node is removed as a TSDB node when you deploy the new configuration changes.

  4. Do one of the following:
    • Click Save to only save the configuration changes to the database without applying the changes to the TSDB nodes.

      You must commit (or rollback) the configuration changes later. For more information, see Commit or Roll Back Configuration Changes in Paragon Insights.

    • Click Save & Deploy to save configuration changes to the database and to apply the changes to the TSDB nodes.

  5. In the pop-up that appears, click OK to confirm.

    You are returned to the TSDB Settings tabbed page.

Adjust Memory Allocation for TSDB Nodes

By default, all InfluxDB pods are capped at 12-GB memory. You can adjust the memory allocation on InfluxDB during the installation of the Paragon Automation cluster, or in the healthbot namespace, or while adding TSDB nodes.


Choose one of the following options to increase the memory limit.

  • During Installation

    During installation of your Paragon Automation cluster, manually edit the config.yml file to increase the memory limit, before you run the deploy command to deploy the cluster. Edit the memory_default_max parameter to add the memory limit. For example to cap the memory to 16-GB, edit the config.yml to include memory_default_max: 16Gi. Note that editing the config.yml will affect all pods.

  • In the healthbot namespace

    Edit the default limit on the healthbot namespace.

    1. Restart the InfluxDB pod for the limit to take effect.

    Note that, the new memory limit will take effect on all pods (under the healthbot namespace), only when the pods are restarted.

  • While adding a TSDB node

    Edit the InfluxDB deployment specifications and explicitly add the resource limit, before or after adding a TSDB node.

    1. Determine the InfluxDB pod and deployment name.

      There might be more than one InfluxDB deployments if multiple TSDB nodes are present. If there are multiple InfluxDB deployments, we must perform these steps on each deployment.

    2. Check the current memory limit.

    3. Edit the limit on the pod. For example, change the limit to 16-GB.

      Before changing the limit, the original values under the Resources parameter are empty. This implies that the limit will default to what is defined at the healthbot namespace level.

    4. Save and exit the InfluxDB pod. The pod is automatically restarted.

    5. Determine the new InfluxDB pod and deployment name.

    6. Verify that the edited limit is reflected in the pod.