AWS Amazon CloudWatch Application Insights
Browse all Amazonaws APIs✓ Official Vendor SpecDeveloper ToolsMonitoring ObservabilityapiKey27 EndpointsREST
For Agents
Use the Amazon CloudWatch Application Insights API to detect application issues across CloudWatch metrics, logs, and events on AWS, with 27 operations covering the full control-plane lifecycle.
Use for: Onboard my resource group to Application Insights, List all detected problems in my application, Get the observations that triggered a specific problem, Set up a log pattern that flags database deadlocks as high severity
Not supported: Does not handle metric ingestion, log storage, or distributed tracing — use for cross-component problem detection on top of existing CloudWatch data only.
CloudWatch Application Insights detects issues across the components of an application by analysing CloudWatch metrics, logs, and events. It builds an application model from resource groups, recognises common workloads such as SQL Server and .NET, and surfaces likely root causes as observations and problems.
Install Jentic One Beta
Connect the Amazon CloudWatch Application Insights to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Amazon CloudWatch Application Insights, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 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 | sh2
Step 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.
Capabilities
What an agent can do with Amazon CloudWatch Application Insights API.
Onboard a resource group as an Application Insights application with auto-configured component detection
Define components that group EC2 instances, RDS databases, or other resources by role
Configure log patterns that classify CloudWatch Logs entries by severity
Browse detected problems with correlated observations across components
Inspect observations that link metrics, logs, and CloudWatch events to a problem
Update component configuration to refine monitoring rules over time
Use Cases
Patterns agents use Amazon CloudWatch Application Insights API for, with concrete tasks.
★ Automated problem detection for a Windows .NET stack
Onboard a resource group containing IIS web servers, .NET application servers, and a SQL Server backend to Application Insights, which then auto-detects the workload and configures CloudWatch metrics, logs, and events monitoring across the components. Detected problems combine signals from all components into a single root-cause narrative. Initial onboarding is typically under an hour.
Create an Application Insights application against the 'orders-prod' resource group, then list any detected problems with their observation counts.
Log-pattern-driven incident classification
Create custom log patterns that match application-specific error strings — for example custom checkout exceptions or database deadlock messages — and assign severity levels. Application Insights then incorporates pattern matches into its problem detection and observation feeds, raising the priority of incidents that match high-severity patterns. Configuration takes minutes per pattern.
Create a log pattern named 'checkout-deadlock' with the regex 'CheckoutDeadlockException' and severity HIGH attached to the orders-prod application's pattern set.
Post-deployment regression check
After a new deployment, list the application's detected problems, filter for ones with start times after the deployment, and review their contributing observations to identify whether the release introduced regressions. This automates the manual triage step of comparing dashboards before and after a release. Useful for any team running CloudWatch-monitored workloads.
List all problems for the orders-prod application started in the last hour, then describe observations for any with status 'Open'.
AI agent triaging Application Insights problems through Jentic
An on-call agent can investigate detected problems autonomously by calling Application Insights through Jentic. It searches for problem-listing intents, loads the schemas for ListProblems and DescribeProblemObservations, and executes them with scoped credentials. The agent surfaces a ranked summary of active problems without engineers having to sign in to the CloudWatch console.
Search Jentic for 'list detected problems for an application', load the schemas for ListProblems and DescribeProblemObservations, and execute them against the orders-prod application.
Key Endpoints
27 endpoints — cloudwatch application insights detects issues across the components of an application by analysing cloudwatch metrics, logs, and events.
METHOD
PATH
DESCRIPTION
POST
/#X-Amz-Target=EC2WindowsBarleyService.CreateApplication
Create an Application Insights application
POST
/#X-Amz-Target=EC2WindowsBarleyService.CreateComponent
Add a component to an application
POST
/#X-Amz-Target=EC2WindowsBarleyService.CreateLogPattern
Create a log pattern for log classification
POST
/#X-Amz-Target=EC2WindowsBarleyService.DescribeProblem
Describe a detected problem
POST
/#X-Amz-Target=EC2WindowsBarleyService.ListApplications
List Application Insights applications
POST
/#X-Amz-Target=EC2WindowsBarleyService.DescribeProblemObservations
List observations contributing to a problem
POST
/#X-Amz-Target=EC2WindowsBarleyService.CreateApplication
Create an Application Insights application
POST
/#X-Amz-Target=EC2WindowsBarleyService.CreateComponent
Add a component to an application
POST
/#X-Amz-Target=EC2WindowsBarleyService.CreateLogPattern
Create a log pattern for log classification
POST
/#X-Amz-Target=EC2WindowsBarleyService.DescribeProblem
Describe a detected problem
POST
/#X-Amz-Target=EC2WindowsBarleyService.ListApplications
List Application Insights applications
POST
/#X-Amz-Target=EC2WindowsBarleyService.DescribeProblemObservations
List observations contributing to a problem
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
AWS IAM access keys for Amazon CloudWatch Application Insights are stored encrypted in the Jentic vault. Jentic signs each request with AWS SigV4 at execution time and returns only the API response — raw access keys never enter the agent's context.
Intent-based discovery
Agents express intents like 'detect problems across my application's components' and Jentic returns matching Amazon CloudWatch Application Insights operations along with their input schemas, so the agent picks the right call without browsing the AWS service reference.
Time to first call
Direct Amazon CloudWatch Application Insights integration: 2-5 days for IAM scoping, SigV4 wiring, retry logic, and pagination handling. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Amazon CloudWatch Application Insights API through Jentic.
What authentication does the Amazon CloudWatch Application Insights API use?
The Amazon CloudWatch Application Insights API uses AWS Signature Version 4 (HMAC) request signing with IAM-issued credentials, the same scheme as every AWS service API. Jentic's MAXsystem stores those AWS credentials encrypted in the vault, generates short-lived signed requests at execution time, and never passes raw access keys into the agent's context.
Can I onboard my resource group to application insights with the Amazon CloudWatch Application Insights API?
Yes — the Amazon CloudWatch Application Insights API exposes 27 operations including the actions needed for that scenario. Use the operations listed in the key endpoints section as the starting point, then chain calls as needed for your workflow.
What are the rate limits for the Amazon CloudWatch Application Insights API?
AWS applies per-account, per-region request rate limits to the Amazon CloudWatch Application Insights control plane. Specific limits are not encoded in the OpenAPI spec; consult the AWS service quotas console for the Amazon CloudWatch Application Insights entry, and design retries with exponential backoff to absorb throttling responses.
How do I detect problems across my application's components through Jentic?
Run pip install jentic, then call client.search('detect problems across my application's components') to discover the Amazon CloudWatch Application Insights operations that match. Load the schema for the chosen operation with client.load(...) and execute it with client.execute(...). Jentic handles AWS request signing automatically against the credentials stored in your Jentic vault.
Is the Amazon CloudWatch Application Insights API free to call?
AWS does not charge for control-plane API calls themselves on most Amazon CloudWatch Application Insights operations, but the underlying resources you create or operate (fleets, queries, deployments, and so on) incur usage charges according to the Amazon CloudWatch Application Insights pricing page. Refer to the AWS pricing page for the service to estimate cost.
Which operations should an agent call first when working with the Amazon CloudWatch Application Insights API?
For most workflows, agents should start by listing existing resources to understand the current state, then call the create or update operation that matches the intent. The endpoints listed under Key Endpoints in the catalog give a ranked starting set.
GET STARTED