Activity Explorer

The activity monitoring dashboard is used to get the list of the events belongs to an activity and search through its results by providing a valid Lucene query.

For example, when a transaction being processed is passing through many subsystems, you can search through events collected from different subsystems to check whether the transaction is completed, the subsystem at which it is currently being processed etc. The filtering is done by sending events to WSO2 DAS with the same activity ID.

The activity monitoring dashboard groups all the events that belong to the same activity ID and provides you a list of activity IDs. This allows you to search for events by the activity ID and make decisions based on that analysis. 

The following sample demonstrates the capabilities of the activity monitoring dashboard.

Enabling the stream for activity monitoring

In order to use the activity dashboard to search for events, the activity_id attribute needs to be included in the relevant event stream, and it should be persisted as a facet as shown below.

In the example given above, the Index Column check box is also selected for the activity_id attribute in order to make it possible to search by this attribute. If there are other attributes by which you want to search, they too need to be persisted as index columns. In this example, it is required to search by the meta_host, meta_http_method, meta_message_type, and operation_name attributes, and therefore, the Index Column check box is selected for them.

For more information, see Persisting Data for Interactive Analytics.

Publish events with the activity ID

As mentioned above, the event stream has the activity_id attribute. Each event set to the stream should have a value for this attribute in JSON string. The following is a sample JSON formed activity.
[  1cecbb16-6b89-46f3-bd2f-fd9f7ac447b6 ]  

Using the activity monitoring dashboard

If you want to perform the search within any time period, select the start time and end time as required in the From Time and To Time fields. If a time interval is not specified, the search is carried out in all the available records. Therefore, it is recommended to specify a time interval to reduce the system overhead.

 You also can enter Lucene queries to further filter the results for the time range pacified. You can add any number of nested queries that span over multiple tables. A sample query by which you can search is given below. 

This fetches a list of activity IDs as shown below. When you click on an activity ID, the first 10 records for that activity are displayed. You can click More to view more records for the activity.

Then you can click on each record to view the full record content.