com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links' is unknown.

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 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 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

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.

 You also can give any Lucene queries to further filter the results from the time range you have given above. You can add any number of nested queries, which spans over any number of tables. Below given is the sample query that you can search.

You will get the list of activity ids as below, and when you click on each you will see a first 10 records for the activities. If you want, you can click on view more.

Then you can click on any record that you like to view to see the full record content.


com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.