Manage Azure Application Insights Monitoring
Take control of your Azure Application Insights monitoring with Nodinite. This guide helps you manage access to curated Kusto queries, support root cause analysis, and empower teams with secure, role-based self-service, without direct Azure Portal access.
- ✅ Execute pre-defined Kusto queries without direct Azure Portal access
- ✅ Empower business and support teams with secure, role-based self-service
- ✅ Reuse curated queries across one or more Application Insights instances
- ✅ Accelerate root cause analysis with actionable Application Insights data
Animated walkthrough: open Execute Queries from the Action menu, click Execute on a query, confirm with Yes, and read the Response for card; here the response is empty because no requests fell in the time window.
Let your business perform everyday tasks and get the answers they need by executing your pre-defined Kusto queries against Azure Application Insights for selected Azure subscriptions.
Start with Monitoring Application Insights to understand which instances Nodinite monitors and which query collections are available before you run or review the actions below.
For your business and other end-users, delegate the power to manage and gain insights into selected Application Insights instances in Azure. Nodinite Monitoring gives the support and maintenance team additional data for root cause analysis without individual direct access to the Microsoft Azure Portal. Reducing access limits the number of attack vectors, and having fewer people with fewer access rights minimizes the risk of disruption of mission-critical services.
Diagram: A user runs Kusto queries from a script collection in a Monitor View (blue); each collection belongs to one Application Insights instance in Azure (teal).
| Application Management Team | IT Operations | Business |
|---|---|---|
| Let your AM team have the power to execute Kusto queries without involving the IT operations team | Stay in complete control with access to everything | Give your business Data and self-service for solutions built using Application Insights |
Management Features
For Resources in the Role-based Monitor Views with the Remote Actions privilege grant, the following Remote Actions grouped by Category are available:
| Category | Monitoring | Actions | Metrics/Statistics |
|---|---|---|---|
| Application Insights | - | Details Edit Execute Queries |
- |
As an Administrator with access to the Configuration for Monitoring Agents, the additional Monitoring options are available:
| Monitoring | Remote Configuration |
|---|---|
| Monitoring Application Insights |
|
Application Insights
The 'Application Insights' Category provides one Resource for each Application Insights instance found using the configuration with the specified display name as the Resource name.
Example from a Monitor View with a list of 'Application Insights' instances.
See Monitoring Application Insights for additional details about Application Insights Monitoring.
The Application Insights category provides Resources that display the evaluated monitored state according to built-in rules.
The following Remote Actions are available for the Application Insights Category:
Example of the Action menu for an Application Insights instance.
Note
Legacy Authentication Method: Prior versions of Nodinite used API keys to access Application Insights data. Nodinite now uses Azure App Registration with Delegated permissions (Application Insights API - Data.Read) for secure, centralized authentication. API key management has been removed. See the Azure user rights section of the Prerequisites and the Azure Application Access guide for configuration details.
Details
To view the selected Application Insights Resource, click the Action button and then click Details in the Control Center part of the menu.
Use Details to open the details modal for the selected Application Insights instance.
The modal shows TenantId, Subscription, Subscription ID, Resource group, Location, the Instrumentation Key, the Azure resource labels, and Description, and lists the Function Web App Sites that log to the instance, with their Function Count.
Example of the details modal for the selected Application Insights instance.
Edit
Edit holds a Description for the instance. Save creates an entry in the global Configuration for the instance's current Instrumentation Key.
Execute Queries
For each Application Insights instance, the Nodinite Administrator can manage a Kusto query script collection. The Administrator creates and manages the collections in the Configuration of the agent.
From the Monitor View, end-users gain self-service, execute these queries, and review the result.
To run the pre-defined queries for the selected Application Insights resource, click the Action button and then click Execute Queries in the Control Center part of the menu.
The Execute Queries menu item opens the Kusto Scripts dialog for the selected Application Insights instance.
The Kusto Scripts dialog shows the instance's facts and a Script collection choice:
- Specific: the queries configured for this Application Insights instance
- Global: the queries available on every Application Insights instance of the Subscription
With no queries configured, the dialog says "No global queries are configured. Add them under Application Insights → Global Script Collection in the agent configuration."
Example of the Kusto Scripts dialog listing the pre-defined queries.
Click Execute on a query. Nodinite asks for confirmation first.
Every query asks "Are you sure you want to execute the specific Kusto query: ''?"; click Yes to run it.
The query runs in Application Insights. A toast says Executed: , and the result appears in a Response for card at the bottom of the dialog.
Example of the Response for card at the bottom of the dialog; this query returned no rows.
A query that fails shows a red toast with the reason, for example "The Application Insights query response did not contain a tables collection. Verify the configured query and Azure access rights."
Note
Kusto queries with a Date Time must be in the ISO 8601 format.
Find Connectors query
If you use a connector in a Logic Apps Workflow that you want to remove but don't know where to look, run the following Kusto query to find where it's used.
The example below finds where AtomicScope-Tracking exists. Always try to avoid a vendor lock-in. Nodinite has plug and play Monitoring and Logging for Logic Apps Workflows through the Azure Logic Apps agent.
resources
|where type == "microsoft.logic/workflows"
|extend connections = properties.parameters.$connections.value
|mv-expand(connections)
|project resourceGroup, name, connections
|parse kind = regex connections with * '"id":"' connection_id '","connectionName' *
|parse kind = regex connections with * '"connectionName":"' connection_connectionName '",' *
|parse kind = regex connections with * '"connectionId":"' connection_connectionId '"' *
|project LogicApp=name, ConnectorId=connection_id, ConnectionName=connection_connectionName, Id=connection_connectionId
|where isnotempty(ConnectorId)
|where ConnectorId contains "AtomicScope-Tracking"