Correlate a Boomi Process to the System resource consumption.

Hello Boomi fans!

For years I have been wondering how to easily correlate a Boomi Process to the System resource consumption.

Or, in other words, calculate the operational cost for a Boomi Process.

For example, let’s say you are monitoring your Boomi runtime, you observe a load pattern and you also observe a spike in the number of executions in a short time frame:

Which Boomi Process executed 13 K times and consumed 70% of the CPU? Who “ate my pudding”?

And finally, I have the answer: Boomi Processes aggregation by Execution Count, Duration, Data Size and so on, correlated with the resource consumption:

Now we know that we need 70% of our CPU for 20 minutes to process 6.5 K Suppliers.

We can even zoom in on a particular distribution, all the way down to the execution ID that “ate my pudding”.

This is how we found the inefficient process designs that drained our resources.

We are now able to fit more and more executions on the same runtime increasing our ROI by leveraging our existing infrastructure investments.

With the rise of AI, the demand for integration is exploding.

If you want to get the most out of your existing Boomi investment, give us a call.

You can find out more details about our Boomi Monitoring Solution from our dedicated Boomi page.