azure_iothub_consumer - Input plugin

[chrishayles]

…crosoft fix.

Required for all PRs:

• Signed CLA.
• Associated README.md updated.
• Has appropriate unit tests.

To follow once code adjustments have been made following cert fix.

[chrishayles]

Known issues/required changes:

• Include tests for plugins. [Telegraf plugin code] Complete
• - More detailed README. [Telegraf plugin code] Complete
• - PR required for iothub module to introduce "iotmodule" type. [iothub module code] Rolled iotmodule into iotdevice instead
• - Move output plugin from "iotdevice" to "iotmodule." [Telegraf plugin code] n/a as above
• - Move input plugin from "iotservice" to "iotmodule." [Telegraf plugin code] n/a as above
• - Add other transport protocols to "iothub" module and create second pull request. [iothub module code]
• - input plugin here needs to work with Telegraf parser and accumulator instead of current log output. [Telegraf plugin code] Complete
• - Typo in the input plugin filename. Complete

[danielnelson]

Can you also add some information about when this plugin would need to be used instead of #6928?

[chrishayles]

@danielnelson Hey Daniel, forwarded on an email I sent to your colleagues last month. Lookout for something from [email protected].

Short version: the IoT Hubs has an "Event Hubs Compatible" endpoint, but that endpoint doesn't have anywhere near the functionality of establishing a device connection with the IoT Hub and won't make use of an edge setup.

[chrishayles]

Highlighting issues.

[chrishayles]

Fixed dependency issue, removed iothub library codebase to reflect this. Cleaned up the metric creation.

[srebhan]

@chrishayles is this still a thing?

[telegraf-tiger]

Hello! I am closing this issue due to inactivity. I hope you were able to resolve your problem, if not please try posting this question in our Community Slack or Community Page. Thank you!