-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Update wifi stats to support multiple stations (#977) #980
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
collector/wifi_linux.go
Outdated
@@ -65,14 +65,14 @@ func NewWifiCollector() (Collector, error) { | |||
) | |||
|
|||
var ( | |||
labels = []string{"device"} | |||
labels = []string{"device", "hw"} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think hw
is nice and short, but not very descriptive. We generally recommend more descriptive names. How about station_address
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From nl80211.h, it is called
* @NL80211_ATTR_MAC: MAC address (various uses)
On linux iw dev wlan1 station dump
command output, it is not explicity named.
I think station_address
might be a bit repetitive given the statistics are named node_station_
but any of the following would be fine:
mac
hardware_address
hw_address
or even just address
Would one of these be acceptable?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
True, how about mac_address
, to match the datasource.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM after changing the label name to mac_address
.
Signed-off-by: neiledgar <[email protected]>
b57d682
to
8da695f
Compare
Changed hw label to mac_address. I squashed all the changes into one commit. Apologies if I lost your comments. Is the correct workflow to add additional commits rather than squash all review updates into one commit? |
@neiledgar Squashing commits is fine. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, Thanks!
LGTM |
…etheus#980) Signed-off-by: neiledgar <[email protected]>
Signed-off-by: neiledgar [email protected]