MSAMM
Back to course

Oracle Integration Cloud: Building Integrations That Survive Production · Module 13 · Monitoring, tracking and alerting

Payload retention, and its limits

Lesson 130 of 175 · 2 min

How long instance data is kept and what is purged. Designing so that a question asked NEXT MONTH is still answerable. Instance data does not last forever, and the retention window is shorter than the questions people ask. A finance query about last quarter arrives after the instances from last quarter have been purged, and the console then has nothing at all — not an empty result, not a partial one: the runs are gone. SO THE MONITORING CONSOLE IS AN OPERATIONAL TOOL, NOT AN ARCHIVE, and designing as though it were an archive is the mistake. It answers "what happened last night" extremely well and "what happened in March" not at all. THE DESIGN CONSEQUENCE IS THAT ANYTHING YOU WILL NEED TO ANSWER LATER MUST BE WRITTEN SOMEWHERE THAT PERSISTS. A record in the target system carrying the source reference is usually the best answer, because it lives as…

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Oracle Integration Cloud: Building Integrations That Survive Production, with a certificate on completion and a fourteen-day refund window.

See the course and enrol9 free lessons

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 13 · Monitoring, tracking and alerting

  1. 1The monitoring console
  2. 2Tracking variables: the one design decisionFree preview
  3. 3Reading a failed instance
  4. 4Payload retention, and its limits
  5. 5Errors versus rejections in the console
  6. 6Alerting: who, when, how loud
  7. 7The silent failure: nothing ran
  8. 8Reporting to the business
  9. 9What breaks: the integration nobody knew had stopped
  10. 10Lab briefing · Make a failure visible in five minutes