Welcome to the Cribl UX Weekly Update, a brand new site from your friendly UX goats! This update will provide you with all the latest happenings in our design team, including hiring updates, ongoing and completed research, concept explorations, and designs we are finalizing. We'll also share any updates on accessibility, the design system, and general UX patterns across our products. If there's anything you feel might be missing week to week or you feel that we would benefit from adjusting the format, please let us know, and we'll be sure to iterate on what we're sharing.

Stream

Ai-608/Cribl Copilot

Using AI to help users event break log files

The problem we're trying to solve is a user has a sample log file from an external system that they want to run through Stream to assure the pipelines they configure are going to work properly once log data begins to flow from their sources to their destinations. This is exploration is to see if the Copilot can detect the log file type then auto-magically suggest the best config for the file type. Draft is out to small Ai internal team for review as well as Dritan. Figma | JIRA TBD

Tiles and New Stream Home Page Concept

With the addition of the cloud provider tag, the WG tiles have become too small to display all necessary data. As a result, we’ve been working on a new concept for the Stream/Edge homepage. In a recent UX interview, a user requested charts for each WG rather than just a single summary, as they use this information for health checks. We’re awaiting further interviews to refine the concept.

Separate (Basic) Authentication for Kafka Schema Registry

We are working with Aaron Whittier on redesigning the Schema Registry section of the Kafka destination configuration to accommodate three sections that require enabling. We designed and created a clickable prototype to illustrate interaction. Currently using progressive disclosure but will revisit at a later date to determine how we want to treat configuration screens throughout the product suite.
JIRA FIGMA

In-Pipeline Metrics Management UX Improvements

Continuing work with Josh Biggley on designing a new user experience for how they interact with metric data in building pipelines. We started a fresh Figma document to keep the older work archived. Currently exploring how users can drop, aggregate or roll-up metrics as well as add or drop specific dimensions.
JIRA FIGMA

SEARCH

SEARCH-6915/History/Saved Quick Access

Allow users to reference previous searches quickly in context

The problem we're trying to solve here is a user cannot access history/saved searches without leaving their current search. When crafting kusto queries its helpful to be able to easily reference/copy/use other searches you have ran recently or saved. You might want to use a unique portion of a previous search and having this data 1 click away from your current search is ideal. Users can access last n searches and filter for more. The full History and Saved pages are still available in the same location as before (top) this is an enhancement to working faster with KQL. Reviews sent to Nick F and Dritan for review. Figma | JIRA

Search-6431/Dashboards

Creating external/internal links that can be invoked on dashboard panels

The problem we're solving is users host related data in various places and there is no way to connect the dots between a Cribl dashboard and that data. The goal here is to provide a way for more robust dashboards that users can link to external webpages/applications/or other dashboards in the Cribl suite. Users should be able to link single panels in a dash as well as generate a list of helpful links from the dashboard itself Figma | JIRA

Global Items, Design System and Patterns

Global Navigation /TCTI-21/Breadcrumbs

Perfecting the usage of breadcrumbs in complex areas

The problem we're solving here is the logic for how breadcrumbs are generated is not perfect for different uses. Our navigation system is complex/nested and the breadcrumbs need to guide the users context at all times. Some rules we established were too much like blanket statements and the nuances of when to render a page in a breadcrumb chain isn't perfect. This is still in progress but we've identified 5 fixes needed so far and some more to come to complete this effort.
Figma | JIRA 1 | JIRA 2 | JIRA 3 | JIRA 4 | JIRA 5

Integrations

Sources and Destinations homepage

We continued developing the POC concept for the Sources and Destinations homepage and subpages, which we are opening in a modal to reduce scope, as this is how it functions today. This initiative aims to identify and improve common customer incident areas within Integrations. JIRA | FIGMA

Primary Goals:

• Reduce support cases related to sources and destinations.
• Decrease the time to identify source and destination issues.
• Enhance the user experience for data stream management.

Proposed Changes:

• Replace the tile view with a redesigned list view layout.
• Improve filtering by adding status-based filters.
• Introduce a “Health” page for better performance management and troubleshooting.

Billing

We’ve added an “email invoices” option with a scheduler, allowing users to receive invoices regularly, and they can now download invoices in JSON/CSV format on demand (see JIRA). We’re planning to conduct UX research on billing in the upcoming weeks. Our goal is to understand general usage, identify any gaps (or confirm if everything is already perfect), and evaluate what’s working and what isn’t. (see Script)

Edge

Ease of Use:

As we embark on a multi-release effort to identify issues with individual nodes related to Upgrades, Source, and Destination states, it's crucial for customers to view this information at a fleet level. This is especially important for customers with many fleets, as it becomes challenging to drill down into each fleet individually to identify node problems. FIGMA JIRA

• Display node information, including source/destination status and activity | JIRA.
• Highlight health status at the fleet level | JIRA .
• Show source/destination status on the Edge homepage, similar to the Stream homepage.
• Ensure fleets highlight any issues with sources or destinations.

Research

Unfortunately our fearless research lead is out sick this week. More to come next week.

Small But Mighty

These are weekly bugs and random Issues we uncover. Our proposed fixes are inside each ticket.

These tickets cover various products (Stream, Edge, Search) and address UX polishing, bugs, and other improvements. Although they’re all from Paul and Sylwia this week, we plan to make this a standard practice across UX to enhance overall usability, consistency, and address any other areas needing improvement.

JIRA

JIRA