Statuslogger will report nothing if no standard stages are found

[rsds143]

This is an odd quirk of statuslogger that if no stages are found..but GC and table stats are present there is no report.
NOTE: tarball anonymized so dates and lines are not accurate

Summary (700,000 lines)
Summary (0 skipped lines)

dse versions: unknown
cassandra versions: unknown
first log time: 2000-01-01 00:00:00.000000+00:00
last log time: 2020-01-01 10:00:0000000+00:00
Nothing found!

Same report with a bug fix for parsing all of the stages in 6.8 (also anonymized output)

                                                                                                                                                                                                                                  
Summary (800,000 lines)
Summary (0 skipped lines)

dse versions: {'6.x'}
cassandra versions: unknown
first log time: 2000-01-01 00:00:00.000000+00:00
last log time: 2020-01-01 10:00:0000000+00:00
duration: 1000.00 hours
total stages analyzed: 100
total nodes analyzed: 2

GC pauses  max        p99        p75        p50        p25        min
           ---        ---        ---        ---        ---        ---
ms         205        205        136        118        110        100
total GC events: 77

busiest tables by ops across all nodes
------------------------------
* 10.1.1.10: system_distributed.nodesync_status: 100,100 ops / 1.00 mb data

busiest table by data across all nodes
------------------------------
* 10.1.1.10: abc.zys: 70,000 ops / 5.11 mb data

busiest stages across all nodes
------------------------------
* TPC/all/WRITE_SWITCH_FOR_RESPONSE active:       100  (10.1.1.11)
* CompactionExecutor pending:                     1  (10.1.1.10)

busiest stages in PENDING
------------------------------
10.1.1.10:
       CompactionExecutor:  1

[rsds143]

I think this got fixed but I forgot to close the issue with the changes at work. Leaving open and moving milestones..may just need to verify if this is still present