Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 9.4
-
Component/s: None
-
Edition:Community
Description
It's not obvious to quickly identify in the different logs when SonarQube has restarted.
Currently, it's quite clear in sonar.log:
2017.11.08 13:05:40 INFO app[][o.s.a.SchedulerImpl] SonarQube is stopped <-- Wrapper Stopped --> Wrapper Started as Daemon Launching a JVM...
But it's less obvious in es.log:
2017.11.30 15:11:00 INFO es[][o.e.n.Node] closed 2017.11.30 15:22:32 INFO es[][o.e.n.Node] initializing ...
in web.log:
2017.11.30 15:10:57 INFO web[][o.s.p.StopWatcher] Stopping process 2017.11.30 15:22:41 INFO web[][o.s.p.ProcessEntryPoint] Starting web
and in ce.log:
2017.11.30 15:10:56 INFO ce[][o.s.ce.app.CeServer] Compute Engine is stopped 2017.11.30 15:23:04 INFO ce[][o.s.p.ProcessEntryPoint] Starting ce
We should have similar logs for each process when it stops and starts. Also, we could have a clear additional marker:
Ex in web.log:
2017.11.30 15:10:57 INFO web[][o.s.p.StopWatcher] Stopping process 2017.11.30 15:10:59 INFO web[][o.s.p.StopWatcher] Web stopped <-- Process stopped --> Process started 2017.11.30 15:22:41 INFO web[][o.s.p.ProcessEntryPoint] Starting web
Attachments
Issue Links
- is related to
-
SUPPORT-8048 Loading...
- relates to
-
