Enhance filters on webhook transaction logs

[rochellelevy]

Is your feature request related to a problem? Please describe. When we receive queries from users, we rely on a quick efficient ways to query transaction logs so that we can respond to incidents raised to us. New Relic provides us with a really quick way to query our own logs, but thats only from the point we receive a message from ReapitApi. Today, I spent at least 45 minutes in the transaction logs looking for one appointment that was set up at 'roughly' 10.30. We're a small team and really pressed for time and spending time searching through logs isnt ideal and slows us down.

Describe the solution you'd like at the very least,

• A way to get the Reapit ID so that we can search for the event (we have no visibility of ReapitID's or property IDs)
• Filter the logs by Negotiator ID Even better:
• A way for us to load the logs into New Relic so we can query it

Describe alternatives you've considered I dont think there are any alternatives

Additional context Add any other context or screenshots about the feature request here.

Specification

• Project: Reapit.Services.Webhooks
• Add additional filters to GetLogsQuery():
  • EntityId -> converts to Payload.Contains
  • EventId -> converts to EventId.Equals
  • TopicId -> converts to TopicId.Equals
  • As per existing rules, applicationIds MUST be set to be able to use any of the additional filters (this is the current behaviour anyway)
  • Once backend updates are made, liaise with frontend team

[github-actions[bot]]

Thank you for raising a feature request. Feature requests will be prioritised in accordance with our roadmap, customer and developer priorities. This request will be reviewed in our weekly refinement sessions and assigned to a specific project board or column, depending on the nature of the request and the development work required. For more information on our processes, please click here

[RWilcox-Reapit]

Requires further investigation/discussion into querying this at a DB level. @plittlewood-rpt

[plittlewood-rpt]

Hi @rochellelevy - please see specification on the ticket above. The way to combat this looks likely to be to provide additional filters on that transactions page. The obvious ones are entity id/event id. Can you let me know your thoughts on the suggested implementation

[github-actions[bot]]

This issue has been updated and moved to our ‘Near Term’ column (typically completed within 1 - 4 months). We have assessed the effort required and outlined a technical specification - please take the time to review this detail. When we're ready to schedule the issue, it will be assigned to the relevant board where you can continue to track its progress to completion. For more information on our processes, please click here

[plittlewood-rpt]

Backend work has been released. Ticket logged for frontend to implement new filters