Project

General

Profile

Actions

Task #5827

open

[investigate] output/drop: make `drop reason` more informative

Added by Juliana Fajardini Reichow almost 2 years ago. Updated 6 months ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
Effort:
Difficulty:
Label:

Description

With drops being caused by elements such as the exception policies, `drop.reason` needs more data
to be actually informative.
Two examples of drop reasons that seem to not show enough to be conclusive to users:

drop.reason: "applayer error" 

or
drop.reason: "stream memcap" 

I've created this with the [investigate] "tag" because it actually seems that each of those reasons could only happen under specific cases
- and yet, when debugging, the info might seem incomplete...

Actions #1

Updated by Victor Julien over 1 year ago

  • Tracker changed from Optimization to Task
Actions #2

Updated by Victor Julien 6 months ago

  • Assignee changed from Juliana Fajardini Reichow to OISF Dev
Actions

Also available in: Atom PDF