There is a command group 'az_iot_hub'. This group of commands could 'manage azure iot hubs'. The group of commands has global parameter '--debug' which means 'Increase logging verbosity to show all debug logs.'. The group of commands has global parameter '--help -h' which means 'Show this help message and exit.'. The group of commands has global parameter '--only-show-errors' which means 'Only show errors, suppressing warnings.'. The group of commands has global parameter '--output -o' which means 'Output format.'. The group of commands has global parameter '--query' which means 'JMESPath query string. See <a href="http://jmespath.org/">http://jmespath.org/</a> for more information and examples.'. The group of commands has global parameter '--subscription' which means 'Name or ID of subscription. You can configure the default subscription using `az account set -s NAME_OR_ID`.'. The group of commands has global parameter '--verbose' which means 'Increase logging verbosity. Use --debug for full debug logs.'. This group contains a child command 'az_iot_hub_monitor events'.The syntax is: az iot hub monitor-events [--cg]
                          [--content-type]
                          [--device-id]
                          [--device-query]
                          [--enqueued-time]
                          [--hub-name]
                          [--interface]
                          [--login]
                          [--mc]
                          [--module-id]
                          [--properties {all, anno, app, sys}]
                          [--repair {false, true}]
                          [--resource-group]
                          [--timeout]
                          [--yes {false, true}]. The 1th example of the child command would be to use it to 'basic usage', the syntax is: az iot hub monitor-events -n {iothub_name}. The 2th example of the child command would be to use it to 'basic usage with an iot hub connection string', the syntax is: az iot hub monitor-events -n {iothub_name} --login 'HostName=myhub.azure-devices.net;SharedAccessKeyName=iothubowner;SharedAccessKey=12345'. The 3th example of the child command would be to use it to 'basic usage when filtering on target device', the syntax is: az iot hub monitor-events -n {iothub_name} -d {device_id}. The 4th example of the child command would be to use it to 'basic usage when filtering targeted devices with a wildcard in the id', the syntax is: az iot hub monitor-events -n {iothub_name} -d Device*. The 5th example of the child command would be to use it to 'filter devices using iot hub query language', the syntax is: az iot hub monitor-events -n {iothub_name} -q "select * from devices where tags.location.region = 'US'". The 6th example of the child command would be to use it to 'filter device and specify an event hub consumer group to bind to', the syntax is: az iot hub monitor-events -n {iothub_name} -d {device_id} --cg {consumer_group_name}. The 7th example of the child command would be to use it to 'receive message annotations  message headers', the syntax is: az iot hub monitor-events -n {iothub_name} -d {device_id} --properties anno. The 8th example of the child command would be to use it to 'receive message annotations   system properties  never time out', the syntax is: az iot hub monitor-events -n {iothub_name} -d {device_id} --properties anno sys --timeout 0. The 9th example of the child command would be to use it to 'receive all message attributes from all device messages', the syntax is: az iot hub monitor-events -n {iothub_name} --props all. The 10th example of the child command would be to use it to 'receive all messages and parse message payload as json', the syntax is: az iot hub monitor-events -n {iothub_name} --content-type application/json. The 11th example of the child command would be to use it to 'receive the specified number of messages from hub and then shut down', the syntax is: az iot hub monitor-events -n {iothub_name} --message-count {message_count}. The parameter '--cg --consumer-group -c' is optional. specify the consumer group to use when connecting to event hub endpoint.. The parameter '--content-type --ct' is optional. specify the content-type of the message payload to automatically format the output to that type.. The parameter '--device-id -d' is optional. target device id.. The parameter '--device-query -q' is optional. specify a custom query to filter devices.. The parameter '--enqueued-time --et -e' is optional. indicates the time that should be used as a starting point to read messages from the partitions. units are milliseconds since unix epoch. if no time is indicated "now" is used.. The parameter '--hub-name -n' is optional. iot hub name or hostname. required if --login is not provided.. The parameter '--interface -i' is optional. target interface identifier to filter on. for example: dtmi:com:example:temperaturecontroller;1.. The parameter '--login -l' is optional. this command supports an entity connection string with rights to perform action. use to avoid session login via "az login". if both an entity connection string and name are provided the connection string takes priority. required if --hub-name is not provided.. The parameter '--mc --message-count' is optional. number of telemetry messages to capture before the monitor is terminated. if not specified, monitor keeps running until meeting the timeout threshold of not receiving messages from hub.. The parameter '--module-id -m' is optional. target module id.. The parameter '--properties --props -p' is optional. indicate key message properties to output. sys = system properties, app = application properties, anno = annotations.. The parameter '--repair -r' is optional. reinstall uamqp dependency compatible with extension version. default: false.. The parameter '--resource-group -g' is optional. name of resource group. you can configure the default group using `az configure --defaults group=<name>`.. The parameter '--timeout --to -t' is optional. maximum seconds to maintain connection without receiving message. use 0 for infinity.. The parameter '--yes -y' is optional. skip user prompts. indicates acceptance of action. used primarily for automation scenarios. default: false.. 