8 posts tagged with "TM Observability"

The batch transaction response status now includes two additional intermediate values:

• pending_ingestion
• ingestion_in_progress

This applies to batch transaction status responses in the Observability API.

Poll the execution status summary from the Observability API using the execution_id. This works for both tenants using either the Rule Rerun API or the Rule Execution API endpoints

• GET /api/v1/rules/execution?execution_id={execution_id}

Request and retrieve data export reports for specific dates through the Transaction Monitoring Observability API.

The response now includes reject_on_invalid and error message in the response for observability batch transaction API.

The response now includes rule_description. The alert_count field has been removed and replaced with total_alerts_received and unique_alerts_after_deduplication in the response for obervability rule execution API.

Includes pre-signed URLs in the response for batch transaction error file.

Fetch batch transaction information either by batch IDs or by date range.

Fetch summary of successful and failed requests sent to the TM Transaction API