-
Notifications
You must be signed in to change notification settings - Fork 238
Conversation
This reverts commit ddd8e9a.
deploy staging |
737c712
to
f543b70
Compare
deploy staging |
@@ -206,6 +216,11 @@ export class MetaTransactionService { | |||
) | |||
.callAsync(); | |||
|
|||
// log quote report and associate with txn hash if this is an RFQT firm quote |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this mean we don't get a report if the meta TX didn't consider an RFQT quote?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
right now all meta-txn calls are RFQT enabled b/c they all come from matcha.
for non-meta-txn calls I do limit it only to RFQT firm quotes (
0x-api/src/handlers/swap_handlers.ts
Line 67 in ba495a7
if (quote.quoteReport && params.rfqt && params.rfqt.intentOnFilling) { |
if we find this data useful for firm quotes we can consider opening up to all requests (as long as get confirmation from Oskar that our log serve can handle it)
deploy staging |
deploy staging |
# [1.15.0](v1.14.0...v1.15.0) (2020-08-17) ### Bug Fixes * added new asset swapper ([#316](#316)) ([029a58a](029a58a)) * excluded sources test ([#322](#322)) ([1327261](1327261)) * lower db pool connections ([#318](#318)) ([d9cb04d](d9cb04d)) * lower db pool connections ([#319](#319)) ([bc9f218](bc9f218)) ### Features * Log QuoteReport to Kibana ([#298](#298)) ([7bd6d4d](7bd6d4d))
🎉 This PR is included in version 1.15.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Logs QuoteReports for RFQT firm quotes so that they can be consumed by Kibana and later put into metabase.
When a firm quote is to be submitted by the taker, it is logged with a
uniqueIdString
to be associated with the random number + timestamp when the fill occurs on chain (See #281)This does not work for meta txns, because the additional calldata is generated as the time that the meta txn service submits the fill on-chain, which is a different request than when the 'order salad' was created. In that case, we log the
zeroExTransactionHash
so we can associate it in metabase.Also, we log the sources in "chunks", as outputting the entire object was too big to be parsed
TODO
apiKey
check prior to logging back for meta_txnDescription
Testing Instructions
Checklist
[WIP]
if necessary.