Replies: 1 comment 3 replies
-
Hey @NgLoader , this is very interesting. I wonder, though, if this overlaps with features that we could include in a future-planned tracing product? See: |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Incorporating a backend session replay feature into web applications can significantly improve the backend experience, similar to how clients benefit from session replay.
There are several compelling reasons why this feature should be considered:
Customized Hardware: In many cases, the backend of a web application is hosted on the customer's servers, which may have custom hardware configurations and background tasks.
By implementing a backend session replay feature, developers can gain insights into how the application is performing on this unique hardware, enabling them to better support customers.
Multiple Servers: Another common scenario is when the backend is distributed across multiple servers, which makes it challenging to analyze logs and identify issues.
A backend session replay feature would allow developers to replay sessions across all servers and gain a view of how the application is behaving, thereby making it easier to troubleshoot and optimize performance.
Metrics: Just getting some more details of how the currently backend is running like
cpu usage
,api request
,ram usage
and so one.It could also be separated into the frontend with two sections
frontend
andbackend
undersessions
.I understand when the Highlight team may not currently plan to support this feature, as it could change the nature of the project.
I hope to get some feedback from the community what they think about this.
Issue: #4446
Beta Was this translation helpful? Give feedback.
All reactions