taylor laubach


System Log


Make it possible for customers to use our log data without exporting it


Sole designer and user researcher. Collaborated with PM and Eng.


Data had to be exported

Users were not able to find the events they needed in the system log of an identity management platform. They were being forced to download their data and manipulate it in Excel. We wanted to fix this and to use our solution as the foundation for a new analytics product area.


Understand usecases and workflows

I started by identifying and interviewing the various user groups that utilize the logs. I made a list of their use cases and their pain points. The main use case was troubleshooting, and the main issues with troubleshooting were:


Support how users work

I made a simple looking interface that allows a user to easily search using any value, but also to construct complex custom queries on any field. Typeahead suggests values that exist in the data for each filter field as it's suggested. In addition, a user may, upon finding an event with a relevant value (the main way that users described finding relevant values to filter by), simply click the value to add a filter by that field and value. Histograms at the top show distribution of events across each value of the most important fields, making it easy to find patterns.

New system log

There are tools to easily find patterns and select relevant filter values.

The system log.

The most important data is highlighted, but all the data is available

A single system log event, expanded.

Table, map, or graph

In addition to a tabular view, users may choose to visualize their data as a map or graph.

A map view of the data. A graph view of the data.

Query builder

The query builder.