Sign in Sign up
  • Home
  • Join
  • Courses
    • Garden Tours (Start Here!)
    • The Garden Paths
    • All Courses
  • News
  • Activity
  • Help
    • Feature Requests
  • Contact
Back to Course

Introduction to Observability

0% Complete
0/0 Steps
  1. What is observability?
    2 Topics
    1. The Setup: Great News, Team!
    2. What Is Observability?
  2. Get Data In
    5 Topics
    1. Get Your Honeycomb Team
    2. Get your own Sequence of Numbers
    3. Connect it to Honeycomb
    4. About the dataset
    5. See Your Data in Honeycomb
  3. Dig Into Your System
    6 Topics
    |
    1 Quiz
    1. A Random Trace
      1. Now you try it!
    2. From the Top
    3. How to Look at a Trace
    4. A Clue From a Trace
    5. Heatmap of Duration
    6. trace.parent_id does not exist
  4. What is different?
    3 Topics
    1. Find the Distinguishing Factors
    2. Group By with a Heatmap
    3. Sharing the Story
  5. Customize the Telemetry
    7 Topics
    1. Find the code to change
    2. Add an attribute to a span
    3. Name the attribute
    4. See the difference in production
    5. Studying a trace
    6. Query the spans within a single trace
    7. Asynchronous collaboration
  6. Fixing the Problem
    3 Topics
    1. Is it safe?
    2. Building observability in
    3. Seeing the impact
Introduction to Observability Dig Into Your System trace.parent_id does not exist
Module 3, Topic 6
In Progress
← Previous Next→

trace.parent_id does not exist

Module Progress
0% Complete

Oop, this content isn't available to visitors. Please register or log in to continue!

Forum Description

The latency heatmap shows the filter of every request, not every event sent to Honeycomb. This video goes into detail on how that works.

Along the way, we use some new tricks:

  • search for fields on a span
  • filter for a field value across spans in a trace
  • modify a query and run a new one
https://shiprise.wistia.com/medias/w2kyuxnhk1?embedType=async&videoFoam=true&videoWidth=640

We found one slow trace.

A few topics ago, we found one slow trace by clicking on a dot high in the latency graph. We haven’t studied that trace yet. Before we focus on one trace, let’s ask a broader question: what makes some requests slower than the others?

When we know that, we’ll know which traces are part of a broad trend that makes requests slow. This will distinguish importantly-slow traces from random outliers.

Report

There was a problem reporting this post.

Harassment or bullying behavior
Contains mature or sensitive content
Contains misleading or false information
Contains abusive or derogatory content
Contains spam, fake content or potential malware

Block Member?

Please confirm you want to block this member.

You will no longer be able to:

  • See blocked member's posts
  • Mention this member in posts

Please allow a few minutes for this process to complete.

Report

You have already reported this .
Clear Clear All