The activity monitoring dashboard is used to get the list of the events belongs to an activity and search through it its results by providing an a valid Lucene query.
Let’s consider an For example, when a transaction is being processed and going through several subsystems and if you want to find out the status of the particular transaction such as whether it has completed or at which sub system currently it’s being processed, etc can be filtered by sending the events to our WSO2 DAS with same activity ID, and then you can search through the events collected from different sub systemsis passing through many sub systems, 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 which belongs that belong to the same activity id, ID and provide provides you the a list of activity ids, and then you can drill down the activity id to see what are the actual events that has fired and then take your decisions based on the analysis.Below sample use case takes you over the capabilities of 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.
| Table of Contents | ||
|---|---|---|
|
Enabling the stream for activity monitoring
If you want to use activity dashboard to search your events, then you need to define the activityId field as the ‘FACET’ field and enable the indexing for that field as given below.
...
Also you can search the activity by field, and if you want to search by any particular fields other than timestamp, then you also need to index them appropriately. In below provided example the user is required to search by meta_host, meta_http_method, meta_message_type, and operation_name. Therefore the user have to enable indexes to those fields.
Publish events with the activity ID
As we have mentioned above, the event needs to have mandatory ‘activityId’ field in the correlation data of the event and the field needs to be as JSON string to use it as FACET type. Therefore convert your activityId as JSON string and publish to WSO2 DAS. For example, sample JSON formed activity shown below.
[ 1cecbb16-6b89-46f3-bd2f-fd9f7ac447b6 ]
Using the activity monitoring dashboard
If you want to perform the search within any time period, then select the data and time for ‘From time’ and ‘To time’ respectively. If you don’t select any time duration for the field, then it will search through the full time range. But it’s advisable to use this time range, if you have events collected and hence searching through the entire list of events will have some processing/memory needs.
...