|
| 1 | +--- |
| 2 | +weight: 2 |
| 3 | +title: VictoriaTraces Cluster |
| 4 | +menu: |
| 5 | + docs: |
| 6 | + parent: helm |
| 7 | + weight: 2 |
| 8 | + identifier: helm-victoria-traces-cluster |
| 9 | +url: /helm/victoria-traces-cluster/ |
| 10 | +aliases: |
| 11 | + - /helm/victoriatraces-cluster/ |
| 12 | +tags: |
| 13 | + - traces |
| 14 | + - kubernetes |
| 15 | +--- |
| 16 | +{{ template "chart.badges" . }} |
| 17 | + |
| 18 | +{{ template "chart.description" . }} |
| 19 | + |
| 20 | +{{ template "chart.prerequisites" . }} |
| 21 | + |
| 22 | +## Quick start |
| 23 | + |
| 24 | +The chart deploys VictoriaTraces cluster database. |
| 25 | +It deploys the following components according to [VictoriaTraces cluster architecture](https://docs.victoriametrics.com/victoriatraces/cluster/#architecture): |
| 26 | + |
| 27 | +- `vtstorage` stores the ingested traces to the configured persistent volumes |
| 28 | +- `vtinsert` receives incoming traces and spreads them evenly across `vtstorage` nodes |
| 29 | +- `vtselect` provides API for querying the ingested traces |
| 30 | + |
| 31 | +The default chart setup is shown below: |
| 32 | + |
| 33 | +```mermaid |
| 34 | +graph LR |
| 35 | + Collector["Log Collector"] --> VTI1["vtinsert-1"] |
| 36 | + Collector --> VTI2["vtinsert-2"] |
| 37 | + |
| 38 | + subgraph "VictoriaTraces Cluster" |
| 39 | + VTI1 --> VTS1["vtstorage-1"] |
| 40 | + VTI1 --> VTS2["vtstorage-2"] |
| 41 | + VTI2 --> VTS1 |
| 42 | + VTI2 --> VTS2 |
| 43 | + |
| 44 | + VTS1 <--> VTQ1["vtselect-1"] |
| 45 | + VTS1 <--> VTQ2["vtselect-2"] |
| 46 | + VTS2 <--> VTQ1 |
| 47 | + VTS2 <--> VTQ2 |
| 48 | + end |
| 49 | + |
| 50 | + VTQ2 <--> Users |
| 51 | +``` |
| 52 | + |
| 53 | +For a quick start, install `victoria-traces-cluster` using the following commands, |
| 54 | +making sure to replace the environment variables with your own values: |
| 55 | + |
| 56 | +```sh |
| 57 | +export RETENTION=30d |
| 58 | +export PVC_SIZE=10Gi |
| 59 | +export VTSTORAGE_REPLICAS=2 |
| 60 | +export NAMESPACE=traces |
| 61 | + |
| 62 | +# Install victoria-traces-cluster chart |
| 63 | +helm install vtc vm/victoria-traces-cluster --namespace $NAMESPACE --wait \ |
| 64 | + --set "vtstorage.retentionPeriod=$RETENTION" --set "vtstorage.persistentVolume.size=$PVC_SIZE" \ |
| 65 | + --set vmauth.enabled=true \ |
| 66 | + --set vtstorage.replicaCount=$VTSTORAGE_REPLICAS |
| 67 | + |
| 68 | +In the example above, two `vtstorage` instances are deployed, each with a 30-day retention period and a 10 Gi PVC. |
| 69 | + |
| 70 | +To access the data within the cluster, use the vmauth address: `http://vtc-victoria-traces-cluster-vmauth.logging.svc.cluster.local:8427`. |
| 71 | +You can use this address as Data Source URL in Grafana. |
| 72 | +The vmui interface is available at: `http://vtc-victoria-traces-cluster-vmauth.logging.svc.cluster.local:8427/select/vmui/`. |
| 73 | + |
| 74 | +To uninstall these charts, run: `helm uninstall vts`. |
| 75 | +Note that this *will not* remove the PVCs, so you will need to delete them manually if no longer needed. |
| 76 | + |
| 77 | +For finer control and easier maintenance, it is recommended to set these |
| 78 | +values in a separate `values` file and use it during installation. |
| 79 | +See [how to install victoria-traces-single](https://docs.victoriametrics.com/helm/victoria-traces-single/#install-victoria-traces-single-chart) for an example. |
| 80 | +You can do this later if you want to configure more settings than shown in the default example. |
| 81 | + |
| 82 | +## Chart configuration |
| 83 | + |
| 84 | +### vmauth |
| 85 | + |
| 86 | +When you enable `vmauth` with: |
| 87 | + |
| 88 | +```yaml |
| 89 | +vmauth: |
| 90 | + enabled: true |
| 91 | +``` |
| 92 | + |
| 93 | +The chart launches an [`vmauth`](https://docs.victoriametrics.com/victoriametrics/vmauth/) service |
| 94 | +for proxying and load-balancing incoming data ingestion requests to `vtinsert` nodes and for proxying and load-balancing incoming queries to `vtselect` nodes. |
| 95 | + |
| 96 | +So, the chart can now be thought of as: |
| 97 | + |
| 98 | +```mermaid |
| 99 | +graph LR |
| 100 | + Collector["Traces Collector"] --> VTI1["vtinsert-1"] |
| 101 | + Collector --> VTI2["vtinsert-2"] |
| 102 | + |
| 103 | + subgraph "VictoriaTraces Cluster" |
| 104 | + VTI1 --> VTS1["vtstorage-1"] |
| 105 | + VTI1 --> VTS2["vtstorage-2"] |
| 106 | + VTI2 --> VTS1 |
| 107 | + VTI2 --> VTS2 |
| 108 | + |
| 109 | + VTS1 <--> VTQ1["vtselect-1"] |
| 110 | + VTS1 <--> VTQ2["vtselect-2"] |
| 111 | + VTS2 <--> VTQ1 |
| 112 | + VTS2 <--> VTQ2 |
| 113 | + end |
| 114 | + |
| 115 | + VTQ1 <--> Users["vmauth"] |
| 116 | + VTQ2 <--> Users |
| 117 | +``` |
| 118 | + |
| 119 | +{{ include "chart.installSection" . }} |
| 120 | + |
| 121 | +{{ include "chart.uninstallSection" . }} |
| 122 | + |
| 123 | +{{ include "chart.helmDocs" . }} |
| 124 | + |
| 125 | +## Parameters |
| 126 | + |
| 127 | +The following tables lists the configurable parameters of the chart and their default values. |
| 128 | + |
| 129 | +Change the values according to the need of the environment in ``victoria-traces-cluster/values.yaml`` file. |
| 130 | + |
| 131 | +{{ template "chart.valuesTableHtml" . }} |
0 commit comments