Per mitigation counters
plajjan opened this issue · comments
Implement relevant counters per mitigation!
We can use same measurement and value name as today, just add a new tag that is set to the mitigation ID.
So do we use the IP as ID for the mitigation? I guess that's a tad weird in a way since it wouldn't be possible to distinguish multiple mitigations for the same IP.
Should we come up with an artificial numeric id?
Maybe one thing doesn't need to exclude another, we can set a tag for the destination IP and another one for an artificial IP that is unique per mitigation.
Although the counters Snabb doesn't work that way - it needs to be a unique path so if it's keyed on the artificial integer id we need to lookup the destination IP before we can send it to influxdb.