Targets or subscription groups?

[hellt]

A potential bottle neck that gnmic config has is the necessity to bind subscriptions and outputs per each target.

Consider having 100 targets and 5 subscriptions, it becomes very cumbersome to maintain the list of bindings between targets, subs and outputs.

Maybe to think about target groups, which will aggregate target addresses?

[karimra]

Can you show an example of how that config might look like ?

[hellt]

didn't give it too much thought, but maybe smth like that

targets:
  all: # group name
    members:
      - leaf1:
      - leaf2:
          subscriptions:
            - cpu # per-target subscription
      - spine1:
    subscriptions:
      - interface_stats # subscriptions to apply to all members
    outputs:
      - prom # outputs to apply to all members of the group

  leafs: # group name
    members:
      - leaf1:
      - leaf2:
    subscriptions:
      - bgp_stats

[karimra]

as discussed offline, a seperate mappings section would be better, to try to keep the current config method compatible.