Skip to main content
This information is for Chronosphere Telemetry Pipeline, which is a standalone product separate from Chronosphere Observability Platform.
The information on this page applies to pipelines with the Deployment or StatefulSet workload type, but not pipelines with the DaemonSet workload type.
Chronosphere Telemetry Pipeline uses replica pods to scale pipelines. Each pipeline needs at least one replica to function. If a pipeline has more than one replica, any ingested data is balanced between those replicas accordingly. You can assign a fixed number of replicas to a pipeline, or enable horizontal pod autoscaling to automatically add and remove replicas in response to utilization changes.

​
Fixed number of replicas

Use one of the following methods to set a fixed number of replicas for your pipelines:
For replica counts with a volume over 100 TB a day, contact Chronosphere Support prior to scaling up to ensure stability.
  1. Sign in to the Telemetry Pipeline web interface.
  2. Open the project that contains the pipeline that you want to modify.
  3. Go to Core Instances, then click the name of the Core Instance associated with the pipeline that you want to modify.
  4. Under Data Pipelines, click the name of the pipeline that you want to modify.
  5. Go to  Advanced Settings.
  6. Increase the Replicas field to the amount you want, and then click Apply.

​
Horizontal pod autoscaling

Requires Core Instance version 2.12.3 or later.
Pipelines support horizontal pod autoscaling (HPA), which enables Telemetry Pipeline to add and remove replicas as needed.

​
Enable horizontal pod autoscaling

To enable HPA, create or modify a pipeline through Pipeline CLI and include both the --scale-up-value and --scale-down-value flags. You must assign a value greater than 0 to both flags, but these values don’t need to be identical to each other.

​
Configure horizontal pod autoscaling

To configure HPA, use the following flags when you create or update a pipeline through Pipeline CLI:

​
Disable horizontal pod autoscaling

To disable HPA, update a pipeline through Pipeline CLI and set both the --scale-up-value and --scale-down-value flags to 0. This prevents the autoscaler from scaling pipelines up or down, which means other HPA settings won’t affect your pipelines.

​
Pause a pipeline

You can pause a pipeline by setting its replicas to zero, which temporarily prevents that pipeline from routing or processing data. Use one of these methods to pause a pipeline:
  1. Sign in to Telemetry Pipeline.
  2. Open the project that contains the pipeline that you want to pause.
  3. Go to Core Instances, then click the name of the Core Instance associated with the pipeline you want to pause.
  4. Under Data Pipelines, find the pipeline that you want to pause, and then click  Settings >  Pause.
  5. In the dialog that appears, click Yes to confirm your choice.

​
Unpause a pipeline

If a pipeline is paused, use one of these methods to unpause it:
  1. Sign in to Telemetry Pipeline.
  2. Open the project that contains the pipeline that you want to unpause.
  3. Go to Core Instances, then click the name of the Core Instance associated with the pipeline you want to unpause.
  4. Under Data Pipelines, find the pipeline that you want to unpause, and then click  Settings >  Resume.
  5. In the dialog that appears, click Yes to confirm your choice.