After the device re-queries SNMP interface information, it will automatically generate various graphical representations

[datutu58888]

HI

cacti 1.2.24

After re-querying SNMP interface information, the device will automatically generate multiple graphics representations in bytes. Many of these automatically created graphics may overlap with the ones I manually created, as the byte-based graphics are not useful to me. Each time I re-query SNMP, it is to update the names of the existing ports. Deleting the automatically created graphics then causes the sequence number of the graphics to become very large.

QQ图片20231204135251.png (217.37 KiB) Viewed 1037 times

Why is it that when I re-query at location no.1 in Figure 1, it automatically creates many graphics in bytes, some of which overlap with the ones I manually created, and some of which are not what I need? It is troublesome to delete them every time, I'm afraid they will occupy resources if not deleted, and each query causes the sequence number of the graphics to keep increasing.

QQ图片20231204135516.png (265.29 KiB) Viewed 1037 times

[cigamit]

Check Console > Automation > Graph Rules
Either disable the "Traffic 64 Bit Server" rule, or change it to Bits to automate the creation of Bit graphs instead of Bytes.

[datutu58888]

Check Console > Automation > Graph Rules
Either disable the "Traffic 64 Bit Server" rule, or change it to Bits to automate the creation of Bit graphs instead of Bytes.

I tried configuring it according to your method to solve the byte problem, but every time I query for deduplication, it automatically creates a bunch of graphics. What's going on? I have to delete them every time, but the serial number of the graphics keeps increasing

[datutu58888]

Check Console > Automation > Graph Rules
Either disable the "Traffic 64 Bit Server" rule, or change it to Bits to automate the creation of Bit graphs instead of Bytes.

Thank you very much. It's effective now. Re-querying no longer generates other inexplicable graphics.