In Cel-based integrations, an issue has been observed as detailed here, where guard conditions like has(x.f) && size(x.f) != 0 do not handle cases where the field is null, which can lead to runtime failures.
It appears some of our packages are also affected, as listed below:
| Integration |
Data stream |
| Mongodb_atlas |
1. Disk
2. Hardware
3. Mongod_audit
4. Mongod_database
5. Process |
| O365_metrics |
Teams_call_quality |
| Ess_billing |
Billing |
These should be reviewed and updated to include a null check (e.g., x.f != null) where appropriate.
In Cel-based integrations, an issue has been observed as detailed here, where guard conditions like has(x.f) && size(x.f) != 0 do not handle cases where the field is null, which can lead to runtime failures.
It appears some of our packages are also affected, as listed below:
2. Hardware
3. Mongod_audit
4. Mongod_database
5. Process
These should be reviewed and updated to include a null check (e.g., x.f != null) where appropriate.