View IaaS billing metered usage processing status
Infrastructure as a Service (IaaS) products include Google Cloud Platform (GCP), Azure, and Amazon Web Services pay-as-you-go (AWS).
After AppDirect submits metered usage for IaaS products, Marketplace Managers, and Developers who belong to a Developer company that owns IaaS products, can check the user interface to see whether the usage was processed successfully.
The Metered usage page displays processing status for usage submitted as follows:
- by AppDirect for IaaS products
- by Developers with the Metered usage V2 API
Note: Only AppDirect can enable the Metered usage page. To request it, contact your AppDirect technical representative.
As metered usage requests and events are processed, they appear on In processing, Failed, and Successful tabs on the Metered usage listing and detail pages. The tabs only appear if there are events to display on them.
Typically, AppDirect submits metered usage data at the end of each billing period. Key metered usage terms include the following:
- Usage events—individual metered usage records
- Requests—groups of one or more usage events
- Runs—performed by AppDirect to submit one or more requests to marketplaces
How to check the status of metered usage processing, and descriptions of the information that appears, follows.
To check IaaS metered usage processing status and errors
- Go to Manage > Billing and Distribution > Metered usage. The Metered usage page opens. It displays a list of usage runs (which are groups of usage requests) and a summary of each one. For definitions of the information that appears on this page, see the Request (run) summary information link later in this topic.
- Click a row to select a run. The request details page opens and displays a list of all the requests included in the run. Successful, and sometimes Failed and In Progress, tabs display the requests in the run (for definitions of the information that appears on this page, see the Request details link later in this topic).
- To view requests currently being processed, click In Progress.
- To view requests that failed, click Failed.
- To view the events that caused a request to fail and the associated errors, click a request row. System errors and Data errors tabs display failed events (for definitions of the information that appears in this view, see the Failed event errors link later in this topic).
Tip: There is a Reprocess System Errors button in this view. Do not attempt to reprocess system errors. AppDirect manages IaaS usage processing errors.
IaaS metered usage processing status information that appears in the UI
The Metered usage page displays a list of usage runs (which are groups of usage requests) and a summary of each one.
Request (run) summary
Request (run) details |
---|
Request (run) status |
Completion date |
The request details page displays a list of all requests in the run.
Request (run) details
Request (run) summary pane | |
---|---|
Name of IaaS product for which usage was submitted | |
Request (run) identifier, appended with the date and time of the last attempt to process data in the run | |
Request (run) status | |
In progress—Usage processing is underway | |
Run Completed—All usage events in the run were processed, successfully or not | |
Failed—One or more usage events in the run were not processed successfully | |
Usage events received—Number of usage events submitted with the run | |
Usage events failed—Number of usage events in the run that did not process successfully | |
Usage events successful—Number of usage events in the run that were processed successfully | |
Usage events ready—Not applicable for IaaS billing. Value displayed is always zero. | |
Request processing status tabs | The following tabs appear when there are events in the corresponding status. The number that appears next to the tab name is the number of requests currently in that status (and that appear on the tab). |
Successful tab—All events in the request were processed successfully | |
Failed tab—One or more events in the request were not processed successfully | |
In processing tab—The requests for which processing is in progress | |
Request details | |
Date and time the request was submitted | |
Request identifier | |
Idempotency key | AppDirect-assigned request identifier |
Records processed | The number of events currently in the tab status (Successful, Failed, In Progress) and the total number of events in the request |
The Error report page provides additional information about the events that failed to process successfully and why.
Failed event errors
Error report pane | |
---|---|
Request (run) identifier, appended with the date and time of the last attempt to process data in the run | |
Reprocess System Errors—Initiates reprocessing of the events on the System Error tab. Tip: Do not attempt to reprocess system errors; AppDirect manages IaaS usage processing errors. | |
Download Report—Downloads a .csv file with error details | |
Processed on—Date and time the request was processed | |
Errors processed—The number of events that failed processing and the total number of events in the request | |
Idempotency key—AppDirect-assigned request identifier | |
Error type tabs | The following tabs display events that failed due to the corresponding error type. The number that appears next to the tab name is the number of events that failed due to the error type (and appear on the tab) |
System errors tab—Events that failed typically because of intermittent system failures during processing | |
Data errors tab—Events that failed because of bad usage data | |
System errors tab | |
Event details —Date and time the request was last submitted | |
Request (run) identifier | |
Error type and Error description—Descriptions of what caused the processing failure | |
Data errors tab | |
Event details—Date and time the request was last submitted | |
Request (run) identifier | |
Error type and Error description—Descriptions of what caused the processing failure. For example: - Reader not found with submitted Reader ID. Submit a different Reader ID, or configure a new reader and then submit its Reader ID. - Pricing plan not found for subscription ID |
Was this page helpful?
Tell us more…
Help us improve our content. Responses are anonymous.
Thanks
We appreciate your feedback!