Cloud Datastore (Beta) Get Metrics activity
Introduction
A Cloud Datastore (Beta) Get Metrics activity, using its Cloud Datastore (Beta) connection, retrieves usage data from a status storage or key storage in Cloud Datastore and is intended to be used as a source to provide data in an operation.
Note
You must request access to the Jitterbit Cloud Datastore (Beta) feature to use this activity. To request beta access or provide feedback on this feature, contact the Jitterbit Product Team.
Create a Cloud Datastore (Beta) Get Metrics activity
An instance of a Cloud Datastore (Beta) Get Metrics activity is created from a Cloud Datastore (Beta) connection using its Get Metrics activity type.
To create an instance of an activity, drag the activity type to the design canvas or copy the activity type and paste it on the design canvas. For details, see Creating an activity instance in Component reuse.
An existing Cloud Datastore (Beta) Get Metrics activity can be edited from these locations:
- The design canvas (see Component actions menu in Design canvas).
- The project pane's Components tab (see Component actions menu in Project pane Components tab).
Configure a Cloud Datastore (Beta) Get Metrics activity
Follow these steps to configure a Cloud Datastore (Beta) Get Metrics activity:
-
Step 1: Enter a name and specify settings
Provide a name for the activity and specify the storage. -
Step 2: Review the data schemas
Any request or response schemas are displayed.
Step 1: Enter a name and specify settings
In this step, provide a name for the activity and specify the storage. Each user interface element of this step is described below.
The interface used in this step of the configuration of a Get Metrics activity depends on the Select storage option selected:
- Select existent storage: Select from a list of existing Cloud Datastore storages.
- Enter storage name manually: Manually enter the name of the Cloud Datastore storage.
Select existent storage
If Select existent storage is selected for Select storage, this user interface is presented:
Tip
Fields with a variable icon support using global variables, project variables, and Jitterbit variables. Begin either by typing an open square bracket [
into the field or by clicking the variable icon to display a list of the existing variables to choose from.
-
Name: Enter a name to identify the activity. The name must be unique for each Cloud Datastore (Beta) Get Metrics activity and must not contain forward slashes
/
or colons:
. -
Select storage: Select the option Select existent storage to choose an existing storage from a populated list.
-
Select a storage: This section displays Cloud Datastore storages available for the environment.
-
Selected storage: After a storage is selected, it is listed here.
-
Search: Enter any column's value into the search box to filter the list of storages. The search is not case-sensitive. If storages are already displayed within the table, the table results are filtered in real time with each keystroke. To reload storages from the endpoint when searching, enter search criteria and then refresh, as described below.
-
Refresh: Click the refresh icon or the word Refresh to reload items from the Cloud Datastore endpoint. This may be useful if storages have been added or edited in Cloud Datastore. This action refreshes all metadata used to build the table of storages displayed in the configuration.
-
Selecting a storage: Within the table, click anywhere on a row to select a storage. Only one storage can be selected. The information available for each storage is fetched from the Cloud Datastore endpoint:
-
Name: The name of the storage.
-
Type: The type of storage, either Lookup by Key (key storage) or Lookup by Status (status storage).
-
Description: The description of the storage provided during storage creation.
-
-
-
Save & Exit: If enabled, click to save the configuration for this step and close the activity configuration.
-
Next: Click to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finished button on the last step.
-
Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.
Enter storage name manually
If Enter storage name manually is selected for Select storage, this user interface is presented:
Tip
Fields with a variable icon support using global variables, project variables, and Jitterbit variables. Begin either by typing an open square bracket [
into the field or by clicking the variable icon to display a list of the existing variables to choose from.
-
Name: Enter a name to identify the activity. The name must be unique for each Cloud Datastore (Beta) Get Metrics activity and must not contain forward slashes
/
or colons:
. -
Storage: Enter the name of the storage to interact with.
-
Save & Exit: If enabled, click to save the configuration for this step and close the activity configuration.
-
Next: Click to temporarily store the configuration for this step and continue to the next step. The configuration will not be saved until you click the Finished button on the last step.
-
Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.
Step 2: Review the data schemas
Any request or response schemas are displayed. Each user interface element of this step is described below.
-
Data Schemas: These data schemas are inherited by adjacent transformations and are displayed again during transformation mapping.
Note
Data supplied in a transformation takes precedence over the activity configuration.
The request and response data schemas consist of these nodes and fields:
Request node or field Description json
Node containing the JSON request schema datastores
Node containing the storages item
Node containing storage data name
The name of the storage Response node or field Description json
Node containing the JSON request schema total
Total storages in the environment datastores
Node containing data for each storage name
The name of the storage total
Total items in a storage metadata
Node containing metadata for each storage item
Node for each storage item status
The status of the item, one of OK
,ERROR
, orABORTED
quantity
The number of items for each status in the status storage errors
Node containing any errors message
An error message success
Boolean representing the success ( true
) or failure (false
) of the data retrieval -
Refresh: Click the refresh icon or the word Refresh to regenerate schemas from the Cloud Datastore (Beta) endpoint. This action also regenerates a schema in other locations throughout the project where the same schema is referenced, such as in an adjacent transformation.
-
Back: Click to temporarily store the configuration for this step and return to the previous step.
-
Finished: Click to save the configuration for all steps and close the activity configuration.
-
Discard Changes: After making changes, click to close the configuration without saving changes made to any step. A message asks you to confirm that you want to discard changes.
Next steps
After configuring a Cloud Datastore (Beta) Get Metrics activity, complete the configuration of the operation by adding and configuring other activities or tools as operation steps. You can also configure the operation settings, which include the ability to chain operations together that are in the same or different workflows.
Menu actions for an activity are accessible from the project pane and the design canvas. For details, see Activity actions menu in Connector basics.
Cloud Datastore (Beta) Get Metrics activities can be used as a source with these operation patterns:
- Transformation Pattern
- Two-target Archive Pattern (as the first source only)
- Two-target HTTP Archive Pattern (as the first source only)
- Two-transformation Pattern (as the first or second source)
To use the activity with scripting functions, write the data to a temporary location and then use that temporary location in the scripting function.
When ready, deploy and run the operation and validate behavior by checking the operation logs.