Currently my Influx db contains the following tags:
influx query 'import "influxdata/influxdb/schema"
schema.tagKeys(bucket: "zrok")'
Result: _result
Table: keys: []
_value:string
----------------------
_start
_stop
_field
_measurement
acctId
envId
namespace
share
Is there a way to forward also the ziti tags or just a single tag?
{"namespace":"usage","event_src_id":"ctl1","timestamp":"2025-07-22T08:41:26.173689007Z","version":3,"source_id":"router1","circuit_id":"7NraeDsxv","usage":{"ingress.rx":197,"ingress.tx":483},"interval_start_utc":1753173600,"interval_length":60,"tags":{"clientId":"envId_src","hostId":"envId_dst","serviceId":"1qckVqdrhmPI7JZoxNjQb2"}}
I'm interested to query influx for "clientId" tag like
influx query 'from(bucket:"zrok") |> range(start:-1h) |> filter(fn: (r) => r.clientId == "envId_src" )'
Zrok controller writes tons of logs:
Jul 26 09:19:29 zrok[2970709]: {"file":"/__w/zrok/zrok/controller/metrics/usageIngest.go:37","func":"github.com/openziti/zrok/controller/metrics.Ingest","level":"error","msg":"unable to assert 'tags': {\"namespace\":\"fabric.usage\",\"event_src_id\":\"ctl1\",\"timestamp\":\"2025-07-26T09:19:29.434545223Z\",\"version\":3,\"source_id\":\"RT1\",\"circuit_id\":\"MU1AW57Bvf\",\"usage\":{\"fabric.rx\":138,\"fabric.tx\":269},\"interval_start_utc\":1753521540,\"interval_length\":60,\"tags\":null}","time":"2025-07-26T09:19:29.555Z"}
Jul 26 09:19:29 zrok[2970709]: {"file":"/__w/zrok/zrok/controller/metrics/usageIngest.go:37","func":"github.com/openziti/zrok/controller/metrics.Ingest","level":"error","msg":"unable to assert 'tags': {\"namespace\":\"fabric.usage\",\"event_src_id\":\"ctl1\",\"timestamp\":\"2025-07-26T09:19:29.434546006Z\",\"version\":3,\"source_id\":\"RT1\",\"circuit_id\":\"5Wkdk5bxR\",\"usage\":{\"fabric.rx\":56,\"fabric.tx\":56},\"interval_start_utc\":1753521540,\"interval_length\":60,\"tags\":null}","time":"2025-07-26T09:19:29.555Z"}
journalctl --since "12 hours ago" -g error | grep fabric\\.usage | wc -l
12838
journalctl --since "12 hours ago" -u zrok-controller.service -g error | wc -l
12860
the messages fabric.usage is the majority: 99.8 %