A playlist is a list of sessions that a team keeps to go through one after the other: the sessions of a bug report, the visits that
ended in the same error, the people a change is meant to help. RUM → Playlists lists them. A playlist belongs to one
application and is seen by everyone who may read RUM (streams.query). Making or changing one requires rum.manage.
Share a moment of a replay
Copy link to this moment in the head of a session copies the address of the session with the replay opened at the moment it is
at. Whoever opens the link finds the replay held there until it is played. A session whose replay has not been read yet, or that
recorded none, gives the plain address, Copy link.
The address carries the moment as at, in microseconds since the epoch, and the stretch of time the session ran in as from and
to, so that a link to an old session still finds it.
Put a session in a playlist
Add to playlist in the head of a session lists the playlists of its application, with how many sessions each holds. A mark
says the session is in a playlist. Click a playlist to put the session in, and click it again to take it out.
- Open it at this moment of the replay puts the session in with the moment the replay is at, so that it opens there from the
playlist. Without it, the session opens at its beginning. A session that is put in again takes the new moment and keeps its place.
- A name and Create and add make a new playlist of the application with the session in it.
A playlist holds at most 500 sessions, each once, in the order they were added.
The list of playlists
The list gives each playlist with its description, its application, how many sessions it holds, when it was changed last, and who
made it. The one changed last is first. With more than one application, choose the application to narrow the list.
- New playlist asks for a name of up to 128 characters, a description of up to 1,000, and the application. A playlist cannot
have the name of another playlist of the same application, whatever the case.
- A row opens the playlist.
One playlist
A playlist lists its sessions in the order they were added, each with its first page, who it was of, when it began, how long it
lasted, what happened in it (errors and signs of frustration), and the moment it opens at, counted from the beginning of the
session. A session whose rows are no longer in the data, because their retention has ended, says Not found in the data; it stays in
the list until it is taken out with the cross at the end of its row.
- Play from the first opens the first session.
- Rename changes the name and the description. The application stays.
- Delete playlist removes the playlist after a confirmation. The sessions in it are not touched.
Go through a playlist
A session opened from a playlist shows a bar above it: the name of the playlist, which session of how many this is, and
Previous and Next. Each opens its session at the moment it was put in at. A session that is gone from the data keeps the bar, so
the walk goes on. The playlist is in the address as playlist, so reloading the page keeps the bar.
API
The RUM API lists, makes, changes, and deletes playlists and puts sessions in and takes them out. Last modified on October 26, 2026
