Extracting Business Information from Service Usage Data Using Path Parameters

The following use case illustrates how to use the Business Metrics Policy to extract business information from service usage data from path parameters.

Managing Policies

Supported Platforms: 8.0 and later.

Configuration

  1. Launch the Envision Console, select New Dataset, and define a dataset with sharing set to Public.

    New Dataset

  2. In the new dataset, select New Dimension and define a dimension with the TEXT type.

    Defining a dimension

  3. In the same dataset, select New Metric and define a metric with the the COUNT type and all aggregations.

    Defining a metric

  4. Save aggregation settings for the selected dataset.

    Saving aggregation settings

  5. Select New Chart, and create a chart using this dataset with the following configuration:

    Creating a chart to use the Business Metrics dataset

    Creating a chart: defining business metrics

    Creating a chart: defining X and Y axes

  6. Select New Dashboard, and create a dashboard with the newly defined chart:

    Creating a dashboard

    Add Chart

    Adding the chart to the Dashboard

  7. Launch the Policy Manager Management Console, and create a service using the WADL file at this address: http://www.ebi.ac.uk/Tools/services/rest/censor?wadl (help for this service: http://www.ebi.ac.uk/Tools/webservices/services/so/censor_rest).
  8. Virtualize the service on the Network Director.
  9. Navigate to Policies > Operational and click Add Policy, then create a Business Metrics policy.
  10. Configure the policy, selecting the dataset you defined earlier, as shown below.

    Configuring the policy: dataset selection

  11. Provide Extract/Derive Configuration for each of the dimensions and metrics using the example illustrated below:
    • Dimension using Extract – To obtain a value in path parameters.

      Configuring the policy: defining the dimensions

    • Metric using Derive – To obtain usage count.

      Configuring the policy: defining the metrics

  12. Attach the policy to the service.

    Attaching the policy to the service

    Sending requests to the service

  13. Send multiple requests to generate data for various cases.

    Sending requests to the service

    Sending requests to the service

    Sending requests to the service

    Sending requests to the service

  14. Check the data to be recorded in MongoDB and Dataset. The data should be appropriate per the requests sent.
  15. The chart should record information based on the data generated in the datasets from the above requests.

Back to top