usage_metering Billing Reports

The Usage Metering (usage_metering) probe generates the following types of billing reports:
uimpga-ga
The Usage Metering (usage_metering) probe generates the following types of billing reports:
  • Overall Billing Summary Report
  • Origin-specific Billing Summary Report for each hub
This article describes the concepts, calculations, and considerations for the billing reports. You can export HTML billable items report after the usage calculation completes. You can then open the report in any Web browser or spreadsheet application for advanced features such as filters and pivot tables, as required. CA Sales Operations require you to generate and send your billing reports each month.
 From usage_metering version 9.01, you can use the webgtw probe to automatically upload the overall summary report to CA support. For more information, see Set Up Automated Usage Metering and Billing.
 
Contents
 
 
 
2
 
 
Billing Report Concepts
Billing Report Considerations
A billable unit in the report is the billable count of the resource..
Consider the following before you generate a report:
  • If the billable units change within a month, the report uses the largest value. For example, if you are monitoring 2 TB using a storage pack probe for 15 days, and 3 TB for the remaining days of the month, the probe calculates the billable units as 3 TB for the whole month.
  • If you remove a billable component from a monitored resource, the report still includes the value for the month. For example, if you remove a disk or volume from your storage server, the probe includes the capacity as billable unit for the whole month.
  • If you rename a hub, the report includes the billable units for both the old and new hub names for the month. For example, if you rename a secondary hub from 
    hub20
     to 
    hub21
    , the report includes the billable units information for both the hubs.
  • If you have no billable items in a month, the probe does not generate reports for that month. You can verify the information from the probe logs.
  • From usage_metering version 9.01, the report does not include probes from the 
    CA NM - Base Infrastructure Pack
    .
You can monitor your environment with CA UIM using one of the following ways:
One Probe to One Device
If you use CA UIM to monitor one device using a single probe, the billing report identifies the monitored device as one billable unit. The following table displays a sample 
Billing Items Detailed Information
 section from an overall summary report with One to One monitoring:
Billing ID
Billing ID Count
CS_ID
Name
Billing Pack Name
Probe Name
Origin
IP
FQDN
Robot
Count Pct
Total Size (TB)
1
1
7
Dodge_Charger
CA NM - Ping Pack
net_connect
myOtherHub
10.112.79.145
doc-team03
Camaro_robot
1
Multiple Probes to One Device
You can monitor a single device using multiple probes in CA UIM and each probe is part of a pack. For more information about probe packs, see usage_metering and CA UIM Probe Packs. The following table displays a sample Billing Items Detailed Information section from an overall summary report with Many to One monitoring:
Billing ID
Billing ID Count
CS_ID
Name
Billing Pack Name
Probe Name
Origin
IP
FQDN
Robot
Count Pct
Total Size (TB)
1
1
3
AstonMartinDB9
CA NM - Server Pack
cdm
myPrimaryHub
10.112.74.209
doc-team02
AstonMartinDB9
0.5
2
1
3
AstonMartinDB9
CA NM - Server Pack
net_connect
myPrimaryHub
10.112.74.209
doc-team03
Camaro_robot
0.5
 
 
4
 
 
Billing Calculation Rules
The following rules apply in the specified order to calculate the billable units in the report. The accompanying example uses a combination of cdm and net_connect probes.
  1. The usage_metering probe includes the pack with the first occurrence of each probe in a hub.
    Probe
    Pack ID
    Pack Name
    cdm
    20
    CA NM - Server Pack
    net_connect
    15
    CA NM - Ping Pack
  2. The usage_metering probe verifies the probe in the minimum rank pack against the other probes for the next higher applicable rank.
    Probe
    Pack ID
    Pack Name
    net_connect
    15
    CA NM - Ping Pack
  3. If other probes exist in pack with the probe from 
    Step 2
    , the usage_metering probe chooses the other pack.
    Probe
    Pack ID
    Pack Name
    cdm
    20
    CA NM - Server Pack
    net_connect
    20
    CA NM - Server Pack
  4. Repeat 
    Steps 2
     and 
    3
    , as applicable.
  5. The usage_metering probe applies the following formula to calculate the weighted billable units:
    1 / Number of probes monitoring the server in the pack
  6.  
    (Optional)
     If there are probes from more than one pack, the usage_metering probe applies 
    Step 5
     for each pack.
Billing Calculation Sample: net_connect, cdm, and aws
  1. The usage_metering probe includes the pack with the first occurrence of each probe in a hub.
    Probe
    Pack ID
    Pack Name
    cdm
    20
    CA NM - Server Pack
    net_connect
    15
    CA NM - Ping Pack
    aws
    30
    CA NM - Server and Application Pack
  2. The usage_metering probe verifies the probe in the minimum rank pack against the other probes for the next higher applicable rank.
    Probe
    Pack ID
    Pack Name
    net_connect
    15
    CA NM - Ping Pack
  3. If other probes exist in pack with the probe from 
    Step 2
    , the usage_metering probe chooses the other pack.
    Probe
    Pack ID
    Pack Name
    cdm
    20
    CA NM - Server Pack
    net_connect
    20
    CA NM - Server Pack
    aws
    30
    CA NM - Server and Application Pack
  4. Repeat 
    Step 3
    .
    Probe
    Pack ID
    Pack Name
    cdm
    30
    CA NM - Server and Application Pack
    net_connect
    30
    CA NM - Server and Application Pack
    aws
    30
    CA NM - Server and Application Pack
  5. The usage_metering probe applies the following formula to calculate the weighted billable units:
    1 / 3
The probe calculates the billable units as 0.33 for each probe.
Billing Calculation Sample: net_connect, cdm, and dns_response
  1. The usage_metering probe includes the pack with the first occurrence of each probe in a hub.
    Probe
    Pack ID
    Pack Name
    cdm
    20
    CA NM - Server Pack
    net_connect
    15
    CA NM - Ping Pack
    dns_response
    70
    CA NM - Service Response Time Adv Pack
  2. The usage_metering probe verifies the probe in the minimum rank pack against the other probes for the next higher applicable rank.
    Probe
    Pack ID
    Pack Name
    net_connect
    15
    CA NM - Ping Pack
  3. If other probes exist in pack with the probe from 
    Step 2
    , the usage_metering probe chooses the other pack.
    Probe
    Pack ID
    Pack Name
    cdm
    20
    CA NM - Server Pack
    net_connect
    20
    CA NM - Server Pack
    dns_response
    70
    CA NM - Service Response Time Adv Pack
  4. The usage_metering probe applies the following formula to calculate the weighted billable units:
    net_connect and cdm: 1 / 2
    dns_response: 1 / 1
The probe calculates the billable units as 0.50 for net_connect and cdm and as 1.00 for aws.
Billing Calculation Sample: net_connect, cdm, and cisco_nxos
  1. The usage_metering probe includes the pack with the first occurrence of each probe in a hub.
    Probe
    Pack ID
    Pack Name
    cdm
    20
    CA NM - Server Pack
    net_connect
    15
    CA NM - Ping Pack
    cisco_nxos
    40
    CA NM - Network Adv Pack
  2. The usage_metering probe verifies the probe in the minimum rank pack against the other probes for the next higher applicable rank.
    Probe
    Pack ID
    Pack Name
    net_connect
    15
    CA NM - Ping Pack
  3. If other probes exist in pack with the probe from 
    Step 2
    , the usage_metering probe chooses the other pack.
    Probe
    Pack ID
    Pack Name
    cdm
    20
    CA NM - Server Pack
    net_connect
    20
    CA NM - Server Pack
    cisco_nxos
    40
    CA NM - Network Adv Pack
  4. The usage_metering probe applies the following formula to calculate the weighted billable units:
    cdm and net_connect: 1 / 2
    cisco_nxos: 1 / 1
The probe calculates the billable units as 1.00 for cdm and 0.50 for net_connect and cisco_nxos.
Billing Report Structure
The billing reports include the following sections:
Report Details
Each billing report includes the following report details:
  •  
    Report Name:
     indicates the name of the report. The rules for the name are as follows:
    • Overall Billing Summary Report: The name of the report is 
      Summary Report
      .
    • Origin-specific Billing Summary Report: The format for the report name is as follows:
      Origin
      Hub_name
      Summary Report
  •  
    Time Zone:
     indicates the time zone of your CA UIM primary hub. For example, Asia/Calcutta, India Standard Time
  •  
    Create Time:
     indicates the time when the report was created in the following format:
    YYYY-MM-DD HH:MM SS
    For example, 2017-07-20 12:30 18
  •  
    Usage Metering Data Start Time:
     indicates the start time of the billing report. The report starts from the first day of the month. For example, 2017-07-01 00:00:00 for the month of July 2017
  •  
    Usage Metering Data End Time: 
    indicates the end time of the billing report. The report ends on the last day of the month. For example, 2017-07-31 23:59:59 for the month of July 2017
  •  
    Pack Type:
     indicates from the following types of packs that are used for the billing report. For more information, see usage_metering and CA UIM Probe Packs.
    • Default: indicates that the billing report uses the default probe packs.
    • Custom: indicates that the billing report uses the custom probe packs.
Overall Billing Packs Summary
The Overall Billing Packs Summary section includes pack-specific billable unit information for all probes in your CA UIM environment. For more information about packs, see usage_metering and CA UIM Probe Packs. The section includes the following details:
  •  
    Pack Name:
     indicates the name of the probe pack.
  •  
    Total Unit Count:
     indicates the number of billable units in the applicable pack.
  •  
    Referenced Probes:
     indicates the names of the probes with billable units.
  •  
    Notes:
     indicates additional information for any pack. For example, for Base Infrastructure Pack, the Notes indicate that the
     
    device count is not included in the total.
  •  
    All Packs Unit Count:
     indicates the total billable unit count for all the packs in the report, except the Base Infrastructure Pack.
The following table displays a sample 
Overall Billing Packs Summary
 section from a report:
Pack Name
Total Unit Count
Referenced Probes
Notes
CA NM - Ping Pack
3
net_connect
CA NM - Storage Pack
65.54
netapp_ontap, ibm-ds, hp_3par
CA NM - Server Pack
1
net_connect, cdm
 
ALL PACKS UNIT COUNT
 
 
69.54
 
Origin Billing Packs Summary
The Origin Billing Packs Summary section includes pack-specific billable unit information for probes of each hub in your CA UIM environment. For more information about packs, see usage_metering and CA UIM Probe Packs. The section lists the origins in alphabetical order and includes the following details:
 In origin-specific billing reports, the Overall Billing Packs Summary section and the Origin Billing Packs Summary section display the same information.
  •  
    Origin Name: 
    indicates the name of the origin (CA UIM hub).
  •  
    Pack Name:
     indicates the name of the probe pack.
  •  
    Total Unit Count:
     indicates the number of billable units in the applicable pack.
  •  
    Referenced Probes:
     indicates the names of the probes with billable units.
  •  
    Notes:
     indicates additional information for any pack.
  •  
    Total Origin Unit Count:
     indicates the origin-specific total billable unit count for all the packs in the report, except the Base Infrastructure Pack.
The following table displays a sample 
Origin Billing Packs Summary
 section from an overall summary report:
Origin Name
Pack Name
Referenced Probes
Total Unit Count
Notes
myOtherHub
CA NM - Ping Pack
net_connect
1
 
myOtherHub
 
 
TOTAL ORIGIN UNIT COUNT
 
 
 
 
 
1
 
myPrimaryHub
CA NM - Ping Pack
net_connect
2
myPrimaryHub
CA NM - Storage Pack
netapp_ontap, ibm-ds, hp_3par
65.54
myPrimaryHub
CA NM - Server Pack
net_connect, cdm
1
 
myPrimaryHub
 
 
TOTAL ORIGIN UNIT COUNT
 
 
 
 
 
68.54
 
Device Collection Information
The Device Collection Information section displays the origin-specific device information that the report includes. The section lists the origins in alphabetical order and includes the following details:
  •  
    CS_ID:
     indicates the unique computer system ID of your device as stored in the CA UIM database.
  •  
    Origin:
     indicates the name of the origin (CA UIM hub).
  •  
    IP:
     indicates the network IP address of the device.
  •  
    FQDN:
     indicates the Fully Qualified Domain Name of the device.
The following table displays a sample 
Device Collection Information
 section from an overall summary report:
CS_ID
Origin
IP
FQDN
7
myOtherHub
10.112.79.145
doc-team03
18
myPrimaryHub
10.5.48.56
19
myPrimaryHub
10.130.10.40
16
myPrimaryHub
10.112.69.69
ds-7071bc8fe599
3
myPrimaryHub
10.112.74.209
doc-team02
13
myPrimaryHub
10.112.73.202
1
myPrimaryHub
10.112.78.75
22
myPrimaryHub
10.112.77.240
Billing Items Detailed Information
The Billing Items Detailed Information section displays the detailed billable unit information for each instance of each probe in the report. The section lists the origins in alphabetical order and includes the following details:
  •  
    Billing ID: 
    indicates the serial number of the record in the report.
  •  
    Billing ID Count
    : indicates the count of the billing record and is based on the device. For example, you can monitor two arrays of an IBM DS storage server from one robot, and three more arrays from another robot. Both records in the report have the same value for this column.
  •  
    CS_ID:
     indicates the unique computer system ID of your device as stored in the CA UIM database.
  •  
    Name:
     indicates the unique computer system name of your device as stored in the CA UIM database.
  •  
    Billing Pack Name:
     indicates the name of the probe pack. For more information about packs, see usage_metering and CA UIM Probe Packs
  •  
    Probe Name:
     indicates the name of the probe with the billable units.
  •  
    Origin:
     indicates the name of the origin (CA UIM hub).
  •  
    IP:
     indicates the network IP address of the device.
  •  
    FQDN:
     indicates the Fully Qualified Domain Name of the device.
  •  
    Robot:
     indicates the name of the CA UIM robot with the probe.
  •  
    Count Pct:
     indicates the weighted count of the billable units.
  •  
    (Storage Pack Probes only) Total Size (TB):
     indicates the total monitored size of the storage server.
The following table displays a sample 
Billing Items Detailed Information
 section from an overall summary report:
Billing ID
Billing ID Count
CS_ID
Name
Billing Pack Name
Probe Name
Origin
IP
FQDN
Robot
Count Pct
Total Size (TB)
1
1
7
myOtherHubRobot
CA NM - Ping Pack
net_connect
myOtherHub
10.112.79.145
doc-team03
Camaro_robot
1
2
2
18
10.5.48.56
CA NM - Storage Pack
ibm-ds
myPrimaryHub
10.5.48.56
Camaro_robot
7.03
2
2
18
10.5.48.56
CA NM - Storage Pack
ibm-ds
myPrimaryHub
10.5.48.56
Corvette_StingRay
53.49
3
1
19
10.130.10.40
CA NM - Storage Pack
hp_3par
myPrimaryHub
10.130.10.40
Camaro_robot
0.02
4
1
16
ds-7071bc8fe599
CA NM - Ping Pack
net_connect
myPrimaryHub
10.112.69.69
ds-7071bc8fe599
Camaro_robot
1
5
2
3
AstonMartinDB9
CA NM - Server Pack
cdm
myPrimaryHub
10.112.74.209
doc-team02
AstonMartinDB9
0.5
5
2
3
AstonMartinDB9
CA NM - Server Pack
net_connect
myPrimaryHub
10.112.74.209
doc-team02
Camaro_robot
0.5
6
1
1
myPrimaryHubRobot
CA NM - Ping Pack
net_connect
myPrimaryHub
10.112.78.75
Camaro_robot
1
7
1
22
10.112.77.240
CA NM - Storage Pack
netapp_ontap
myPrimaryHub
10.112.77.240
Camaro_robot
5.00