...
Introduction
The Stream audit view data is available once the stream processing is complete. In the case of an unbounded stream, you need to stop the stream to view the metrics.
...
Unbounded Stream Explanation
...
, and you can view it in the Stream audit tab in the Audit page. If you have an unbounded stream, which is a stream with a running HTTP server that keeps on processing or waiting for new requests
...
until manually stopped, you need to stop the stream to view the metrics.
This type of audit data is not available unavailable if the target stream has failed running to run or it has been aborted.
Stream Audit Overview
...
You can access the stream audit from the Solutions panel. On the Actions dropdown menu choose the Audit Function. This will open the main Audit screen. Navigate to the Stream Audit area by clicking on that tab on the upper part of the screen.
You can also access the Stream audit by clicking on the Audit button from the Stream Editor.
The following details of a stream record are available:
...
Column Name
...
Description
...
To open the Stream audit tab, you can either click on the More menu in the Action column in the Stream tab, and select Audit and then click the Stream audit tab, or you can open the stream in the Stream editor, click on the View audit button, and then click on the Stream audit tab.
...
The stream audit information is displayed in a table with the following columns:
Column | Description |
|---|---|
Start time | Date and timestamp when the first transaction in a stream is started. |
End time | Date and timestamp when the last transaction operation has ended. |
Total input | The total number of events processed by the collector Functions in the stream. |
Total output | The total number of events processed by the forwarder Functions in the stream. |
Processing time | The total processing time of the stream. |
The total time, that which is the time between Start time and End time, is will always be slightly higher than the Processing time.
The reason for this is as follows:
...
The start time is when the first transaction starts.
...
since there is a short gap in time between each transaction, and the total time considers this gap.
The
...
Processing time is
...
the
...
The Processing time is the data processing time itself time it took to process the data and is also used for calculating the transactions per second (tps) metric.
Click on the plus sign in front of a stream record to view more details.
...
In the following Function-wise detailstable displayed you can see the following information:
Column |
|---|
Description | |
|---|---|
Function |
name | Name of the Function |
Function |
type | Type of the Function |
Inputs | Total number of incoming events processed by the Function |
Outputs | Total number of outgoing events processed by the Function |
TPS | The number of transactions handled per second |
...
. |
...
Operator Name
Description
=
Searches for values that are equal to the entered query
>=
Searches for values that are greater than or equal to the entered query
<=
Searches for values that are less or than or equal to the entered query
>
Searches for values that are greater than the entered query
>
~
Searches for values that have an approximate value to the entered query
Note!
The |
...
TPS value Calculation:
...
TPS |
...
is calculated as: TPS value for a Function = (Total number of output events handled by the Function) / (duration of the stream) |
It may take a few seconds for the metrics to load in the metrics view. Click Refresh or go back to the metrics page after some time.
The metrics are stored for 180 30 days.