SERVERLESS_ALERTS to report Alert ID, not Task ID (Pending)

Attention

This behavior change is in the 2026_04 bundle.

For the current status of the bundle, refer to Bundle history.

When this behavior change bundle is enabled, rows in the ACCOUNT_USAGE.METERING_HISTORY and ORGANIZATION_USAGE.METERING_HISTORY views where SERVICE_TYPE is SERVERLESS_ALERTS behave as follows.

This behavior change applies only to new metering data recorded after the bundle is enabled in your account. Existing rows in METERING_HISTORY are not rewritten; they continue to show the ENTITY_ID and ENTITY_TYPE values that were stored when those rows were ingested.

Before the change:

For newly recorded SERVERLESS_ALERTS rows in those METERING_HISTORY views, ENTITY_TYPE is 'TASK' and ENTITY_ID does not identify the alert.

After the change:

For newly recorded SERVERLESS_ALERTS rows in those METERING_HISTORY views, ENTITY_TYPE is 'ALERT' and ENTITY_ID identifies the alert.

Customer readiness

Customers should update any queries, dashboards, or automation that reference ENTITY_ID or filter on ENTITY_TYPE = 'TASK' for SERVERLESS_ALERTS rows in METERING_HISTORY (ACCOUNT_USAGE or ORGANIZATION_USAGE) to use ENTITY_TYPE = 'ALERT' and the alert identifier in ENTITY_ID.

Suggested diagnostic steps

Review any queries or workflows that use METERING_HISTORY in ACCOUNT_USAGE or ORGANIZATION_USAGE and filter on SERVICE_TYPE = 'SERVERLESS_ALERTS'. Then update references from ENTITY_TYPE = 'TASK' to ENTITY_TYPE = 'ALERT', and adjust any joins on ENTITY_ID to use the identifier from rows where ENTITY_TYPE is 'ALERT'.

Engineering details: BCR-2261 (epic BCR-2144).

Ref: 2261