[SOLVED]Automation Graph Rule Changes ALL Graphs

[eholz1]

Hello All,
I tried to use cacti automation to add 64bit counter (In/Out Bits) to UP interfaces
on a device (later a range of devices).

I set up a network discovery for the the network in question - but NOT adding device to cacti.
I then copied the stock 64 bytes rule and made it 64 counter In/Out Bits.

I then applied the automation rule to the device - it adds some graphs (64bit counters In/Out bits) but only to the sub interfaces:
i.e Gi0/1.301 this interface is up. I need it to add a graph for Gi0/1 not the sub-interface. It would be ok if the rule added
64Bit counter to both Gi0/1 and Gi0/1.301.

Pattern matching by adding a 4th item to the rule for ifName does not work.

The I discovered what i think is very strange. When I apply the graph rule to a device, it may (or may not) add a 64bit In/Out bits graph, but it changes all existing In/Out graphs to use 64bit counters, but does not change the graph type or template!

Is this the intended mode of operation? I also notice that if a device is discovered thru automation, it adds appropriate graphs.

Help - will post this on Git Hub as well.

Thanks,
eholz1


Turns solution is to use 30 second poller intervals - this results in a correct data flow representation -
Which leads to other problems like poller table not empty and gaps in graphs