Skip to main content

​
Overview

You can use dynamic URLs to open Explore v2 (Beta) with pre-specified data by encoding visualization parameters directly into the browser address. By navigating to the /explore route with specific query parameters, you can instantly load targeted telemetry datasets for rapid review and automated reporting. This capability allows you to create dynamic entry points that are pre-configured with the exact data context required for a specific analysis task. These URLs allow you to define the exact data to plot, including the specific Run or Asset, Channels, and designated Panel type. The system also supports setting precise start and end times for the analysis session to focus on specific events. This automation ensures that team members land on the exact telemetry required for their review without the need for manual setup or navigation through the standard interface.
Explore v2 (Beta): The /explore endpoint is similar to Explore v1, but the parameters differ significantly for Explore v2 (Beta). To learn more, see Endpoint structure.

​
Endpoint structure

To launch a targeted analysis in Explore v2 (Beta), use the /explore route followed by the ?method=single parameter. This base configuration ensures the application initializes correctly to handle the additional telemetry parameters provided in the URL. The full URL is constructed as follows: 
{domainName}/explore?method=single \
  &runId={uuid1,uuid2,...} \
  &runIds={uuid1,uuid2,...} \
  &runs={runNameOrUUID1,runNameOrUUID2,...} \
  &assetId={uuid1,uuid2,...} \
  &assetIds={uuid1,uuid2,...} \
  &assets={assetNameOrUUID1,assetNameOrUUID2,...} \
  &channels={axisPrefix:channelNameOrUUID,...} \
  &channelId={channelNameOrUUID,...} \
  &channelIds={channelNameOrUUID,...} \
  &panelType=timeseries|table \
  &startTime=YYYY-MM-DDTHH:MM:SSZ \
  &endTime=YYYY-MM-DDTHH:MM:SSZ
Format: This structure uses backslashes (\) and line breaks for readability. When creating the actual URL, combine all parameters into a single continuous string, connecting them with &, without spaces or backslashes.
Order of parameters: The order of query parameters does not matter and they may appear in any position. However, the base structure must begin with domainName/explore?method=single.

​
Channel and axis configuration

The channels, channelId, and channelIds parameters are aliases and all accept a comma-separated list of Channel UUIDs, Channel names, or a mix of both. Each parameter supports 0, 1, or more values. When Runs and/or Assets are provided, listed Channels are matched across all selected data sources and auto-plotted. You can control which vertical axis each Channel plots to by adding a specific prefix. Axis prefixes work with both UUIDs and names. Only the four valid axis prefixes (L1, L2, R1, R2) are recognized colons that appear within Channel names (for example, sensor temperature) are not treated as axis prefixes.

​
Examples

The following examples demonstrate how to construct dynamic URLs for specific analysis scenarios using https://app.siftstack.com as the base domain.
Format: The examples below use backslashes (\) and line breaks for readability. When using these URLs in a browser or API request, remove the backslashes and line breaks, and combine all parts into a single continuous string, connecting query parameters with & and without any spaces.

​
Mixed Run and Asset selection

This example pre-selects multiple Runs and Assets in the same URL. runId/runIds and assetId/assetIds can be mixed and matched, and each accepts comma-separated values. 
https://app.siftstack.com/explore \
  ?method=single \
  &runIds=8bfc7a2a-de0c-402c-bec1-089f4a69f128,2fd5e1f9-d185-4f18-a31d-8f2aee20ef17 \
  &assetId=5161a578-c3f2-4ecb-8ea9-ae6fcbf3b3f0 \
  &panelType=timeseries
  • runId and runIds are equivalent
  • assetId and assetIds are equivalent
  • Runs and Assets can be provided together, and provided IDs are auto-selected on page load

​
Timeseries with mixed axes

This example uses the Timeseries panel type to plot specific Channels to different vertical scales (L1 and L2) for comparison. It also shows that channelIds behaves the same as channels. 
https://app.siftstack.com/explore \
  ?method=single \
  &runId=8bfc7a2a-de0c-402c-bec1-089f4a69f128 \
  &assetIds=5161a578-c3f2-4ecb-8ea9-ae6fcbf3b3f0 \
  &panelType=timeseries \
  &channelIds=L1:df2cba99-abc2-4b36-bd16-e615b7682ace,L2:8dad764f-fda2-4784-9132-ddc616df46c1
  • panelType=timeseries is shown explicitly, but this is also the default if panelType is omitted
  • channels, channelId, and channelIds are equivalent
  • If Run and/or Asset IDs are provided, listed Channels are matched across selected data sources and auto-plotted
  • Each Channel UUID is prefixed with an axis label (L1, L2) to control which vertical scale it is plotted against
  • If axis prefixes are omitted, Channels are plotted using the default axis (L1)

​
Zoomed-in analysis

This configuration focuses on a specific time window by including startTime and/or endTime parameters. 
https://app.siftstack.com/explore \
  ?method=single \
  &runId=8bfc7a2a-de0c-402c-bec1-089f4a69f128 \
  &panelType=timeseries \
  &channels=L1:df2cba99-abc2-4b36-bd16-e615b7682ace \
  &startTime=2024-05-26T13:59:28.569Z \
  &endTime=2024-05-26T14:02:52.232Z
  • startTime and endTime are optional and may be provided independently
  • If only startTime is specified, data is shown from that time until the end of the Run
  • If only endTime is specified, data is shown from the beginning of the Run up to that time
  • Timestamps must be in ISO 8601 format (UTC)

​
Table view

To view data in a tabular format, set the panelType to table. This example displays data values at the timestamp specified by startTime. The endTime parameter is not used in this view and is ignored if provided. 
https://app.siftstack.com/explore \
  ?method=single \
  &runId=8bfc7a2a-de0c-402c-bec1-089f4a69f128 \
  &panelType=table \
  &channels=df2cba99-abc2-4b36-bd16-e615b7682ace,8dad764f-fda2-4784-9132-ddc616df46c1 \
  &startTime=2024-05-26T14:00:00.000Z
  • When panelType=table, data is evaluated at a single point in time defined by startTime
  • The endTime parameter is ignored for table views, even if it is provided
  • Channel axis prefixes (for example, L1:) are not applicable in table views

​
Run by name

This example selects a Run by its human-readable name instead of its UUID and plots two Channels by name. 
https://app.siftstack.com/explore \
  ?method=single \
  &runs=my-test-run \
  &channels=temperature,pressure
  • The runs parameter accepts Run names, UUIDs, or a mix of both
  • If the name my-test-run matches multiple Runs, the most recently created Run is used
  • Channel names (temperature, pressure) are resolved automatically

​
Asset by name with axis configuration

This example selects an Asset by name and assigns Channels to different axes using Channel names. 
https://app.siftstack.com/explore \
  ?method=single \
  &assets=my-asset \
  &channels=L1:temperature,R1:pressure
  • The assets parameter accepts Asset names, UUIDs, or a mix of both
  • Axis prefixes (L1:, R1:) work with Channel names the same way they work with UUIDs

​
Mixed UUIDs and names

This example demonstrates mixing UUIDs and names in the same URL. The system auto-detects whether each value is a UUID or a name. 
https://app.siftstack.com/explore \
  ?method=single \
  &runs=8bfc7a2a-de0c-402c-bec1-089f4a69f128 \
  &channels=temperature,L2:8dad764f-fda2-4784-9132-ddc616df46c1
  • The runs value is a UUID and is used directly
  • The first Channel (temperature) is a name and is resolved to its UUID automatically
  • The second Channel uses a UUID with an L2 axis prefix
  • UUIDs and names can be freely mixed within any parameter