We use cookies or similar technologies to personalize your online experience and tailor marketing to you. Many of our product features require cookies to function properly. Your use of this site and online product constitutes your consent to these personalization technologies. Read our Privacy Policy to find out more.


Client-side code

What can you observe?

Client-side observability can enable impressive scenarios for understanding the true effects of user experience. With large Javascript running in the browser, being able to track how users experience both front-end code and back-end experiences can be invaluable. With Honeycomb, client-side events must be batched together and proxied through the server, which can send them to Honeycomb to avoid cross-site scripting issues.

In a front-end observability scenario, Honeycomb can track user experience questions like:

What is the top of the stack?

The ‘top of the stack’ are any entry points where user input or browser actions can cause a change. Finding where to instrument can be more challenging than other applications because there isn’t a single entry point: instead, the choice of events may be spread throughout the code.

What is the unit of work?

The unit of work are the various events within the browser app. This might include page rendering, user clicks and interactions, and page transitions. In a single application, it might be useful to instrument how long the page takes to render, how long it takes for a query to respond to a click, and how long it takes an autocorrect function to suggest a new word.

What context is useful to capture?

For each event, the event should capture:

What comes next?