Opened 10 hours ago
Last modified 11 minutes ago
#2848 closed enhancement
FIX - rasql queries logged in petascope.properties should contain the request id as well — at Initial Version
| Reported by: | Bang Pham Huu | Owned by: | Bang Pham Huu |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | petascope | Version: | 10.4 |
| Keywords: | Cc: | Dimitar Misev | |
| Complexity: | Medium |
Description
Currently, in petascope.log, it only logs rasql queries separately, e.g.
Executing rasql query rasql-2639 with user unauthenticated: SELECT ENCODE(( ( scale( scale( ( ( sqrt( POW(c0[14129,2,0:408,0:376].0, 2.0) + POW(c0[14129,2,0:408,0:376].1, 2.0) ) ) ), [0:725, 0:668] ) [213:469, 157:412], [0:255, 0:255] ) ) ), "png", "{\"colorMap\":{\"type\":\"intervals\",\"colorTable\":{\"0\" ...
It is hard to know from which petascope request received from client this rasql query was generated.
So it should be changed to add the information about the request id to petascope like below:
Executing rasql query rasql-2639 from req-57434 with user unauthenticated
In case the query is not generated from client request, but by petascope internally, then petascope log as below:
Executing rasql query rasql-2639 from internal with user rasadmin
Note:
See TracTickets
for help on using tickets.
