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

Using Event Metrics

Event Metrics feature provides a drilled down visualisation of metrics relating to CEP specific artifacts to carry out in-depth monitoring of throughput, latency, and memory usage of CEP. It is disabled by default to avoid the excessive processing of events and execution plan from causing a system overhead.

Prerequisites

Before you use event metrics, both JVM metrics and CEP component-specific metrics need to be enabled as follows.

  • To enable metrics for the CEP,  set the Enabled parameter under the Metrics element to true in the <CEP_HOME>/repository/conf/metrics.xml file. Alternatively, you can enable metrics at the time of starting the CEP server by using the following command:

    -Dmetrics.enabled=true

    For detailed instructions to enable/disable metrics and to configure metrics, see Enabling Metrics and Storage Types. 

  • To generate metrics related statistics, set the StatisticsReporterDisabled property to false in the <CEP_HOME>/repository/conf/carbon.xml file as shown below.

    <StatisticsReporterDisabled>true</StatisticsReporterDisabled>
  • To enable event metrics for specific event receivers, event publishers, and execution plans, enable statistics for the relevant components by clicking the Enable Statistics link. e.g., The following image shows how to enable statistics for an execution plan.
     

Monitoring event metrics

There are two methods to view event metrics:

Both methods generate the same metrics. The difference between the two methods is, when there are multiple tenants, the CEP Management Console allows you to view metrics for the currently logged tenant as well as other tenants wheres the JConsole only allows you to view metrics for the currently logged tenant.

Monitoring Metrics using the Management Console

Follow the procedure below to access event metrics via the Management Console.

  1. Log into the CEP Management Console. For detailed instructions, see Running the Product.
  2. In the Monitor tab, click Event Metrics. The View All Metrics page is displayed as shown in the example below.

    Alternatively, you can click Metrics to open the View All Metrics page.

    If you click Event Metrics, the View All Metrics page displays only event metrics. If you click Metrics, the View All Metrics page displays both JVM metrics and event metrics.


     Click on a link displayed under Sub Levels to view a specific metric as shown in the example below.
     

Monitoring Metrics using the JConsole

Follow the procedure below to monitor event metrics via the JConsole.

  1. Start the WSO2 CEP server.
  2. Start the JConsole. For detailed instructions to start the JConsole to monitor the CEP, see JMX-Based Monitoring.
  3. Click the MBeans tab in the JConsole window. Then expand the org.wso2.carbon.metrics domain.

  4. Click on the relevant MBeans under the org.wso2.carbon.metrics domain to view the required metrics. 
com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.