-
Notifications
You must be signed in to change notification settings - Fork 25
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
Bring back option to configure target SNMP port #23
Comments
Good catch, I would like to have this functionality back in the script (still with default so that one does not have to use it). Adding it to the example files is a good idea, too 👍🏻 |
I will try to take care about it within one of the next iterations. |
Current |
As #31 now got merged i would like to publish a new release. But as the option to configure a target port is still a regression it would be a major version. So i am drafting a feature version bump as a pre release and release "normal" one as soon as this regression is solved. EDIT: published pre-release v0.4.0-beta.1 |
Dear Frederic, I will re-add this option in the course of the next iterations. That's why I wanted to add #39 ff. beforehand. In the meanwhile, as I found out just yesterday, everyone can use a composite With kind regards, |
Braindump (for future me or others): The corresponding option for the |
I added the missing port definition to easysnmp.Session in #46 |
Hi,
I just discovered that the refactoring coming from #4/#19 dropped that feature to specify the target SNMP port number (#2), so we will have to bring it back when there is demand.
Also, after integrating #21, the Icinga configuration snippets will provide access to almost all parameters this program has to offer. However, the
-p
option is still missing there. Also depending on community demand, this can be added every time.With kind regards,
Andreas.
The text was updated successfully, but these errors were encountered: