elasticSearchWarehouseV300 vs mappedmetric

Open sebtesobe opened this issue 8 years ago • 1 comments

It looks like no issue was opened here when discovered a few months ago (see https://github.com/OpenBankProject/OBP-API-Scripts/blob/master/obp_api_scripts/generate_stats/stats.py#L161) so i will do it now:

With the advent of function elasticSearchWarehouseV300, table mappedmetric can not give us information about the usage of the warehouse anymore. The parameters have moved from the URL to the POST payload which is not covered by mappedmetric. Is there another place in the database where the parameters can be retrieved from?

Nov 20 '17 11:11 sebtesobe

@simonredfern and i discussed yesterday that a new field es_uri_part could be added to table mappedmetric which would be populated with the value of es_uri_part when elasticSearchWarehouseV300 logs the call.

Not sure if adding a new field to mappedmetric for one individual call is a good idea, maybe it is a better idea to have a generic fieldname like extra or comment or note or data where other calls could store extra data in the future as well?

Nov 21 '17 10:11 sebtesobe