Repository navigation
yanic: 2.1.1+batmanv5, write Parker CLAT and mesh VPN peer metrics - #1102
Merged
Merged
Conversation
- Package yanic_2.1.1+batmanv5-2 on the production yanic and the pgws.
The pgws now forward the respondd data unchanged (yanic#4).
- Production yanic: [respondd.metrics] rules for statistics.clat.{direction}
(measurement clat) and statistics.mesh_vpn.groups.{group}.peers.{peer}
(measurement mesh_vpn_peer, method active=1 standby=0).
This was referenced Nov 21, 2026
awlx
marked this pull request as ready for review
November 21, 2026 16:57
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Write the Parker node data for CLAT and the mesh VPN tunnels to InfluxDB (database
yanic), so that Grafana can show it.Changes
yanic_2.1.1+batmanv5-2_amd64.debinyanic/init.sls(production yanic, gw04) andparker/yanic/init.sls(pgw01-04).yanic/yanic.conf.tmpl(only the production yanic writes to InfluxDB):[respondd.metrics]with 2 rules:statistics.clat.{direction}to measurementclat(fieldspackets,bytes; tagdirection).statistics.mesh_vpn.groups.{group}.peers.{peer}to measurementmesh_vpn_peer(fieldsestablishedin seconds,methodwith active = 1, standby = 0; tagsgroup,peer).nodeid,hostname,site,domain.mesh_vpnpeers also getmesh_vpn_peerpoints (same rule).Why the pgws need the new package
The pgws forward the node data to the production yanic (
database.connection.respondd). The old yanic sent only keys with a Go field, soclatandmethodwere lost. freifunkMUC/yanic#4 sends the received data unchanged.Related pull requests
[respondd.metrics])v2.1.1+batmanv52.1.1+batmanv5)Package
https://apt.ffmuc.net/yanic_2.1.1%2Bbatmanv5-2_amd64.debis live.sha256
f28ddef1adc212415a24bf7c2b6ecc21fcbb06cd56e050471f10101dd9b156fd(same as the CI artifact of freifunkMUC/yanic-deb#7; checked over the public URL).Tests
yanic/yanic.conf.tmplwith Jinja2 and test pillar data. Started yanic (branch of yanic#4) with it: the config loads, the metrics rules are accepted.clatand 2mesh_vpnpeers, active and standby) sends to a "pgw" yanic on port 11001; it forwards to a "gw04" yanic with the rendered config; this writes to a fake InfluxDB. Result:go test ./...in yanic#4: pass.Not tested
state.applyon gw04 and the pgws. After the merge: one host at a time,test=Truefirst.Rollout and rollback
2.1.1+batmanv4-2and the old config).