-
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
Add options to OPC UA listener plugin for handling a failed connection #14533
Labels
feature request
Requests for new plugin and for new features to existing plugins
Comments
annamooseity
added
the
feature request
Requests for new plugin and for new features to existing plugins
label
Jan 6, 2024
annamooseity
pushed a commit
to annamooseity/telegraf
that referenced
this issue
Jan 6, 2024
…uxdata#14533) Adds Error (default, same behavior as before), Ignore, and Retry as options for when the plugin cannot connect to the OPC UA server when Telegraf starts
annamooseity
pushed a commit
to annamooseity/telegraf
that referenced
this issue
Jan 6, 2024
…uxdata#14533) Adds Error (default, same behavior as before), Ignore, and Retry as options for when the plugin cannot connect to the OPC UA server when Telegraf starts
1 task
annamooseity
pushed a commit
to annamooseity/telegraf
that referenced
this issue
Jan 6, 2024
…uxdata#14533) Adds Error (default, same behavior as before), Ignore, and Retry as options for when the plugin cannot connect to the OPC UA server when Telegraf starts
Thanks for the issue and for putting up a PR! Will review hopefully this week. |
annamooseity
pushed a commit
to annamooseity/telegraf
that referenced
this issue
Jan 12, 2024
…uxdata#14533) Adds Error (default, same behavior as before), Ignore, and Retry as options for when the plugin cannot connect to the OPC UA server when Telegraf starts
annamooseity
pushed a commit
to annamooseity/telegraf
that referenced
this issue
Jan 12, 2024
…uxdata#14533) Adds Error (default, same behavior as before), Ignore, and Retry as options for when the plugin cannot connect to the OPC UA server when Telegraf starts
annamooseity
pushed a commit
to annamooseity/telegraf
that referenced
this issue
Jan 12, 2024
…uxdata#14533) Adds Error (default, same behavior as before), Ignore, and Retry as options for when the plugin cannot connect to the OPC UA server when Telegraf starts
annamooseity
pushed a commit
to annamooseity/telegraf
that referenced
this issue
Jan 12, 2024
…uxdata#14533) Adds Error (default, same behavior as before), Ignore, and Retry as options for when the plugin cannot connect to the OPC UA server when Telegraf starts
annamooseity
pushed a commit
to annamooseity/telegraf
that referenced
this issue
Jan 15, 2024
…uxdata#14533) Adds Error (default, same behavior as before), Ignore, and Retry as options for when the plugin cannot connect to the OPC UA server when Telegraf starts
annamooseity
pushed a commit
to annamooseity/telegraf
that referenced
this issue
Jan 15, 2024
…uxdata#14533) Adds error (default, same behavior as before), ignore, and retry as options for when the plugin cannot connect to the OPC UA server when Telegraf starts
annamooseity
pushed a commit
to annamooseity/telegraf
that referenced
this issue
Jan 15, 2024
…uxdata#14533) Adds error (default, same behavior as before), ignore, and retry as options for when the plugin cannot connect to the OPC UA server when Telegraf starts
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Use Case
We have several sites with multiple OPC UA servers that may or may not be on at a given time. We would like the ability to for Telegraf to still collect information from other successfully initiated inputs even if it can't talk to the OPC UA server. Ideally, we'd have three options when Telegraf fails to start subscriptions:
Expected behavior
The user has the option of continuing running Telegraf with all other plugins, even if a particular server is off.
Actual behavior
Right now, Telegraf gives up as soon as it cannot connect to a OPC UA server.
Additional info
Adding error handling for inputs has been discussed a LOT in several tickets, like #11313 and #13834, plus some others I can't find right now. The verdict was to implement this type of error handling on a per-input basis. The Kafka consumer plugin does something similar.
The text was updated successfully, but these errors were encountered: