Telemetry

Telemetry is a capability that is integrated into Broadcom’s SaaS and On-Premise products to transmit customer subscription usage and system configuration information to the Broadcom/CA Technologies data warehouse. We have found that leveraging information about how our customers use our products helps us understand how and why customers achieve success, or face challenges. Gathering and leveraging that data, in a secure and anonymized way, is essential to our ability to deliver relevant products that drive your success.
dts105
Telemetry is a capability that is integrated into Broadcom’s SaaS and On-Premise products to transmit customer subscription usage and system configuration information to the Broadcom/CA Technologies data warehouse. We have found that leveraging information about how our customers use our products helps us understand how and why customers achieve success, or face challenges. Gathering and leveraging that data, in a secure and anonymized way, is essential to our ability to deliver relevant products that drive your success.
Telemetry does not transmit any Personally Identifiable Information (PII). Broadcom/CA Technologies continues to follow the policy as outlined in our privacy statement: https://www.ca.com/us/legal/privacy.html
Telemetry is a foundational element of the new Enterprise Software Portfolio License Agreement (PLA) model.
Telemetry Data
The following metrics are read from the existing Enterprise Dashboard database and are collected for each hour.
A VSE is considered to have been in performance mode for a given hour if the VSE was in performance mode at any time during that hour.
Metric
Description
CAI Power User
The maximum number of concurrent CAI power users on each calendar day.
Functional Transactions
The number of functional VSE transactions, month-to-date. This number is collected over the month and then divided by 23,000 to obtain the number of transaction packs.
Performance VSE
The maximum number of concurrent performance VSEs on each calendar day.
SV Power User
The maximum number of concurrent SV power users on each calendar day.
TEST Power User
The maximum number of concurrent Test power users on each calendar day.
Configure Telemetry Options
Follow these steps:
  1. Browse to the Enterprise Dashboard.
    http://
    hostname
    :1506
  2. Click the gear icon and select
    Data Usage Setting
    .
    The Data Usage Setting dialog opens.
  3. Make the desired changes to the following fields:
    • Company Domain:
      Customer-provided string to identify the customer domain name, such as
      company.com
      . This is not a full email address.
    • Enterprise Site ID:
      Customer Enterprise Site ID that is used to access Support. A registered support user can get their Site ID from the Broadcom/CA Support Portal.
    • Internal Identifier:
      Customer-provided string to identify an internal group or charge area for the customer's internal use, such as billing back to groups.
  4. To use a proxy for your usage data, select
    Use a proxy to send usage data
    and enter a Proxy URI and the associated user name and password.
    • Port 443 is used by default for sending usage data. If that port is unavailable, enter a Proxy URI.
  5. Click
    Activate
    .
    Your selections are saved.
  6. Click
    Close
    .
To view your data usage within the product, see DevTest Solutions Usage Audit Report and Enterprise Dashboard Transaction Graph.
Report Telemetry Usage Manually
You can report Telemetry usage manually using these steps. You should only report usage manually if you are a PLA customer and there is a valid reason why you cannot configure Telemetry to automatically report usage.
You must report on the following metrics as part of Telemetry requirements for PLA customers:
  • CAI Power Users
  • SV Power Users
  • Test Power Users
  • SV Performance VSE
  • SV Functional VSE Transaction Counts
Follow these steps to download the required reports:
  1. Browse to the Enterprise Dashboard.
    http://hostname:1506
  2. Click on the gear icon and select
    Export Audit Usage Data
    .
  3. Select the To and From Dates so that the report covers the last 30 days, and click OK.
    The default file name is
    DevTestSolutionsUsageAuditReport.xlsx
    .
  4. Click
    Save
    .
    The report is downloaded to your Downloads folder.
  5. To download the report for the Functional Transactions metric, click the gear icon again, select
    Export Transactions Usage Data
    , and click OK.
    The default file name is
    DevTestTransactionsUsage.xlsx
    .
  6. Click
    Save
    .
    The report is downloaded to your Downloads folder.
Follow these steps to retrieve the required metrics:
  1. Open the DevTestSolutionsUsageAuditReport.xlsx file.
    The required metrics are on lines 10, 11, 12, and 15.
  2. Collect and copy the numeric values in the corresponding line in the report:
    • CAI Power Users: Line 10
    • SV Power Users: Line 11
    • Test Power Users: Line 12
    • SV Performance VSE: line 15
    The rest of this procedure describes how to derive the value of the final metric, functional transactions.
  3. Open
    DevTestTransactionsUsage.xlsx
    .
  4. Highlight Row #1.
  5. Select
    Sort and Filter
    ,
    Filter
    .
  6. Open the drop-down in the Type column and select only
    Number of Transactions
    (other entries should be unselected).
  7. Select Column C.
  8. Select
    Data
    ,
    Text to Columns
    .
  9. Click
    Next
    , click
    Next
    again, and select
    Date
    .
  10. Click
    Finish
    .
  11. Open the drop-down in Column C,  and select
    Date Filters
    ,
    Between
    .
  12. Select a date range for the last 30 days and click Ok.
    The data changes to reflect the selected time range.
  13. Select all of the data in Column D for the rows displayed for the past 30 days.
  14. Select
    AutoSum
    .
    The last entry below the final entry shows the functional transactions consumed over the last 30 days.
  15. Copy this numeric value and add it to your list of data to report to the Telemetry tool.