f41gh7

Mutli level cluster setup

doc

Lets say we have 2 zones: zone-a and zone-b. Separate cluster must be deploy to the both zones with commands:

helm upgrade -i zone-a vm/victoria-metrics-cluster -f zone.yaml

f41gh7

How to use opentelemetry collector with VictoriaMetrics

requirements

• helm
• kubectl
• kubernetes cluster

Installation of VictoriaMetrics

In education purpose, I'll use single node version of VictoriaMetrics.

f41gh7

python wrapper for metricsql expr validation.

usage:

1. build shared lib: go build -buildmode=c-shared -o library.so main.go
2. use it

python3 metricsql.py 'not_exist(up)'`
failed to parse expr: not_exist(up), error: unsupported function "not_exist"

f41gh7

Recommeneded project structure for alertmanager helm chart

I'd recommend to keep project structure simple and straight forward:

chart-name/
  # any static content to include into templates
  files/
  # all needed dynamic templates
  templates/

f41gh7

apiVersion: operator.victoriametrics.com/v1beta1
kind: VMAgent
metadata:
  name: main
spec:
  selectAllByDefault: true
  replicaCount: 1
  statefulMode: true
  shardCount: 2
  extraArgs:

f41gh7

apiVersion: v1
kind: Service
metadata:
  name: vlinsert
spec:
  type: ClusterIP
  ports:
    - name: http
      protocol: TCP
      port: 9428