Common Datadog Mapping Mistakes in OIC Integrations

During recent reviews of Datadog error logging for OIC integrations, the following common mapping issues were identified. These need to be addressed to ensure accurate monitoring, correct ticket routing, and proper error categorization.

🔎 Observed Common Mistakes

1. Environment is populated as DEV/SIT/NA in OIC SIT test. It should be strictly set to SIT when testing in SIT.
2. Either Source or Target marked as NA.
3. RICEF ID is missing.
4. Different application names used in Source, such as: CCS vs Oracle CCS ,PPM vs Oracle PPM
5. Instance ID logged is not the actual service where the error happened, but rather the Datadog logging service ID.
6. Error Severity is missing. (In past days, all entries showed severity as "Error". The team should clearly distinguish between Info vs Error.)
7. Error Type is missing or incorrectly populated.
8. Values other than Technical or Business are used. Currently, all executions are logged as Technical error. Data validation errors should be categorized under Business Error, otherwise all tickets will be routed to the OIC team.
9. Short Description or Error Description is missing. ErrorDescription should contain a detailed message, but some entries contain only a custom summary.
10. Created By user field is not properly populated. It should indicate: OIC user (if triggered internally), or API key user (if invoked from external API).
11. Error Categorization not clearly defined: TECHNICAL ERROR vs BUSINESS ERROR.