What if my message flows use custom logging to databases/files?
Keep existing logging during transition (belt-and-suspenders approach). Enable IBM Monitoring Profiles for 20 flows (pilot), verify Nodinite captures expected data, then disable custom logging incrementally. Migration timeline: 200 flows typically complete in 3-6 months (20 flows/month pace).
Long-term: Remove custom ESQL logging code (MQOutput nodes, File nodes, database CALL statements) after Nodinite proven. Simplifies message flows, reduces maintenance, eliminates per-flow logging logic variations.
Related Questions
See all FAQs: [Troubleshooting Overview][]