--- schema_version: "1" id: e18ce71f70e838c69a42328ed97ed8eb8696b7c80f72d687d77a62b0dbfbd82d title: "FAQ: Anypoint Monitoring Logs, Metrics, Alerts, and Limits" collection: mulesoft version: current locale: en-us portal_url: https://docs.salesforce.com/mulesoft/current/en-us/monitoring/am-faq.md canonical_url: https://docs.mulesoft.com/monitoring/am-faq source_site: docs.mulesoft.com content_type: documentation content_hash: 308fcefcac6557ff9ba69126204c8e58ec4b01a5f0ea999cbb8a9aa521c16264 description: Answers to frequently asked questions about logs, metrics, alerts, traces, data retention, performance, and limits in MuleSoft Anypoint Monitoring. latest: true --- --- product: Monitoring description: Answers to frequently asked questions about logs, metrics, alerts, traces, data retention, performance, and limits in MuleSoft Anypoint Monitoring. keywords: MuleSoft, Anypoint Monitoring, FAQ, logs, metrics, alerts, traces, data retention, performance limits, troubleshooting, Anypoint Monitoring limits --- # FAQ: Anypoint Monitoring Logs, Metrics, Alerts, and Limits > For the full documentation index, see: https://docs.mulesoft.com/llms.txt Get answers to common questions about Anypoint Monitoring logging, metrics, alerts, traces, traffic data availability, performance impact, storage and retention limits, log line constraints, log forwarding, and what happens to your data when your subscription changes. ## Logs Learn how logs are stored, constraints on log line length, deletion behavior, log forwarding, and how to retrieve log data. - [Storage and Limits](#log-storage-limits) - [How does Anypoint Monitoring calculate log storage, and what are the limits?](#searchable-log-storage) - [What happens when the log storage limit is reached?](#storage-limit-reached) - [Log Lines](#log-lines) - [What is the maximum length for a single log line, and what happens if my data exceeds it?](#log-line-length) - [Log Deletion and Recovery](#log-deletion-recovery) - [Can I delete logs for specific applications and dates?](#delete-logs) - [If I raise a support case to delete logs, what will MuleSoft delete?](#support-case-deletion) - [Can I recover logs that have been deleted or overwritten?](#recover-deleted-logs) - [Can I import log data back into the system after deletion?](#import-logs) - [What happens to logs after I delete an application?](#logs-after-app-deletion) - [Does purging application logs in Runtime Manager require any special deployment configuration?](#rm-log-purge-config) - [Log Availability](#log-availability) - [Why is there a delay between the Anypoint Monitoring UI and the Archive API data?](#archive-api-delay) - [Why is my application not appearing in the Anypoint Monitoring log search filter?](#app-not-in-filter) - [Are Mule runtime logs available in Anypoint Monitoring log search?](#mule-ee-logs) - [Log Forwarding](#log-forwarding) - [If I disable Anypoint Monitoring for a CloudHub 1.0 application, will logs still be forwarded to Anypoint Platform?](#cloudhub1-disable-monitoring) - [Can I disable Anypoint Monitoring log forwarding while keeping metrics collection enabled?](#disable-log-forwarding) - [Runtime Fabric](#log-rtf) - [How does Anypoint Monitoring connect to Runtime Fabric, and how many connections does it use?](#rtf-connections) - [What subscription does Runtime Fabric require for Anypoint Monitoring?](#rtf-subscription) - [Subscription Changes](#log-subscription-changes) - [What happens to log data when I change my subscription?](#subscription-change-logs) ### Storage and Limits #### How does Anypoint Monitoring calculate log storage, and what are the limits? Anypoint Monitoring stores raw logs and searchable logs separately: - Searchable logs are stored as indexes on top of raw logs to support fast queries, but cover only the most recent logs up to 10% of your purchased storage. Total searchable storage across your organization is capped at 6 TB regardless of the number of vCores or flows you purchased. - Raw logs are stored in archival storage and can be scoped by business group, environment, application, and date range. Anypoint Monitoring creates indexes on raw logs to enable fast log search queries. To retrieve logs beyond the searchable storage, use the [Anypoint Monitoring Archive API](https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/anypoint-monitoring-archive-api/minor/1.0/pages/Metric%20Data/). For more detail, see [Raw Data in Anypoint Monitoring](https://docs.mulesoft.com/monitoring/raw-data). Storage per unit purchased varies by subscription tier:
Subscription TierUnit PurchasedArchival Storage (Raw Logs)Searchable Storage

Anypoint Integration Advanced

1 flow

5 GB

0.5 GB

Anypoint Integration Advanced

1M messages

2.5 GB

0.25 GB

Titanium

1 production vCore

200 GB

20 GB

Titanium

1 pre-production vCore

50 GB

5 GB

#### What happens when the log storage limit is reached? When storage reaches capacity, the oldest logs are deleted first to reclaim space. ### Log Lines #### What is the maximum length for a single log line, and what happens if my data exceeds it? The maximum length for a single log line is 8 KB, including date and thread metadata. Lines longer than 8 KB are truncated at the 8 KB mark. To log data that exceeds this limit, split it into chunks that are each smaller than 8 KB. ### Log Deletion and Recovery #### Can I delete logs for specific applications and dates? No. You can’t delete logs directly. If sensitive data is exposed in logs, raise a support case with MuleSoft. MuleSoft accepts log deletion requests only when sensitive data is exposed. #### If I raise a support case to delete logs, what will MuleSoft delete? The answer differs for raw logs and searchable logs. **Raw logs** can be scoped by business group, environment, application, and date range (GMT). MuleSoft can delete a targeted subset of raw logs without affecting other data. **Searchable logs** cannot be scoped by business group, environment, or application. Deletion is performed by dropping whole indices under the root organization. Under the current multitenant Log Search architecture on Hyperforce, a single searchable-log index can span several days, weeks, or months. The exact coverage depends on your stock-keeping unit (SKU), index size, and storage usage. As a result, the actual date range deleted will be equal to or larger than the range you request — in some cases by a significant margin. Before executing the deletion, MuleSoft runs a dry-run of the operation and shares the cumulative date range that will be dropped, along with the list of affected indices, so you can confirm before proceeding. > [!WARNING] Deleted logs cannot be recovered or re-imported. Review the dry-run results carefully > before confirming. #### Can I recover logs that have been deleted or overwritten? No. After logs are deleted or overwritten, they can’t be recovered. #### Can I import log data back into the system after deletion? No. You can’t import logs back into the system after deletion. #### What happens to logs after I delete an application? Anypoint Monitoring and Runtime Manager are separate systems with independent log retention policies. Deleting an application in Runtime Manager does not immediately remove its logs from Anypoint Monitoring. Logs stored in Anypoint Monitoring remain accessible after an application is deleted from Runtime Manager. Retrieve these logs using the [Anypoint Monitoring Archive API](https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/anypoint-monitoring-archive-api/minor/1.0/pages/home/). Anypoint Monitoring deletes the oldest logs first when storage capacity is reached. For details on Anypoint Monitoring storage limits, see [How does Anypoint Monitoring calculate log storage, and what are the limits?](#searchable-log-storage). Runtime Manager maintains its own log storage with separate limits and rotation behavior. For Runtime Manager log retention details, see [Log Persistence (Anypoint Runtime Manager)](https://docs.mulesoft.com/cloudhub/viewing-log-data#log-persistence). If your apps are deployed to CloudHub 2, see also [CloudHub 2.0 Logging FAQ](https://help.salesforce.com/s/articleView?id=001119527&type=1). > [!NOTE] Log removal operations in Anypoint Monitoring are organization-wide, not > application-specific. To request log deletion due to sensitive data exposure, see > [If I raise a support case to delete logs, what will MuleSoft delete?](#support-case-deletion). #### Does purging application logs in Runtime Manager require any special deployment configuration? No. You can purge application logs in Runtime Manager regardless of how the application is deployed. No specific deployment configuration is required. For instructions, see [Viewing Log Data in Runtime Manager](https://docs.mulesoft.com/cloudhub/viewing-log-data). > [!NOTE] Purging logs in Runtime Manager affects only the logs stored within Runtime Manager. It > does not affect logs stored in Anypoint Monitoring, which are managed independently. ### Log Availability #### Why is there a delay between the Anypoint Monitoring UI and the Archive API data? The Archive API is backed by an archival storage backend. A file becomes available for download when it reaches either 9 minutes of accumulation or 10 MB in size, whichever comes first. The delay between the UI and Archive API occurs because the Archive API’s batch process accumulates data before a file becomes available, while the UI uses a real-time search engine. #### Why is my application not appearing in the Anypoint Monitoring log search filter? The app doesn’t appear in the filter when recent log lines are unavailable or when a large number of apps are reporting recent logs. For more information, see [Not All Apps Are Showing in the Left Sidebar in Anypoint Monitoring](#apps-not-showing-sidebar.adoc). #### Are Mule runtime logs available in Anypoint Monitoring log search? No. You can’t view on-premises `mule_ee.log` files directly through Anypoint Monitoring log search. ### Log Forwarding #### If I disable Anypoint Monitoring for a CloudHub 1.0 application, will logs still be forwarded to Anypoint Platform? Yes. If you disable Anypoint Monitoring by setting the following property: ```text anypoint.platform.config.analytics.agent.enabled=false ``` Logs are still forwarded to Anypoint Platform and remain visible in the Anypoint Monitoring logs UI. #### Can I disable Anypoint Monitoring log forwarding while keeping metrics collection enabled? Yes. The steps vary by deployment target: - **CloudHub 1.0**: See [How to Disable Log Forwarding to the Anypoint Monitoring Titanium Backend](#cloudhub-disable-log-forwarding.adoc). - **CloudHub 2.0**: Private space and shared space have separate procedures. See [Disable Log Forwarding in CloudHub 2.0](#ch2-disable-log-forwarding.adoc). - **Hybrid/on-premises**: See [Disable Log Forwarding for Hybrid Deployments](#hybrid-disable-log-forwarding.adoc). ### Runtime Fabric #### How does Anypoint Monitoring connect to Runtime Fabric, and how many connections does it use? Each Runtime Fabric app has a sidecar container that makes one persistent connection to Anypoint Monitoring to send logs. Each pod uses one connection. #### What subscription does Runtime Fabric require for Anypoint Monitoring? All deployment targets include a basic level of monitoring with the base subscription. Runtime Fabric requires a Platinum subscription for general monitoring. Certain features, such as logging, require a Titanium subscription. ### Subscription Changes #### What happens to log data when I change my subscription? Log data is lost and the storage that held it is terminated within an hour when you change subscriptions — for example, from Titanium to Platinum or from Platinum to Titanium. Log infrastructure changes are not migrated. Log data is also lost when moving from a Titanium trial to a paid Titanium subscription, because trials run on a multitenant cluster that is separate from the dedicated single-tenant infrastructure used for paid Titanium. > [!IMPORTANT] Back up any logs you need before changing your subscription. Log data cannot be > recovered after the change takes effect. ## Metrics Learn what metrics Anypoint Monitoring provides, how long data is retained, how to query traffic and consumption data, and how to access metrics programmatically. - [Retention](#metrics-retention) - [How long does Anypoint Monitoring retain application metrics?](#application-metrics-retention) - [How long does Anypoint Monitoring retain enhanced API metrics?](#enhanced-api-metrics-retention) - [Subscription Changes](#metrics-subscription-changes) - [What happens to my metrics data if I downgrade or cancel my Anypoint Monitoring subscription?](#subscription-change-metrics) - [Traffic and Aggregation](#metrics-traffic-aggregation) - [Can I get VPC-level network traffic metrics from Anypoint Monitoring?](#vpc-traffic-metrics) - [Can I get monthly outbound traffic totals from Anypoint Monitoring?](#outbound-traffic-totals) - [Does Anypoint Monitoring aggregate application metrics across environments or business groups?](#cross-env-aggregation) - [Metrics API](#metrics-api) - [Why does my Metrics API query return empty data even though the dashboard shows metrics?](#metrics-api-empty-data) - [What attributes should I use to query application traffic data via the Metrics API?](#metrics-api-traffic-attributes) - [Archive API](#metrics-archive-api) - [How can I access API analytics metrics data programmatically?](#access-api-analytics-metrics) - [Can I export historical custom metrics in bulk using the Archive API?](#archive-api-custom-metrics) ### Retention #### How long does Anypoint Monitoring retain application metrics? Retention (how long data is stored) and the lookback window (how far back you can query in the [Anypoint Insights](https://docs.mulesoft.com/monitoring/anypoint-insights) UI) are separate limits.
TierData retentionIndividual app and API Lookback WindowCross-entity Lookback Window

Advanced and Titanium

365 days for built-in and custom metrics

Up to 90 days within the 365 day retention period

7 days

Starter

30 days

Up to 30 days

24 hours

Gold/Platinum

30 days

Up to 30 days

7 days

The cross-entity overview page in Anypoint Insights shows aggregate totals across multiple apps and APIs, such as total requests and error rate. Lookback windows for individual app and API UIs that you access from the overview page are longer. #### How long does Anypoint Monitoring retain enhanced API metrics? Anypoint Monitoring retains enhanced API metrics for 30 days across all subscription tiers. These additional limits apply regardless of tier: - Data in the **Client Applications** tab is limited to one hour. - Data from the `api_path_metric` and `api_client_ip_metric` tables in advanced mode of custom dashboards is limited to one hour. > [!NOTE] Metrics data can persist beyond the stated retention period. Data is removed when the > automated cleanup cycle runs. ### Subscription Changes #### What happens to my metrics data if I downgrade or cancel my Anypoint Monitoring subscription? Unlike log data, metrics data is retained for a grace period before removal: - **Downgrade** — approximately 14 days after the downgrade takes effect, a 21-day grace period begins before your data is removed. - **Cancellation** — approximately 90 days after cancellation, a 21-day grace period begins before your data is removed. To retrieve metrics data before it is removed, use the [Anypoint Monitoring Archive API](https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/anypoint-monitoring-archive-api/minor/1.0/pages/Metric%20Data/). ### Traffic and Aggregation #### Can I get VPC-level network traffic metrics from Anypoint Monitoring? No. Anypoint Monitoring doesn’t provide VPC-level network traffic metrics — such as total inbound or outbound bytes at the VPC or private space boundary. Anypoint Monitoring collects application-level metrics from Mule runtime, not from the underlying network infrastructure. To estimate traffic volumes, use the [Anypoint Monitoring Metrics API](https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/metrics-api/) to query application-level inbound and outbound metrics per Mule application. See [What attributes should I use to query application traffic data via the Metrics API?](#metrics-api-traffic-attributes) for the correct metric names. #### Can I get monthly outbound traffic totals from Anypoint Monitoring? Not directly. Anypoint Monitoring doesn’t provide a prebuilt report or dashboard view for monthly outbound traffic aggregated across all applications. To estimate monthly outbound traffic, use the Metrics API to query `mulesoft.app.outbound` metrics for each application and sum the results. This provides application-level outbound message counts and data volumes as a proxy for network egress. #### Does Anypoint Monitoring aggregate application metrics across environments or business groups? No. Anypoint Monitoring doesn’t aggregate application metrics across environments or business groups in a single dashboard view. Application-level metrics are scoped to individual environments. To aggregate traffic across environments, query the Metrics API separately for each environment and combine the results. > [!NOTE] Anypoint DataGraph usage metrics are an exception — DataGraph provides aggregated GraphQL > API request counts across all environments of a given type (production or sandbox) within a > business group. This aggregation applies only to DataGraph, not to general Mule application > traffic. See [Viewing Usage Metrics for Anypoint DataGraph](https://docs.mulesoft.com/datagraph/usage-metrics). ### Metrics API #### Why does my Metrics API query return empty data even though the dashboard shows metrics? A Metrics API query can return a 200 OK response with `"data": []` when the Connected App used to generate the Bearer token lacks the required environment-level scopes for the target environment. To resolve this, grant the Connected App the following permissions for each business group and environment you want to query: - **API Configuration Viewer** - **Read Applications** Without these permissions, the API returns empty data rather than a permission error. For details, see the [Anypoint Monitoring Metrics API](https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/metrics-api/) documentation. #### What attributes should I use to query application traffic data via the Metrics API? Use the following metrics for application-level traffic data: - `mulesoft.app.inbound` — inbound message count and volume at the application level, with endpoint-level dimensions - `mulesoft.app.outbound` — outbound message count and volume at the application level, with endpoint-level dimensions Don’t use `endpoint.type` or `endpoint.operation` as query attributes on the `mulesoft.api.summary` metric. These attributes were removed from `mulesoft.api.summary`. The same restriction applies to `mulesoft.api.path`, `mulesoft.api.client_ip`, and `mulesoft.api.geo_location` on that metric. For endpoint-level dimensions, use `mulesoft.app.inbound` and `mulesoft.app.outbound` instead. ### Archive API #### How can I access API analytics metrics data programmatically? You can access API analytics metrics data directly via the [Anypoint Monitoring Archive API](https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/anypoint-monitoring-archive-api/minor/1.0/pages/home/), available to Anypoint Integration Advanced and Titanium subscribers. The Archive API exposes your metrics data in a directory hierarchy you can navigate and download as files containing JSON objects, each representing one or more metric events. You can write an application to traverse the data and integrate it into your own system. To also capture non-aggregated API events — which contain more detailed information about each API invocation — enable them by setting the following property: ```text anypoint.platform.config.analytics.agent.api_raw_metrics.enabled=true ``` Non-aggregated events are accessible under the `raw` file type in the Archive API. #### Can I export historical custom metrics in bulk using the Archive API? No. The Anypoint Monitoring Archive API doesn’t support bulk export of custom metrics. To retrieve application and API metrics via the Archive API, see [How can I access API analytics metrics data programmatically?](#access-api-analytics-metrics). ## Alerts - [What are the alert limits in Anypoint Monitoring?](#alert-limits) ### What are the alert limits in Anypoint Monitoring? Alert limits vary by alert type and subscription tier:
Alert TypeStarterAdvancedGold/PlatinumTitanium

Custom dashboard alerts

—

10 per app or API instance

—

20 per parent organization

Basic alerts for servers and Mule apps

—

10 per server or app

50

50 × production vCores + 100

Basic alerts for APIs

—

10 per server or app

6 per API instance

10 per API instance

Starter and Gold/Platinum tiers have no allowance for custom dashboard alerts. > [!NOTE] For Titanium, your basic alert allowance for servers and Mule apps can also be used for > sandbox deployments, subject to the overall > [production vCore limit](https://docs.mulesoft.com/access-management/business-groups#redistribute-resources). ## Telemetry Exporter - [What are the Telemetry Exporter connection limits?](#telemetry-exporter-limits) - [What are the known issues for Telemetry Exporter?](#telemetry-exporter-known-issues) ### What are the Telemetry Exporter connection limits? Anypoint Monitoring supports up to 10 Telemetry Exporter connections per organization for Anypoint Integration Advanced and Titanium subscribers. ### What are the known issues for Telemetry Exporter? Telemetry Exporter currently has the following data differences, limitations, and known issues: - For failed requests, Telemetry Exporter retries are handled using the OpenTelemetry specifications for handling failures: - Permanent failures, such as bad requests, do not retry. - 5xx errors that can retry wait for a specific interval. Retries continue for 300 seconds before timing out. - When you create configurations for the same connection, you cannot create a configuration that uses all business groups if there are configurations that use individual business groups. Conversely, you cannot create configurations for that connection if there is a configuration that uses all business groups. For example, `Connection A` to Splunk has `Configuration A` and `Configuration B` that map to `Business Group A` and `Business Group B`. In this scenario, you are unable to use `Connection A` to create a configuration that exports data from all business groups. - Because Azure Monitor Exporter does not support sending persistent queues, connections that use it might experience data loss. Data might be deleted from the sending queue when the Telemetry Exporter restarts hourly to apply updates. - The audit logs that the Telemetry Exporter sends to third-party apps often have different field names from the audit logs that appear in Access Management or the Audit Query Log API. For example, audit logs shown in the UI or retrieved by the Audit Log Query API describe a user action (such as `update` or `delete`) as `action`, whereas the OpenTelemetry attribute refers to it as `mulesoft.audit.action`. - If the audit log entry metadata and payload field exceed 30KB when compressed, the payload is truncated before compression. For full Telemetry Exporter setup and configuration, see [Exporting Telemetry Data to Third-Party Monitoring Systems](https://docs.mulesoft.com/monitoring/telemetry-exporter). ## Traces Traces in Anypoint Monitoring (open beta, Titanium only) let you track requests as they travel through service pipelines using OpenTelemetry span data. For full documentation, see [Examining Traces](https://docs.mulesoft.com/monitoring/traces). - [What is the sampling rate for trace data in Anypoint Monitoring?](#traces-sampling-rate) ### What is the sampling rate for trace data in Anypoint Monitoring? Trace data sampling rates vary by entity type: - **100%**: Agents, brokers, and MCP servers - **10%**: Mule apps and APIs A 10% sampling rate for Mule apps and APIs means that only one in ten requests is captured as a trace. This applies to Mule runtime 4.6 or later deployed to CloudHub 2.0 or Runtime Fabric (limited availability). For more information about traces and supported entity types, see [Examining Traces](https://docs.mulesoft.com/monitoring/traces). ## Performance - [What is the performance impact of Anypoint Monitoring on my Mule applications?](#performance-impact) ### What is the performance impact of Anypoint Monitoring on my Mule applications? The expected CPU utilization from the Mule monitoring agent is less than 5% based on typical use. Anypoint Monitoring collects data asynchronously at a one-minute resolution, so monitoring activity does not block Mule runtime data processing. For deployment-specific configuration, see [Configure and Enable Anypoint Monitoring for Mule Apps (CloudHub)](https://docs.mulesoft.com/monitoring/configure-monitoring-cloudhub#performance-impact). ## See Also - [Anypoint Monitoring](https://docs.mulesoft.com/monitoring/) - [Logs in Anypoint Monitoring](https://docs.mulesoft.com/monitoring/logs) - [Examining Traces](https://docs.mulesoft.com/monitoring/traces) - [Exporting Telemetry Data to Third-Party Monitoring Systems](https://docs.mulesoft.com/monitoring/telemetry-exporter) - [Anypoint Monitoring Metrics API](https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/metrics-api/) - [Configure and Enable Anypoint Monitoring for Mule Apps (CloudHub)](https://docs.mulesoft.com/monitoring/configure-monitoring-cloudhub) - [Anypoint Insights](https://docs.mulesoft.com/monitoring/anypoint-insights) - [Anypoint Monitoring Archive API](https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/anypoint-monitoring-archive-api/minor/1.0/pages/home/) - [Raw Data in Anypoint Monitoring](https://docs.mulesoft.com/monitoring/raw-data) - [Viewing Usage Metrics for Anypoint DataGraph](https://docs.mulesoft.com/datagraph/usage-metrics) - [Log Persistence (Anypoint Runtime Manager)](https://docs.mulesoft.com/cloudhub/viewing-log-data#log-persistence) - [CloudHub 2.0 Logging FAQ](https://help.salesforce.com/s/articleView?id=001119527&type=1)