Retrieve a Replay Instance

Go to Product

Return details on an individual replay.

Options

Organization Slug
The slug of the organization the resource belongs to.
Replay Id
The ID of the replay you'd like to retrieve.
Stats Period (*)

This defines the range of the time series, relative to now. The range is given in a <number><unit> format. For example 1d for a one day range. Possible units are m for minutes, h for hours, d for days and w for weeks. You must either provide a statsPeriod, or a start and end.

Start (*)

This defines the start of the time series range as an explicit datetime, either in UTC ISO8601 or epoch seconds. Use along with end instead of statsPeriod.

End (*)

This defines the inclusive end of the time series range as an explicit datetime, either in UTC ISO8601 or epoch seconds. Use along with start instead of statsPeriod.

Field (*)
Specifies a field that should be marshaled in the output. Invalid fields will be rejected.
Project (*)
The ID of the projects to filter by.
Environment (*)
The environment to filter by.
Sort (*)
The field to sort the output by.
Query (*)
A structured query string to filter the output by.
Per Page (*)
Limit the number of rows to return in the result.
Cursor (*)

The cursor parameter is used to paginate results. See here for how to use this query parameter

Result Format
Specify how the response should be mapped to the table output. The following formats are available:
  • Structured Table: Returns a parsed table with data split into rows and columns.
    • Id:
    • Project Id:
    • Trace Ids:
    • Error Ids:
    • Environment:
    • Tags:
    • User:
    • Sdk:
    • Os:
    • Browser:
    • Device:
    • Is Archived:
    • Urls:
    • Clicks:
    • Count Dead Clicks:
    • Count Rage Clicks:
    • Count Errors:
    • Duration:
    • Finished At:
    • Started At:
    • Activity:
    • Count Urls:
    • Replay Type:
    • Count Segments:
    • Platform:
    • Releases:
    • Dist:
    • Count Warnings:
    • Count Infos:
  • Raw Response: Returns the raw response in a single row with the following columns:
    • body: Response body
    • status: HTTP status code

Input Ports

Icon
Configuration data.

Output Ports

Icon
Result of the request depending on the selected Result Format.
Icon
Configuration data (this is the same as the input port; it is provided as passthrough for sequentially chaining nodes to declutter your workflow connections).

Popular Predecessors

  • No recommendations found

Popular Successors

  • No recommendations found

Views

This node has no views

Workflows

  • No workflows found

Links

Developers

You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.