Who rated this post

The Doctor Log script outputs diagnostic information that should help you determine this.
At a high level, the script returns the following:

*** Diagnostics Results ***

System Status : OK
Changes in Config Files : OK
MGMT version : OK
Registry file Corruptions : OK
Load Average : OK
Check Processes : Error
Inconsistencies Detector : OK
Connections Config : OK
GW's and Log Clients : OK
Problems in Debug Log Files : OK
Rfl/Solr Memory Report : OK
Verify FetchedFiles : OK
Maintenance Configuration : OK
Smart View Status : Warning
SmartView performance : OK
Topology View : OK
Abnormal Long Requests : OK
RFL Status Query : OK
Current Logging Rates : OK
Daily Average Logging Rates : OK
Sizing status : OK
Detects Indexing Delay : OK
Top Consuming Processes : OK
dbsync status : OK

It will show some additional information, including logging rates, top consuming processes, and issues found, as shown below.
In this case, it's a standalone gateway running R81.20 and not passing traffic (thus the warning about log rates) 🙂

Issues Found:
----------------------------

System Info:
  Attention           : Some of the server's jars are from different versions 

Registry file Corruptions:
  Possible fix        : Please refer to: sk168472 

Check Processes:
  ERROR               : RFL_SOLR_MAX_HEAP is smaller then RFL_SOLR_MIN_HEAP. 'D_SOLR' process will fail to start. 
  Possible fix        : Please refer to: sk172385 

Smart View Status:
  WARNING             : Found no data in the file: [smartview] from the last 1 hours 
                              Check the debug logging level of smartview 
                              If debug level is correct this could indicate that the process is stuck 


Current Logging Rates:
  Hint                : Indexed mode is disabled (non-indexed mode) 

Summary:
Found 1 Errors, 1 Warnings in this running configuration.

Detailed report and more can be found under /tmp/sme-diag/results

*** Diagnostic Completed ***