-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
ifName agent
default value
#8011
Comments
@reimda what do you think? |
I agree that the tags across these three plugins should match. It was an oversight from the beginning that they don't match. We haven't been able to change the default because it will break anyone who is using the default. We can change the default on a major release (2.0) because major releases won't guarantee settings compatibility. For now we ought to prepare for a change in 2.0 by choosing the tag we want to use across all three plugins and deprecating the defaults in all three plugins that don't match the tag we chose. |
According to #4413, |
@Hipska I think the |
No, not by default. Only if you added a OID as tag and gave it that name. |
To which of they points is your comment? ;-) |
The first one, |
next steps: look at adding the |
@powersj I'm not sure how to deprecate the agent tag default value for the ifname processor. Did the other 2 already.. |
Feature Request
Opening a feature request kicks off a discussion.
As discussed in #7763 (comment)
Proposal:
Let the default value of these be the same:
agent
forprocessors.ifname
agent_host
forinputs.snmp
agent_address
forinputs.sflow
Current behavior:
The default value (agent) mostly never useful.
Desired behavior:
The default value should be a logical one that makes sense or most users would not need to change.
Tasks
The text was updated successfully, but these errors were encountered: