-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Support SNMP Traps in snmp receiver #32358
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
You might have a look at this open source solution from kentik https://github.com/kentik/ktranslate, they just added OTEL support. It provides SNMP traps/polling and includes device profiling to determine which MIBs are supported based on sysOID. |
Thanks for the suggestion + information Alex! That said, after thinking about it more, a new |
ktranslate author here. gosnmp does support v3 traps, highly recommend the library. This said, pulling packets off the wire is not even half the battle. The value add is around supporting secure ways to provide snmp credentials to the process and mapping from oid keys to human readable names. Traps are naturally events but otel doesn't do events so I'm debating whether to map traps received as logs or a trace. Happy to team up / share code if there's interest. |
Could you elaborate on this. Are you referring to the lack of distinction between Events and Logs in the OTEL spec? |
Mostly I'm talking about the non 1.0 state of the golang API. Also yes, logs/events being run together. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Component(s)
receiver/snmp
Is your feature request related to a problem? Please describe.
We have customers who wish to use receive messages from SNMP traps
I see a reference to supporting snmp trap ingestion in the syslog receiver, but figured native snmp trap support may make more sense here (or, at least, point a user to docs in syslog receiver if not/in the short term)
Describe the solution you'd like
Support
rfc1215
in this receiver (or maybe a bespokesnmptrap
receiver)Describe alternatives you've considered
Using syslog receiver, assuming it supports traps like the exporter claims to
Additional context
Some results from the top of my search engine for background context:
Additional RFCs which are useful
The text was updated successfully, but these errors were encountered: