Skip to content

Conversation

@koseni123
Copy link
Contributor

🎫 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.

  • Step 1 - Run report in int env and confirm all queries run
  • Step 2 - Validate report results with dashboard
  • Step 3

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
Copy link
Contributor

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
Copy link
Contributor

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

@astrogeco
Copy link
Contributor

Superseded by #12790

@astrogeco astrogeco closed this Jan 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants