Introduction
This feature has been available for some time now; it's availability doesn't jump out in your face, so let's look at it in some detail.
View Slowest Activities
This feature is available in instance tracking. The goal here is to give you insight into where most of the flow execution time is being spent in respect of the actions you have defined in your integration.
Just to make sure there is no ambiguity, we can look at the execution time as being divided into 2 areas -
- The time taken to execute the actions you have defined within your integration. In the following case that would be - Map(writeFile), File server(writeFile) and Map(saveFile). The trigger is an exception here. Let's classify this as infrastructure.
- infrastructure - triggers, transitions between actions etc.
As you see above, the integration has been run with the trace level set to debug. Let's check out the slowest activities.
Here we see that writing the file to OIC File Server, via the file server native action, consumed almost half the execution time.
I run the same integration again, this time with trace set to audit -
As you can see, the Map actions are not included.
Production level trace is the same -
Summa Summarum
This feature is extremely useful, especially in the development phase, where you are testing in debug mode. It is also very useful in production, for seeing where processing time is being spent, in respect of invokes. You can always flip between production / debug tracing to get more data -
If you need data over a longer time period, then look at OCI Service Metrics, e.g. Outbound Request Invocation Time. Here you can investigate the time taken by your invokes over whatever period of time you want. You also get the rich variety of stats -
