Introduction
This metric is now available with the 26.04 release. It gives insight into the OIC Async Queue for your OIC instance.
Async integrations are fire and forget. In my example, the client is SOAP UI and it sends requests to invoke the OIC integration, async create order.
In my simple demo, this async integration invokes a sync integration, which waits for 60 secs, before returning a response. This will ensure a build up of the async queue. My OIC instance has 1 message packs assigned to it, therefore the async concurrency limit is set to 50.
Before starting the SOAP UI load test, let's check out the Observability page, -
I start the test 1000 invokes of the async integration.
Back in OIC Observability and we see the queue building up -
Note 73 invokes of the sync integration, i.e. the concurrent async limit is not 100% strictly enforced.
1000 - 129 = 871
Note: this service metric should be viewed with the following filters applied -
- Interval - 1m
- Statistic - Sum
Alerts based on this Metric
The threshold you will use is dependent on your business use case. For demo purposes, I will create an alert to notify me if the queue is over 500. Click Edit queries -
I run the SOAP UI test again and return to the Alarms page in the OCI console -
Back in OCI - the threshold has been breached -
Again, the 500 threshold was just an arbitrary limit I selected, as it fitted nicely to my test run of 1000 flows.
Summa Summarum
This new metric is very useful for monitoring throughput and performance. Remember, OIC will never refuse an async request, it will just be queued for future processing. How quickly that will happen depends on the complexity of the integration etc. as well as the concurrent async processing limit, applicable to your OIC instance. Naturally, the latter can be increased, by adding more message packs.

No comments:
Post a Comment