Metering

​

Terminology

​

Create a Metric

1. Identify the Metric: From your customer order, determine the metric you want to bill for (e.g., Monthly Active Users, GB Used, Emails Sent).
2. Navigate to Meter Creation: Go to Metering > Meters > Create meter.
3. Enter Meter Name: Provide a name for your meter for easy identification.
4. Select Metric: Choose the metric identifier (e.g., test_meter) that matches the events you are tracking.
5. Set Filters (Optional):
   • Filters allow you to include only specific events in your meter calculation.
   • You can filter on event metadata fields (e.g., browser type, region, etc.).
   • Filters can be simple or complex, using logical operators (and, or) and conditions.
   • Example:
     • To count only Chrome browser events:
       Copy

       {
         "logic": "and",
         "conditions": [
           { "field": "browser", "operator": "eq", "value": "Chrome" }
         ]
       }
       

     • To count Chrome or Firefox events:
       Copy

       {
         "logic": "and",
         "conditions": [
           {
             "logic": "or",
             "conditions": [
               { "field": "browser", "operator": "eq", "value": "Chrome" },
               { "field": "browser", "operator": "eq", "value": "Firefox" }
             ]
           }
         ]
       }
       

   • Leave filters empty to include all events for the metric.
6. Choose Aggregation Method: Select how to aggregate the events (e.g., sum, count, max, min).
   • Example: Use sum to total up usage values, or count to count the number of events.
7. Set Window: Choose the time window for aggregation (daily or monthly).
8. Set Status: Choose the status for the meter (e.g., active/inactive).
9. Set Start and End Dates:
   • Start Date: The date from which to start logging the metric.
   • End Date: The date until which to log the metric (leave blank if ongoing).

​

Create a new Event Configuration

1. This is where you tell Enso to process your raw event log into a metric
2. Have a sample Event Log (csv) file ready with you which has the same columns as the periodic log file that you will be uploading
3. Go to Metering>Events>Import Event>upload CSV

create a new event configuration

5. Click on “Create a new configuration”
6. Give a name for your configuration
7. Headers is the main section of your Event Log processing
8. Headers>Metric: This is the Metric identifier which you entered while creating the Metric. See “Create a Metric” above. Select the column header which has this data in the Event Log file.
9. Headers>Customer: is the identifier for your customer. Select the column header which has this data in the Event Log file. The identifier for your Customer can be set up in Settings>Customers>Select Customer>Click on an enity>Create attribute> (under value add the identifier from your Event Log). Example, a number which is how your customer is identified in your product database, an alias for your customer from your CRM etc.
10. Headers>Timestamp: is the date/time column in your Event Log file. This helps Enso relate the event log data to a certain day or month corresponding to your billing.
11. Headers>Value: is the most important feature. This is where you assign a value against each event log in your Event File. This maybe expressed as a formula or if a value is already available picked up from the column header. configure an event

12. Using Formula: you use a Formula instead of a column header in cases where the event log file needs to be processed for you to arrive at a value for each log. For example in the below case I need to count the number of “Log_in” under the column “Acitivty”. In an excel I would add a column next to it with this formula =IF(F2=“Log_in”,1,0) Enso supports a wide range of excel formula. Since we are using Column headers and not specific cell, we replace the cell reference (F2) with the Column Header reference (Activty). The above formula in Enso will be represented as IF(Activity=“Log_in”,1,0) Note:
    • the column headers are represented within double paratheses {{column header name}}
    • don’t add an ”=” in front of the formula

13. Attributes: these are additional data that you want to capture from the Event Log CSV for you to check the data later, use it for reports etc. “Key” is the name you want ot give this column header and go ahead and select a column from your Event Log or compute a formula for this. Adding Attributes is optional and it does not have any impact on your metric.
14. Unique Identifiers: in case your event log file has duplicates of the same line item (say log #) then use this to exclude such duplicates. This is required only if you want to weed out duplicates. It is not a mandatory field.