Licensing & Usage Reporting
To facilitate seamless product utilization, Capacity Private Cloud (formerly LumenVox) instances communicate with our central licensing service. This secure outbound connection typically occurs once daily and is strictly limited to license usage metrics; no user-identifiable information (PII) is ever transmitted.
Connectivity Requirements
To ensure uninterrupted service, clients must verify that their network and firewall configurations allow outbound traffic to our licensing endpoint:
- Endpoint: https://licensing.lumenvox.com
- Port: 443 (HTTPS)
Failure to allow this connection may result in licensing validation errors within your cluster.
Retrieving Usage Reports via API
Clients can programmatically audit their own resource consumption by querying the Reporting API. In a production environment, you will typically route these requests through your cluster's ingress controller.
The following example demonstrates how to request a usage report using grpcurl.
Note that for Capacity Private Cloud, you must provide the appropriate deployment, operator, and scope headers for security.
Example Request
Replace reporting-api.your-cluster-ingress.com with your specific cluster ingress URL:
grpcurl \
-H "x-deployment-id: d80b9d9b-086f-42f0-a728-d95f39dc2229" \
-H "x-operator-id: 00000000-0000-0000-0000-000000000001" \
-H "x-scopes: REPO" \
-d '{}' \
reporting-api.your-cluster-ingress.com:443 \
lumenvox.api.ReportingAPIService/UsageReportTip: If you provide an empty JSON payload {} as shown above, the API will return usage stats for all utilized components. You can also filter for specific components by defining them in the request body.
Understanding the Output
When you call the UsageReport method, the system returns a structured breakdown of your consumption metrics. Here is a typical example of the response you will receive:
component_data {
component: "SESSION",
usage_ms: 920,
usage_count: 1
}
component_data {
component: "TTS3",
usage_ms: 4382,
usage_count: 1
}
component_data {
component: "TTS3_ENUS",
usage_ms: 4382,
usage_count: 1
}
component_data {
component: "TTS3_ENUS",
usage_ms: 4382,
usage_count: 1
}
component_data {
component: "TTS3_ENUS_CHRIS",
usage_ms: 4382,
usage_count: 1
}
component_data {
component: "TTS3_ENUS_CHARS",
usage_ms: 42710,
usage_count: 62
}