Agent Smith: Track Agent Inventory in Azure Tables Crate
What does the Agent Smith: Track Agent Inventory in Azure Tables Crate do?
Our Agent Smith: Track Agent Inventory in Azure Tables Crate is an add-on component for Agent Smith deployments that provides enhanced inventory tracking capabilities by performing data collection from devices that run Agent Smith. On an interval, computers will collect information about themselves and post that to be stored within an Azure Tables database.
How the Crate works
Extends the basic Agent Smith setup to use Azure Tables as a storage backend
Configured to run periodic data collection tasks
Task Scheduler also monitors the Agent Smith service status
This workflow is kicked off through the following process:
Crate installation and unpacking
Automatic activation of scheduled tasks and service monitoring
Crate prerequisites
Install and deploy the following before unpacking the Crate:
Agent Smith command executor
Unpack the Agent Smith: Track Agent Inventory in Azure Tables Crate
Navigate to Crates > Crate Marketplace in the left side menu Rewst platform.
Search for
Agent Smith: Track Agent Inventory in Azure Tables Crate
.Click on the Crate tile to begin unpacking.
Click Unpack Crate.
Click Continue.
Enter Time Saved under Crate Configuration.
Ensure that Enabled is toggled on for both Cron Job and Webhook accordion menus under Configure Triggers. Note that you have the option in both Cron Job and Webhook to activate the Crate for all future organizations in addition to the current one. You may also set activation to certain tags, and set trigger criteria or integration overrides.
Click Unpack.
Test the Crate
Navigate to Automations > Workflows in the left side menu of your Rewst platform.
Search for
Agent Smith: Receive Check-In from Endpoint
.Click on the workflow to view it in the Workflow Builder.
Click Test in the top right corner of the Workflow Builder Canvas.
On the
body_stringified
field, you can enter the following:For HTTP/API actionsJSON data - If the workflow expects a JSON input, enter a valid JSON format.
json { "test": "Hello, World!", "user_id": "12345", "action": "create_user" }
For webhook testingRequest body data - This is the actual payload that would be sent to the webhook.
json { "event_type": "user_created", "data": { "name": "John Doe", "email": "{EMAIL}" } }
For general workflow input variablesStatic test data - These should be values that match the expected input variable types defined in your workflow.
String values - Enter plain text if the field requires a string.
Structured data - These should be JSON objects if the workflow processes complex data structures.
Note that the test data you enter will be accessible in your workflow as context variables (For example,
{{ CTX.body.field_name }}
for JSON data or{{ CTX.input_variable_name }}
for input variables).Click Test.
Allow the workflow to run.
You'll see a green success message at the top of your screen if the execution is successful. You'll see a red failure message if the execution fails. Click View Results for a more detailed breakdown of each.
Organization variables associated with this Crate
The following variables would be used for Azure IoT Hub integration and device management workflows:
azure_iothub_subscription_id
azure_iothub_resource_group
azure_iothub_name
Last updated
Was this helpful?