Skip to content
Explore the preview
Browse workflow ideas

Give your monitoring process realistic sample readings to work with.

Illustrative idea, not a published runnable template. Grunt is prelaunch; live service is paused and live provider connections and outcomes remain unverified. The steps, providers, and outcomes below describe a concept.

Create scheduled test records with a configured sensor identifier, a generated sample value, a timestamp, and an unset alert status. Keep sample data separate from live measurements so teams can safely validate their monitoring process.

Explore the simulation Explore the idea

Actual availability depends on published steps, supported connections, permissions, and provider approval.

Illustrative workflow and outcome
Scheduled sample-data runA configured testing schedule and a list of sample sensor identifiers
“At the agreed interval, prepare sample sensor readings with their identifiers, generated values, timestamps, and initial notification status, then save them to the designated test record set.”
Work through the request.

Clear tasks, with review where it matters.

  1. Select the sample sensor identifiers
  2. Generate a sample reading
  3. Add a recorded time and initial alert state
See all 5 tasks
A time-stamped set of synthetic sensor records in the approved testing collection, ready for monitoring and reporting checks.

What this workflow could do

Produces repeatable sample readings and stores them in a designated test collection so teams can exercise monitoring and alert review.

Review points proposed in this idea

Generated values are simulated and must never be presented as real sensor measurements or mixed into production decisions. An owner should approve the test destination, schedule, and data-retention approach before the process runs.

How the idea could work

Select an illustrative task to explore its proposed role. No workflow runs here.

Explore the sequenceStep 1 of 5

  1. Use only the sensor labels configured for the test dataset.

Step 1 of 5

Select the sample sensor identifiers

Use only the sensor labels configured for the test dataset.

Proposed setup considerations

These are planning notes for the concept, not instructions for a currently available template.

  1. 01

    Define the sample record fields

    Choose the sensor identifiers, generated-value range, timestamp convention, and initial notification status required for testing.

  2. 02

    Approve a separate test destination

    Select a collection clearly separated from live operational measurements and confirm who may access or remove its records.

  3. 03

    Set the schedule and retention period

    Choose how often sample rows are created and how long test records should be kept.

  4. 04

    Validate the sample-data boundary

    Check that reports and decisions based on live measurements exclude synthetic records.

Read the prelaunch status

Published templates and verified customer availability remain pending.

A little help with the whole task

A little less busywork.
A little more room for you.

Explore the sample experience while launch details are being finalized.

View pricing status Explore the simulation