Skip to main content

​
Overview

You can use parameterized 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). Explore v2 requires the method=single parameter, uses UUIDs instead of names for Runs, Assets, and Channels, and uses startTime/endTime instead of from/to. 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|assetID=[runID|assetID] \
  &panelType=[panelType] \
  &channels=[channels] \
  &startTime=[startTime] \
  &endTime=[endTime]
Format: This structure uses backslashes (\) and line breaks for readability. When creating the actual URL, combine all parameters into a single continuous string without spaces or backslashes.

​
Channel and axis configuration

The channels parameter accepts a comma-separated list of Channel UUIDs. You can control which vertical axis each Channel plots to by adding a specific prefix.

​
Examples

The following examples demonstrate how to construct URLs for specific analysis scenarios using https://app.siftstack.com as the base domain.
Format: The examples below use backslashes (\) and line breaks to improve readability. To use these URLs in a browser, you must remove the backslashes and combine the text into a single continuous string without spaces.

​
Timeseries with mixed axes

This example uses the Timeseries panel type to plot specific Channels to different vertical scales (L1 and L2) for comparison. 
https://app.siftstack.com/explore \
  ?method=single \
  &runID=8bfc7a2a-de0c-402c-bec1-089f4a69f128 \
  &panelType=timeseries \
  &channels=L1:df2cba99-abc2-4b36-bd16-e615b7682ace,L2:8dad764f-fda2-4784-9132-ddc616df46c1

​
Zoomed-in analysis

This configuration focuses on a specific time window by including startTime and 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

​
Table view

To view data in a tabular format, set the panelType to table. This configuration 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