ApplicationInsightsManagementClient is the Azure Resource Manager surface for the Application Insights web-test alerting feature. It exposes the metadata operation that Azure Portal and tooling use to enumerate the supported Microsoft.Insights provider operations for application performance monitoring resources. This is a control-plane companion to the broader Azure Monitor Application Insights stack, focused specifically on web-test based availability alerts.
1 endpointsAutomationManagement is the Azure Resource Manager API for managing Azure Automation accounts — the runbook execution and configuration management service. It covers automation account provisioning, key listing, account-level usage and statistics retrieval, and provider operations metadata. Use this client to set up the parent account that runbooks, DSC configurations, and update management workloads run inside.
10 endpointsAutomationManagementClient is the Azure Resource Manager API for managing webhooks attached to Azure Automation runbooks. It supports listing, creating, updating, and deleting webhooks, plus generating the unique webhook URI used to trigger a runbook from an external system. Use this client to wire runbooks into webhook-driven event sources such as monitoring tools, custom apps, or third-party CI systems.
6 endpointsThe Azure Activity Log Alerts API lets agents configure rules that fire when subscription-level events occur in Azure, such as resource writes, service health incidents, or policy actions. It exposes CRUD operations on activityLogAlert resources scoped to a subscription or resource group, with conditions that filter on category, level, operationName, and target resource. Alerts can be wired to action groups so that downstream notifications (email, SMS, webhooks) trigger automatically when the activity log records a matching event.
6 endpointsThe Azure Alerts Management API provides a unified view of fired alert instances across Azure Monitor, including activity log, metric, log search, and Service Health alerts. It exposes endpoints to list alerts with filtering by severity, monitor service, and time range, change alert state to acknowledged or closed, retrieve alert history, and manage action rules that suppress or route alerts. It also returns aggregated alert summaries and metadata that drive dashboards.
17 endpointsJentic publishes the only available OpenAPI specification for Azure API Management Client, keeping it validated and agent-ready. This deployment-level surface manages Azure API Management service instances themselves: list services in a subscription or resource group, get service details, check name availability, run backups and restores, apply network configuration updates, and obtain SSO tokens for the management portal. The product-level operations on APIs, products, and policies live on adjacent APIM clients.
13 endpointsJentic publishes the only available OpenAPI specification for Azure App Configuration Management Client, keeping it validated and agent-ready. This API manages Azure App Configuration store resources at the control plane: create, list, retrieve, and delete configuration stores, list and regenerate access keys, and read or list specific key-values held in a store. It is the surface used to provision the centralised configuration service that applications then read from at runtime.
17 endpointsJentic publishes the only available OpenAPI specification for Azure Application Insights Data Plane, keeping it validated and agent-ready. This API exposes the read-only telemetry surface for Application Insights: run Analytics (Kusto) queries against an application's logs, retrieve events filtered by event type, fetch event metadata via OData, and read pre-aggregated metric data with metadata. It is the surface used by dashboards, agents, and analytics pipelines that consume App Insights without hitting the management plane.
7 endpointsThis API is the Microsoft.DevOps ARM resource provider that manages Azure DevOps Pipelines as ARM resources, distinct from the data-plane Azure DevOps Services REST API. It exposes eight endpoints for listing, retrieving, creating, updating, and deleting pipeline resources scoped to subscriptions or resource groups, plus pipeline template definitions and operations discovery. Pipeline resources connect a source repository, an organisation profile, and a target Azure resource through a chosen pipeline template.
8 endpointsJentic publishes the only available OpenAPI specification for Azure Log Analytics - Operations Management, keeping it validated and agent-ready. This API manages Operations Management Solutions and their associated configuration objects in the Microsoft.OperationsManagement namespace, letting operators install, list, update, and remove solutions like Updates, AzureActivity, or Security on a Log Analytics workspace. It also exposes ManagementAssociations and ManagementConfigurations for binding solutions to ARM resources. All requests authenticate with Azure AD OAuth 2.0 against Azure Resource Manager.
15 endpointsJentic publishes the only available OpenAPI specification for Azure Metrics, keeping it validated and agent-ready. The Azure Metrics API lets clients submit custom metric data points to the Azure Monitor metrics store via a single regional ingestion endpoint at monitoring.azure.com. It is the publishing side of the Azure Monitor metrics pipeline, used by applications and infrastructure to record numeric time-series data tied to a specific Azure resource. Once ingested, these metrics can be queried, charted, and alerted on through Azure Monitor.
1 endpointsJentic publishes the only available OpenAPI specification for ContainerRegistryManagementClient, keeping it validated and agent-ready. This 2019-06-01-preview revision of the Azure Container Registry (ACR) Management Client focuses on ACR Tasks — the in-registry build and run pipeline. Its 18 endpoints cover scheduling runs, listing and cancelling runs, requesting log SAS URLs, fetching build source upload URLs, and managing tasks (create, list, get, update, delete, listDetails). Use it to run a docker build inside ACR, pull the build log, or trigger a quick task from a remote git context.
18 endpointsJentic publishes the only available OpenAPI specification for DeploymentScriptsClient, keeping it validated and agent-ready. The API manages Azure Resource Manager Deployment Scripts under Microsoft.Resources, the resource type that lets ARM templates run inline PowerShell or Bash scripts during a deployment. It covers create, get, update, delete, and listing of script resources at subscription and resource-group scope, plus the dedicated logs endpoints for retrieving execution output.
8 endpointsJentic publishes the only available OpenAPI specification for DevSpacesManagement, keeping it validated and agent-ready. The API manages Azure Dev Spaces Controllers under Microsoft.DevSpaces — the legacy preview service that paired with AKS to give developers per-developer namespaces and live debugging. It covers controller create, get, update, delete, listing at subscription and resource-group scope, and the listConnectionDetails action used to bootstrap kubectl access.
9 endpointsJentic publishes the only available OpenAPI specification for DevTestLabsClient, keeping it validated and agent-ready. The API is the full management surface for Azure DevTest Labs under Microsoft.DevTestLab — labs, virtual machines, formulas, custom images, ARM templates, artifacts, schedules, policies, environments, and disks. Across 132 endpoints it covers every step of provisioning self-service dev/test environments, scheduling auto-shutdown, and enforcing per-user quotas without giving developers direct subscription access.
132 endpointsJentic publishes the only available OpenAPI specification for Diagnostics API Client, keeping it validated and agent-ready. The Azure Diagnostics API Client provides programmatic access to diagnostic detectors, analyses, and category data for Azure App Service sites and App Service Environments. It exposes 22 endpoints that let you list site diagnostic categories, retrieve detector responses for sites and deployment slots, and execute analyses against a running web app. The API is part of the Microsoft.Web resource provider on management.azure.com and is used to surface the same troubleshooting data as the Azure portal Diagnose and solve problems blade.
22 endpointsJentic publishes the only available OpenAPI specification for Dynamics Telemetry, keeping it validated and agent-ready. The Dynamics Telemetry API exposes the operations metadata for the Microsoft.DynamicsTelemetry resource provider — the namespace responsible for telemetry resources used by Microsoft Dynamics workloads on Azure. It exposes a single endpoint that returns the list of CSM operations available on the provider, used for RBAC role authoring, audit, and feature discovery.
1 endpointsJentic publishes the only available OpenAPI specification for Guest Diagnostic Settings, keeping it validated and agent-ready. The Azure Guest Diagnostic Settings API manages reusable diagnostic configurations that describe which Windows event logs, performance counters, and ETW traces should be collected from inside Azure VMs and Arc-managed servers. Operators define a setting once and then attach it to many guests via the companion association API. The API runs against Azure Resource Manager with Azure AD OAuth2 and exposes six list, get, create-or-update, update, and delete operations on the microsoft.insights provider.
6 endpointsJentic publishes the only available OpenAPI specification for Guest Diagnostic Settings Association, keeping it validated and agent-ready. The Azure Guest Diagnostic Settings Association API binds a previously defined guest diagnostic settings resource to a specific target — typically a VM, scale set, or Arc-managed server — so that the configured event logs and perf counters are actually collected from that machine. Operators use it together with the Guest Diagnostic Settings API: the settings define the what, the association defines the where. The API runs against Azure Resource Manager with Azure AD OAuth2 across six list, get, create-or-update, update, and delete operations.
6 endpointsJentic publishes the only available OpenAPI specification for HDInsightJobManagementClient, keeping it validated and agent-ready. The HDInsight Job Management API submits and tracks Hadoop jobs against a running HDInsight cluster via the cluster's WebHCat (Templeton) endpoint. It supports Hive, Pig, Sqoop, MapReduce, and MapReduce streaming job submissions, plus job listing and kill operations. The API runs against the cluster DNS name (e.g. clustername.azurehdinsight.net) and is authenticated with cluster gateway credentials over OAuth2.
10 endpointsJentic publishes the only available OpenAPI specification for InfrastructureInsightsManagementClient, keeping it validated and agent-ready. The Azure Stack Infrastructure Insights admin API surfaces region health alerts for an Azure Stack Hub stamp so operators can list, inspect, and repair alerts raised by the platform. It exposes 4 ARM admin endpoints under Microsoft.InfrastructureInsights.Admin/regionHealths to enumerate alerts in a location and trigger a repair workflow on an individual alert.
4 endpointsJentic publishes the only available OpenAPI specification for Microsoft Insights, keeping it validated and agent-ready. This Azure Monitor surface manages Scheduled Query Rules, the alert rules that run a Kusto query on a Log Analytics workspace at a defined cadence and trigger actions when a threshold is met. Use it to create, list, retrieve, update, and delete scheduled query rules across a subscription or a single resource group. Authentication is via Azure Active Directory OAuth 2.0 on Azure Resource Manager.
6 endpointsJentic publishes the only available OpenAPI specification for Microsoft.ResourceHealth, keeping it validated and agent-ready. The Resource Health API exposes the current and historical availability state of every Azure resource in a subscription, alongside platform-emerging issues that affect entire services or regions. Operators and AI agents can query availability statuses for individual resource URIs, list child availability statuses for parent resources like virtual machine scale sets, and surface emerging issues directly into incident response workflows. Status values include Available, Unavailable, Degraded, and Unknown, with reason codes that explain platform-initiated outages versus user-initiated downtime.
10 endpointsJentic publishes the only available OpenAPI specification for this Azure Monitor management event types endpoint, keeping it validated and agent-ready. The MonitorManagementClient 2015-04-01 surface exposes a single read endpoint that returns the list of management event types available for an Azure subscription. Management events represent control-plane operations such as resource creation, deletion, and policy changes recorded in the Azure activity log. The returned event types form the vocabulary used to filter activity log queries and to construct alert rules that trigger on specific control-plane operations.
1 endpointsJentic publishes the only available OpenAPI specification for Azure Network Experiments, keeping it validated and agent-ready. The Microsoft.Network NetworkExperiments resource provider, also known as Azure Internet Analyzer, lets engineering teams measure the real-world latency that end users see between their clients and a set of candidate endpoints. Operators define a NetworkExperiment Profile, configure one or more A/B experiments comparing endpoints, and pull back latency scorecards and time series data from real client measurements. The 2019-11-01 surface covers experiment lifecycle, preconfigured endpoints, latency scorecards, time series, and report generation.
14 endpointsJentic publishes the only available OpenAPI specification for Service Map, keeping it validated and agent-ready. The Azure Service Map API exposes the Microsoft.OperationalInsights/serviceMap feature inside a Log Analytics workspace, giving agents a structured view of every machine, process, listening port, and TCP connection that the Dependency Agent has observed. It models machines, machine groups, client groups, processes, ports, and connections, and produces an on-demand topology map that shows which services talk to which on each host.
25 endpointsJentic publishes the only available OpenAPI specification for Visual Studio Projects Resource Provider Client, keeping it validated and agent-ready. This Azure Resource Manager API exposes the microsoft.visualstudio pipelineTemplates resource — a list of pipeline templates available when bootstrapping CI/CD for a new Visual Studio Team Services / Azure DevOps project. Agents typically use it during project bring-up to discover the templates that can be applied automatically. Authentication uses Azure Active Directory OAuth 2.0.
1 endpointsJentic publishes the only available OpenAPI specification for Visual Studio Resource Provider Client, keeping it validated and agent-ready. This Azure Resource Manager API manages Visual Studio Team Services accounts and projects as ARM resources under the microsoft.visualstudio provider. Agents can list provider operations, check whether an account name is available, create or update an account in a resource group, attach extensions to that account, and create projects under the account. Authentication uses Azure Active Directory OAuth 2.0 against management.azure.com.
15 endpointsThe Azure Workload Monitor API surfaces health monitoring data for workloads running on Azure resources, including components, monitors, monitor instances, and notification settings under the Microsoft.WorkloadMonitor provider. It exposes 13 operations across 11 resource paths covering subscription-wide summaries, per-resource component listings, monitor configuration retrieval, and notification configuration. Use it to inventory monitored components, retrieve health status for individual monitor instances, and roll up workload health into dashboards or alerts.
13 endpointsStep 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.