# Configure Remote Write Endpoints

Remote write endpoints allow you to send metrics data from Kloudfuse to external systems or storage backends. You configure multiple endpoints by defining them in your settings, assigning aliases for easy reference, and then using relabel rules to route specific time series data to the appropriate destination.

To do that, you must configure the `ingester.config.aggregator` section of the `custom-values.yaml` files:

```yaml
ingester:
  config:
    aggregator:
      metric:
        relabelConfigs:
          - source_labels:
              - deliverystreamname
            regex: test-stream
            action: remotewrite (1)
            remote_write_endpoints:
              - prod (3)
          - source_labels:
              - aws_ec2_fleet_id
            regex: fleet-0c1e3eb5-c607-ec8f-8cb2-ab82056fa651
            action: remotewrite (1)
            remote_write_endpoints:
              - test (3)
              - prod (3)
        RemoteWriteConfig:
          Enabled: true
          endpointUrls: (2)
            prod: http://prometheus1-server.kfuse-example.svc:80/api/v1/write
            test: http://prometheus2-server.kfuse-example.svc:80/api/v1/write
```

|     |     |
| --- | --- |
| **1** | `remotewrite`: Use the `relabel` rule to route time series data to different endpoints. |
| **2** | `endpointUrls`: Specify aliases for endpoints. Here, they are `prod` and `test`. |
| **3** | `remote_write_endpoints`: Reference these aliases in the relabel rule argument, `remote_write_endpoints`. |