Loading

Anypoint Monitoring "endpoint.type" and "endpoint.operation" No Longer Valid on the "mulesoft.api.summary" Metric

Udgivelsesdato: Jul 13, 2026
Beskrivelse

When querying the mulesoft.api.summary metric through the Anypoint Monitoring Metrics API, a query that previously succeeded now fails with:

{
  "message": "'endpoint.type' is not a supported attribute"
}

The same applies to 'endpoint.operation'.

- The failing query typically references endpoint.type and/or endpoint.operation in the SELECT and/or GROUP BY clause against "mulesoft.api.summary".
- The query was unchanged and worked previously.
- The error is returned as an attribute-validation failure (not authentication or syntax).
- The metric descriptor (GET /observability/api/v1/metric_types/mulesoft.api.summary:describe) no longer lists endpoint.type or endpoint.operation in its attributes array.

The same removal also applies to the other API-level metrics: mulesoft.api.path, mulesoft.api.client_ip, and mulesoft.api.geo_location.

Løsning

CAUSE

endpoint.type and endpoint.operation are endpoint-level dimensions. The mulesoft.api.summary metric (and the other API-level metrics listed above) is an API-level aggregation whose underlying events do not carry endpoint-level dimensions.

These attributes were incorrectly exposed in the metric descriptor. Because the data never existed at this aggregation level, any query grouping or filtering by them returned null values, which was a source of confusion. The attributes were therefore removed from the descriptor so the schema accurately reflects the data the metric can return.

This is an intended correction, not an outage or regression. No data was lost, these fields were already returning null on mulesoft.api.summary.

SOLUTION

Choose the option that matches what you need:

1. If you do not need endpoint-level breakdown (most cases):
Remove endpoint.type and endpoint.operation from the SELECT and GROUP BY clauses of your query. All other attributes (e.g. api.version, http.status_code, policy.id, flow.id, env.id, sub_org.id) remain valid and unaffected.

2. If you require endpoint-level dimensions (endpoint.type, endpoint.operation):
Query an application-level metric instead, where these attributes are legitimately populated:
- mulesoft.app.inbound
- mulesoft.app.outbound

Vidensartikelnummer

005388832

 
Indlæser
Salesforce Help | Article