Skip to content

W-23259917-CR-DocumentAPIForAlerts-EBM #901

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
emileemooreVT wants to merge 4 commits into
base: latest
Choose a base branch
from
+30 −0
Open

W-23259917-CR-DocumentAPIForAlerts-EBM #901

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
8e9843b
W-23259917-CR-DocumentAPIForAlerts-EBM
emileemooreVT Aug 3, 2026
2c51051
SG Updates
emileemooreVT Aug 3, 2026
a2e9dee
Updates from PM review
emileemooreVT Aug 6, 2026
8bfe6fd
Merge branch 'latest' into W-23259917-CR-DocumentAPIForAlerts-EBM
emileemooreVT Aug 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
30 changes: 30 additions & 0 deletions runtime-manager/modules/ROOT/pages/alerts-on-runtime-manager.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,6 +20,36 @@ Runtime Manager retains thirty days of alert history.
Alerts retrigger when the conditions exceed the specified threshold.
====

== Compare Runtime Manager Alerts and Anypoint Monitoring Alerts

Runtime Manager and Anypoint Monitoring provide different alert systems.
Use the alert page and API for the system that owns the alert you need.

Runtime Manager alerts::
Infrastructure-focused alerts for servers, clusters, and application lifecycle events.
Examples include CPU usage, memory usage, load average, thread count, deployment events, and server connectivity events.
+
Use Runtime Manager REST Services endpoints for these alerts:
+
* Alert configuration (alert definitions): `GET /hybrid/api/v1/alerts` and related alert-definition operations
* Fired-alert history: alert-history endpoints for the alert ID, for example `GET /armui/api/v1/alerts/cloudhub/{alertId}/history`
+
Runtime Manager retains 30 days of alert history.
Runtime Manager alerts retrigger when a condition continues to breach its threshold.
Runtime Manager alerts aren't listed on the Anypoint Monitoring *Alerts* page.

@glenn-rodgers-sf glenn-rodgers-sf Aug 7, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this section could be bullets, but it's not really that important.


Anypoint Monitoring alerts::
Alerts for APIs, Mule applications, and servers, including instance alerts such as response time, request count, policy violations, and HTTP status codes, plus Contracts, Basic, and Advanced alerts. For instance alerts, the sliding window is configurable.
+
Use Anypoint Monitoring alert APIs for:
+
* Alert configuration (alert definitions)
* Fired-alert history
+
Runtime Manager alert endpoints don't return these Anypoint Monitoring alerts.
+
For Anypoint Monitoring alerts, see xref:monitoring::basic-alerts.adoc[Getting Alerts].

You can also create custom alerts for applications deployed to CloudHub and CloudHub 2.0.

Custom alerts in CloudHub are triggered when your application sends notifications to the Runtime Manager console
Expand Down