Groups keyboard shortcuts have been updated
Dismiss
See shortcuts

Regarding the "Dropped Packets" on Grafana

120 views
Skip to first unread message

InFi_Bebe_

unread,
Aug 22, 2024, 9:52:57 AM8/22/24
to sFlow-RT
Hello, Group members

I came across the working group through https://blog.sflow.com/ and would like to get assistance in visualizing dropped packet information in Grafana. Currently, all other metrics appear to be working fine, except for the dropped packet metrics.

After investigating, here is what I’ve found across the different containers:

1. http://localhost:8008/app/browse-drops/html/index.html: I can see the dropped packet information correctly displayed here (e.g., reason, stack, ipsource, ipdestination).
Discard Browser 2024-08-22 14-18-25.png

2. http://localhost:9090/targets?search=: The state for the sflow-rt-drops target shows as ‘up’, but unlike other targets, no data is visible for this endpoint.

Prometheus Time Series Collection and Processing Server 2024-08-22 14-21-15.png

<No data with white page>
localhost:8008:app:prometheus:scripts:export.js:fl.png
3. http://localhost:3000/d/fc5840ce-c59d-4145-9b20-1a5b3f8931da/sflow-rt-dropped-packets?orgId=1&refresh=10s: Due to the lack of data from step 2, no information is being displayed on the Grafana dashboard.


Is there anyone who can help guide me on what I should check or adjust in this situation?

Peter Phaal

unread,
Aug 22, 2024, 10:29:44 AM8/22/24
to sFlow-RT
Thank you for the detailed information! I think I see what is going on, the 'node:inputifindex' and the 'ifname:inputifindex' keys require that SNMP is enabled for the sFlow-RT container (-Dsnmp.ifname=yes), or a topology is installed, https://sflow-rt.com/topology.php. The easiest fix for now would be to change 'node:inputifindex' to 'agent' and 'ifname:inputifindex' to 'inputifindex' in your Prometheus scrape script (and restart Prometheus container).
Reply all
Reply to author
Forward
0 new messages