Major Description
In a CBSE the http access log had these entries
127.0.0.1 - @localtoken [12/Mar/2024:18:21:15 +1100] "GET /diag/password HTTP/1.1" 200 32 - curl/7.60.0-DEV
|
127.0.0.1 - @ [12/Mar/2024:18:21:17 +1100] "GET /diag HTTP/1.1" 200 chunked - curl/7.60.0-DEV
|
127.0.0.1 - @ [12/Mar/2024:18:22:26 +1100] "GET /diag/masterEvents?o=1 HTTP/1.1" 200 0 - curl/7.60.0-DEV
|
127.0.0.1 - @ [12/Mar/2024:18:22:26 +1100] "GET /diag/ale HTTP/1.1" 200 2349 - curl/7.60.0-DEV
|
127.0.0.1 - @localtoken [14/Mar/2024:21:03:58 +1100] "GET /diag/password HTTP/1.1" 200 32 - curl/7.60.0-DEV
|
127.0.0.1 - @ [14/Mar/2024:21:03:59 +1100] "GET /diag HTTP/1.1" 200 chunked - curl/7.60.0-DEV
|
127.0.0.1 - @ [14/Mar/2024:21:05:08 +1100] "GET /diag/masterEvents?o=1 HTTP/1.1" 200 0 - curl/7.60.0-DEV
|
127.0.0.1 - @ [14/Mar/2024:21:05:08 +1100] "GET /diag/ale HTTP/1.1" 200 2349 - curl/7.60.0-DEV
|
which indicates a cbcollect was taken on 12Mar2024 starting around 18:21:15. The collection of the bundle might have impacted the performance of the node so I wanted the start/end times of that cbcollect (and I don't have the resultant bundle). I just have the bundle collected on 14Mar2024.
It would be nice if cbcollect could use the /_log endpoint as the first/last thing done.
xcurl localhost:9000/_log -d 'message=starting_log_collection&logLevel=info&component=cbcollect_info'
|
|
|
xcurl localhost:9000/_log -d 'message=ending_log_collection&logLevel=info&component=cbcollect_info'
|