Introduction
Here is a simple example, from which you can extrapolate - the basis is the following Project and it's integrations -
validateOrder is only invoked via local invoke by the integrations - processOrderSync and processOrderAsync.ProcessLargeOrderListSync - processes a file of 80KB.
Hourly Orders Run is a scheduled job that does essentially nothing, except WAIT for 10 seconds.
Let's run these integrations -
Now to OCI Dashboards - As you can see, I have 2 widgets - OIC Integration Technical Message Count by Integration and Billable Messages by IntegrationThe former shows the number of "technical" messages / requests OIC received, while the latter shows the resulting billable messages. Both widgets are grouped by integration.
So why are there differences between the two? Let's investigate -
The scheduled integration - Hourly_Orders_Run executed twice. However, all this flow does is WAIT for 10 seconds. It does not contain any invokes that retrieve data. If it did, only data > 50KB is counted, from a billing perspective. Ergo, no billable messages for this integration.ProcessOrder ran 5 times and generated 5 billable messages.
ProcessOrderAsync ran 3 times and generated 3 billable messages.
The integration, ValidateOrder, ran 8 times, but all of these were via local invoke from ProcessOrder and ProcessOrderAsync. Ergo, these are not billed.
Behind each widget lies a query, based on OCI service metrics.
For the "Technical" messages widget -
For the "Billable" messages widget -
This Dashboard was created in OCI Log Analytics and includes the following filters -
So how did I add the filters? I simply duplicated one of the OOTB Integration dashboards, delivered with OCI Log Analytics -The OOTB dashboards are those created by Oracle -Open the Health Overview dashboard -
Click on the Actions dropdown and select Duplicate - Give it a name -Open the Dashboard - Click Edit and delete all the existing widgets in the dashboard -All gone! - Now create a new query based widget - Action - Edit - Copy and paste the "technical" query - Note the $(params.oic-env)} - this is the link to the OIC resource id in the filter. We need to add this parameter to this widget - The default Visualisation is Table, let's change this - Amend as follows - This results in -Do the same for the "Billing" widget.A very nice feature is the ability to export to CSV -
Policies Required

No comments:
Post a Comment