4.3 Using System Insight for Batch Workflows
- Jenni Wallin
- Former user (Deleted)
Note!
This section only applies if you are using System Insight with InfluxDB for data storage.
In batch workflows, metrics are not published to InfluxDB after every batch. An aggregation task which runs every 10 seconds aggregates all the batch results generated up to that point and sends them to InfluxDB.
Only metrics which are a Number are aggregated. Creating metrics from MIMs that are instances of a String, timestamp etc is not applicable, and these are not aggregated nor sent to InfluxDB.
For workflow MIM parameters, we aggregate only batch_duration.
This means that individual batches cannot be tracked using System Insight. If you require to track individual batches, use Audit: see 8.3 Audit Profile. System Insight provides aggregate metrics only.
Throughput for Batch Workflows
If you want to display the throughput of a batch workflow using System Insight, you can determine the throughput depending on what data you require and on your workflow.
Example of how you can determine throughput for a batch workflow
If you have the workflow shown below, you choose how you want to determine the throughput data, which you want to display using System Insight.
Example batch workflow
If you want the throughput to be determined by the number of UDRs decoded within the batch duration period, you can use the Outbound UDRs MIM parameter as a metric and divide it by the batch_duration to get the throughput in UDRs per second. In this example the metric name is mim.batch.processing.decoder.outbound_udrs.
If you want the throughput to be determined by the number of bytes encoded within the batch duration period, you can use the Outbound Bytes MIM parameter as a metric and divide it by the batch_duration to get the throughput in bytes per second. In this example the metric name is mim.batch.processing.encoder.outbound_bytes.
Example MIM Browser