AzureDataExplorer
Use the Azure Data Explorer integration to collect and analyze data inside Azure Data Explorer clusters, and to manage search queries.
Analytics & SIEM · Azure Data Explorer
Configuration parameters
cluster_url— Cluster URL (e.g. https://help.kusto.windows.net) (required)client_id— Application ID (required)client_activity_prefix— Client Activity Prefix (required)insecure— Trust any certificate (not secure)proxy— Use system proxy settingsauthentication_type— Authentication Type (required)tenant_id— Tenant IDcredentials— Client Secretredirect_uri— Application redirect URIauth_code— Authorization code
Commands (9)
-
azure-data-explorer-auth-completeRun this command to complete the authorization process. This should be used after running the azure-data-explorer-auth-start command.
-
azure-data-explorer-auth-resetRun this command if for some reason you need to rerun the authentication process.
-
azure-data-explorer-auth-startRun this command to start the authorization process and follow the instructions in the command results.
-
azure-data-explorer-auth-testRun this command to test the connectivity to Azure Data Explorer.
-
azure-data-explorer-generate-login-urlGenerate the login url used for Authorization code flow.
-
azure-data-explorer-running-search-query-cancelStarts a best-effort attempt to cancel a specific running search query in the specified database.
-
azure-data-explorer-running-search-query-listList currently executing search queries in the given database. A database admin or database monitor can see any search query that was invoked on their database. Other users can only see search queries that they themselves invoked.
-
azure-data-explorer-search-query-executeExecute a Kusto Query Language (KQL) query against the given database inside a cluster. The Kusto query is a read-only request to process data and return results. To learn more about KQL go to https://docs.microsoft.com/en-us/azure/kusto/query/.
-
azure-data-explorer-search-query-listList search queries that have reached a final state in the given database. A database admin or database monitor can see any command that was invoked on their database. Other users can only see queries that they themselves invoked.