Many of our applications log an associated TLTSID when an error occurs. We would like to have the capability to programmatically access the related tealeaf session from our event logs. With on-prem Tealeaf, we had this capability by utilizing the TLSearchServer api. Since this api is not available in SaaS, this functionality is no longer available.

Current state:

When a session is opened, the url can be copied so that it provides direct access to the session. This is great, with the exception that the sid portion of query string requires the exact beginning timestamp of the session (_20190207152324). This timestamp value is unknown to our systems at the time an error gets logged.

https://tealeaf.ibmcloud.com/webapp/home#/session-replay-timeline?org=xxxxxxxxx-xxxxxxxxx&sid=xxxxxxxxxxxxxxxxx_20190207152324&tltsid=xxxxxxxxxxxxxxxxxxxx

Suggestion:

One solution would be to allow the above url to accept only the tltsid portion of the query string and default the search time range to the last 24 hours.