This counter tracks the number of traced frames discarded specifically because the trace session's queue was full, wrapping back to 0 after reaching its maximum value. An admin monitors it to quantify trace data loss due to queue overflow, noting that frames dropped while the queue was in the blocked state are not included in this count. For example, a rising traceSessionFramesDiscarded count during a busy trace session would tell an admin the queue is regularly filling up and some traced data is not making it to the receiver.