f41gh7

apiVersion: v1
kind: Service
metadata:
  name: vm-demo-grafana
  labels:
    k8s-app: grafana
    app.kubernetes.io/name: vm-demo
    app.kubernetes.io/component: grafana
spec:
  ports:

f41gh7

version: '3.5'
services:
  vminsert:
    image: victoriametrics/vminsert:v1.60.0-cluster
    command:
      - '--storageNode=vmstorage-0:8400'
      - '--storageNode=vmstorage-1:8400'
      - '--storageNode=vmstorage-2:8400'
      - '--storageNode=vmstorage-3:8400'
      - '--storageNode=vmstorage-4:8400'

f41gh7

how to generate load on vmagent

requirements

• golang
• python3
• git

starting

f41gh7

generate self-signed ca with key

openssl req -x509 -sha256 -days 1825 -newkey rsa:2048 -keyout rootCA.key -out rootCA.crt -nodes

• ca.default.svc.cluster.local - ou

generate storage node certificates

YOU HAVE TO USE extfile -> domain.ext

storage 0

ou - mtls-vmstorage-0.mtls-vmstorage.default.svc.cluster.local

openssl req -newkey rsa:2048 -nodes -keyout vmstorage_0.key -out vmstorage_0.csr

f41gh7

serviceMonitor:
  enabled: true

alertmanager:
  enabled: true
  persistentVolume:
    enabled: false
  replicas: 1
  resources:
    limits:

f41gh7

Additional user registration

1. Log in into AWS Account, which was subscribed to the Managed solution
2. Open AWS Market Place page with Product and click continue to subscribe:

3) Click at `click here` link and you will be redirected with AWS token to the UI page, where you can register user account:

4) Register account.

f41gh7

apiVersion: operator.victoriametrics.com/v1beta1
kind: VMServiceScrape
metadata:
  name: apiserver
  namespace: monitoring-system
spec:
  endpoints:
  - bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token
    bearerTokenSecret:
      key: ""

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

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

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"