Opened 3 years ago
Closed 3 years ago
#2567 closed enhancement (fixed)
petascope - enhance petascope.log with rasql / requests id
Reported by: | Bang Pham Huu | Owned by: | Bang Pham Huu |
---|---|---|---|
Priority: | major | Milestone: | 10.0 |
Component: | petascope | Version: | 9.8 |
Keywords: | Cc: | Dimitar Misev, Vlad Merticariu | |
Complexity: | Medium |
Description
In petascope.log, it is hard to know which rasql query was run when multiple queries started. For example:
INFO [2022-03-30 10:56:17] RasUtil@147: Executing rasql query: UPDATE S2_L2A_32628_WVP_10m SET S2_L2A_32628_WVP_10m[223,-9996:983,40002:50981] ASSIGN REFERENCING insitu("/tmp/R10m/T28QCM_20180103T113451_WVP_10m.jp2", "gdal", "{\"variables\":[0]}",[0:10979,0:10979]) INFO [2022-03-30 10:56:17] RasUtil@227: Rasql query executed in 1387 ms. INFO [2022-03-30 10:56:17] RasUtil@227: Rasql query executed in 69 ms.
Hence, this needs to be enhanced, by adding id to unique rasql query (pattern: rasql-i
with i
is a number counter) and petascope requests (req-i
with i
is a number counter).
For example:
RasUtil@147: Executing rasql query rasql-1234 ... RasUtil@227: Rasql query rasql-1234 executed in ...
This allow admin to grep the queries and times from petascope.log much easier.
Note:
See TracTickets
for help on using tickets.