-
Notifications
You must be signed in to change notification settings - Fork 164
312: Update API Transaction Count report #12733
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| fields @timestamp, @message, @log, id | ||
| | filter name = 'IdV: doc auth verify proofing results' | ||
| | fields jsonParse(@message) as message | ||
| | unnest message.properties.event_properties.proofing_results.context.stages.state_id into state_id |
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.
@koseni123 @shilenpatel1 for this, we should just need should_proof_state_id=true as the filter within this event property and something indicating that we got a response from AAMVA. success or failure at the event level doesnt matter.
| properties.event_properties.vendor_name as @vendor_name, | ||
| properties.event_properties.mva_exception as @exception, | ||
| properties.event_properties.success as success | ||
| | filter !@exception |
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.
@koseni123 @shilenpatel1 same comment as above, we dont need to filter out exceptions, but we do need to filter for aamva:state_id in the new event as that indicated whether an AAMVA transaction occurred at all
|
Superseded by #12790 |
🎫 Ticket
Link to the relevant ticket:
LG-312
🛠 Summary of changes
Added GPO, AAMVA and Phonerisk queries to report
📜 Testing Plan
Provide a checklist of steps to confirm the changes.