[FEAT]: add Event show API endpoint about lago HOT 4 CLOSED

Hey @prognostikos,

We recently introduced two features to improve confidence in event ingestion:

• The event debugger
• event.error webhook for failed events: getlago/lago-api#252

But we are aware that it does not guaranty that all events will be processed in case of Redis outage or misconfiguration.

Having a webhook for event.created would certainly fix the problem but at the cost of many webhooks sent back to the source.
So it would also probably require a way to be able to chose which webhooks an application wants to receive before enabling it.

We also discussed about adding an API endpoint to download the logs of all received events. It would allow an easy reconciliation between an app and Lago. Would it be an acceptable option for you?

For now, we do not have action on our short term roadmap to tackle this but we are marking it as a feature request.
Also we would be happy to discuss about how it could be implemented.

Cheers

from lago.

Thanks @vincent-pochet the debugger looks useful.

I understand that not everyone would want to get the event.created webhook and right now it's not possible to configure which events are sent to a webhook endpoint nor to have multiple endpoints.

For us an API endpoint where we can GET on say transaction_id would work. We would probably just setup a job in our system to confirm each ingested event in 60 seconds or something like that.

Getting logs of all received events would also be useful, but may require a bit more work on the caller end.

We will need some way to confirm event creation, so we are happy to do the work on the API and ruby client for this. Adding an endpoint to GET an event by transaction_id seems pretty straightforward. If you'd prefer an endpoint to download logs maybe you could start by describing what parameters it should take and what the response should look like and we can take it from there?

from lago.

Thanks @prognostikos for your contribution proposal.

I agree that a GET /api/v1/events/:transaction_id looks like a simple solution for your need.
Let me discuss it with the product and tech teams and I will get back to you today.

from lago.

After discussing internally, we think that adding a new API route is the easiest way to move forward with it for now.

We will probably improve the webhook side in the future, but not in the short term.

If you want to take care of this dev, we would be pleased to review and merge it in the main branch for future release 🚀

from lago.