GoTransverse Query
Prerequisite
The user of this function should be familiar with:
GoTransverse ( https://gotransverse.com )
The GoTransverse Query function is a processor that is used to query data from GoTransverse deployments using specified options and parameters. You can query records and further process them using the available functions in Usage Engine.
To configure the GoTransverse Query function, fill in the mandatory fields in the Configuration with the required information.
Environment
You select the Tenant by selecting one of the available options:
Tenant type | Description |
|---|---|
GoTransverse API Sandbox | Select this option to specify GoTransverse API Sandbox tenant for test configurations and other related use cases. |
GoTransverse API Production | Select this option to specify GoTransverse API Production tenant. |
Custom | Enter a custom tenant URL. |
GoTransverse credentials
Enter the Secret access key in the designated field. Optionally, you can also enable Secrets wallet to enter the credentials.
Query parameters
Open the Configurations tab to enter the desired options using the dropdown menu. For each query option, there are different queries that can be selected by entering a Key and Value in the fields. Select the appropriate option and then add the parameter using the Add query parameter.
Query options | Description | Key query options |
|---|---|---|
GET Billing Accounts - All | Select this option to retrieve a subset of existing billing accounts. | account_num, filter, id, return, status |
GET Usage Lookup Tables - All | Select this option to retrieve a subset of existing usage lookup tables. | filter, id, name, return, status |
Get Usage Lookup Tables Entries - Specific ID | Select this option to retrieve an existing usage lookup table entry associated with the specified usage lookup table and entry IDs. | filter, id, name, return, status |
Operational settings
This section contains settings that can be optionally set to adjust the GoTransverse function behavior.
You can toggle Retry on fail to let the service retry each request when the server returns error codes such as 429, 500, or 503 because of intermittent server issues or rate limiting.
You can specify the number of retries in the Number of retries box, and the service performs those retries within a dynamically adjusted retry period. This retry behavior applies only to 5xx and 429(Too many requests) error codes.
Note!
The maximum number of allowed retries is 12 and all retries will be attempted in a total span of a maximum of 68 minutes.
You can choose to either Ignore or Stop the stream when an error is detected.