Management by Exception: Take Control of Integration Errors
In this sixth and final episode of the Fluxygen Integration series for transportation and logistics, you’ll learn how to monitor integrations, centrally log errors, and follow up in a targeted manner when something goes wrong.
We’ll wrap up the integration between a TMS and a visibility platform with Management by Exception. You’ll set up centralized error monitoring, define functional exceptions, log errors in a database, and build an automated hourly error report with email notifications. We’ll also explore how certain errors can be automatically resolved.
🔍 In this video, you’ll learn:
- What Management by Exception is and how to apply it within Fluxygen
- Why Flow Tracing alone is not sufficient for structural production monitoring
- Centralizing the logging of technical errors with Error Route Monitoring (ERM)
- Setting up a central database for error logging
- Working with PostgreSQL and the necessary database connection details
- Importing and applying the ERM component to a flow’s error route
- How to store error details, such as flow name, environment, timestamp, breadcrumb ID, and error message
- How to define functional exceptions based on expected results
- How to use Flow Function Monitoring (FFM) for deviations in the business flow
- How to validate JSON results using JQ expressions and a content router
- How to test, analyze, and retrieve errors via Fluxygen Flow Tracing and the database
- Log HTTP errors, such as 404 responses, as functional exceptions
- Options for automatic error handling, such as throttling for HTTP 429 and updates for HTTP 409
- Prioritize monitoring based on the importance of integrations and error budgets
- Build an hourly error report using SQL, a scheduler, a filter, and an email component
- Automatically send error reports as email attachments to the responsible person or department
We are currently working on our Fluxygen video library, as soon as this is available, you will be able to find it in the Video section of our Resources.