MSAMM
Back to course

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

The monitoring console

Lesson 127 of 175 · 2 min

Instances, their statuses, and what each status actually means — INCLUDING THE TWO THAT LOOK LIKE SUCCESS AND ARE NOT. The console lists INSTANCES: one row per run of an integration. That is the unit everything in this module works on — you do not monitor an integration, you monitor its instances, and a healthy integration is one whose instances are healthy. THE STATUSES DIVIDE INTO THREE GROUPS AND ONLY THE FIRST IS UNAMBIGUOUS. A FAILED instance is an incident: it stopped, and something needs a person or a retry. An instance still IN PROGRESS is running, or is stuck — which those two states look identical until you compare against how long the flow normally takes. AND THE TWO THAT LOOK LIKE SUCCESS ARE THE POINT OF THIS LESSON. THE FIRST IS COMPLETED-WITH-A-BUSINESS-REJECTION. The integration ran end to end, called the target, received a clean rejection — a validation…

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