There is a command group 'az_iot_ops'. This group of commands could 'manage azure iot operations'. 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_ops_check'.The syntax is: az iot ops check [--as-object {false, true}]
                 [--context]
                 [--detail-level {0, 1, 2}]
                 [--ops-service {akri, dataprocessor, deviceregistry, lnm, mq, opcua}]
                 [--post {false, true}]
                 [--pre {false, true}]
                 [--resource-name]
                 [--resources {asset, assetendpointprofile, assettype, broker, brokerlistener, configuration, datalakeconnector, dataset, diagnosticservice, instance, kafkaconnector, lnm, mqttbridgeconnector, pipeline}]. The 1th example of the child command would be to use it to 'basic usage  checks  mq  health with summary output', the syntax is: az iot ops check. The 2th example of the child command would be to use it to 'evaluates  mq  like prior example  however output is optimized for ci', the syntax is: az iot ops check --as-object. The 3th example of the child command would be to use it to 'checks  dataprocessor  health and configuration with detailed output', the syntax is: az iot ops check --svc dataprocessor --detail-level 1. The 4th example of the child command would be to use it to 'same as prior example  except constraining results to the  pipeline  resource', the syntax is: az iot ops check --svc dataprocessor --detail-level 1 --resources pipeline. The 5th example of the child command would be to use it to 'use resource name to constrain results to  pipeline  resource exactly matching name  pipeline', the syntax is: az iot ops check --svc dataprocessor  --resources pipeline --resource-name pipeline. The 6th example of the child command would be to use it to 'use resource name to constrain results to resource names that start with  pipeline name', the syntax is: az iot ops check --svc dataprocessor --detail-level 1 --resource-name pipeline-name*. The 7th example of the child command would be to use it to 'use     glob pattern to constrain results to resource names that contain  pipeline  and end with a single character', the syntax is: az iot ops check --svc dataprocessor --detail-level 1 --resource-name pipeline?. The parameter '--as-object' is optional. output check content and validations in a ci friendly data structure.. The parameter '--context' is optional. kubeconfig context name to use for k8s cluster communication. if no context is provided current_context is used.. The parameter '--detail-level' is optional. controls the level of detail displayed in the check output. choose 0 for a summary view (minimal output), 1 for a detailed view (more comprehensive information), or 2 for a verbose view (all available information).. The parameter '--ops-service --svc' is optional. the iot operations service deployment that will be evaluated.. The parameter '--post' is optional. run post-deployment checks.. The parameter '--pre' is optional. run pre-requisite checks to determine if the minimum requirements of a service deployment are fulfilled.. The parameter '--resource-name --rn' is optional. only run checks for the specific resource name. the name is case insensitive. glob patterns '*' and '?' are supported. note: only alphanumeric characters, hyphens, '?' and '*' are allowed.. The parameter '--resources' is optional. only run checks on specific resource kinds. use space-separated values.. 