Question & Answer
Question
Why has the Instana event mapping changed after upgrading from CP4AIOps 4.10.1 to 4.13.1? Is this expected?
Cause
The mapping change is caused by an enhancement introduced in CP4AIOps 4.11.0, where the Instana integration moved from a fixed, built-in connector mapping to JSONata-based event mapping.
Answer
Yes. This change is expected and is a result of an enhancement introduced in CP4AIOps 4.11.0.
In CP4AIOps 4.10.1 and earlier, Instana events used a fixed, built-in mapping within the connector. Starting with CP4AIOps 4.11.0, the Instana integration was enhanced to use JSONata-based mapping, providing greater flexibility to customize alert fields such as Summary, Classification, and Event Type.
As a result, the default mapping behavior in 4.11.0 and later releases, including 4.13.1, may differ from 4.10.1. The observed change in the Instana alert mapping is therefore related to this enhancement and is not an issue with the Instana event data.
The JSONata mapping can also be customized if the previous 4.10.1 alert format is required.
Historical Number
TS022665334
Product Synonym
IBM Cloud Pak for AIOps
IBM Concert Operate
Was this topic helpful?
Document Information
Modified date:
19 August 2026
UID
ibm17283621