Ingesting usage when customer and subscription are not created
complete
T
Titouan BENOIT
Hey Lago team, one feedback about sending Event against billable metrics when we don't have created customer and subscription. The API return an error that there is no customer or subscription but I think it should not and should ingest the event since if we create the customer and the subscription with the correct external_id the event will be attached as usage.
We have two use-cases to be able to ingest events without the customer and subscription is created:
- On the first time integration (now), we are waiting for the quarterly billing interval, so we cannot create plan an subscription but we have roll out on production the integration, so far we create consumption on our side and we will need to resync all customers when everything will be setup. I would have love to begin sending events to Lago and check the event logs and after that I let the Ops team configure the plan, customer and subscription when it's the right time for them.
- On the run, we have a flag plan (trial, customer) on our workspace and when you set to customer it will begin to send events to Lago. If the sales puts the workspace un customer before the customer and subscription is created it will begin to send events and we will have errors. In this scenario, the tech team will need to launch a resync that is not ideal and not a good use of the tech team time IMO. Also these identified patterns has forced us to create some devtools to handle those cases and maybe we could have saved some times on the integration if the ingester was more flexible.
Lago admin
complete
M
Mathieu Déjean
Feedback from another user:
"The usage comes from S3 notification events sent to an SQS queue, and we're not logging those long-term, so it's currently not possible to replay events, and even if it were, it would be manual and difficult.
Is it possible for Lago to relax that restriction? E.g. if an event comes in with a new customer ID, create the customer for us, and if we don't fully configure the customer by the end of the billing period, then don't bill them, and that's our problem. Then we wouldn't need to ensure that customer creation happens before events are sent.
To ensure that, I think we would have to funnel all our Lago requests through one program using a message queue, and if any request fails, we would have to halt processing the messages, and either fix the message data, or wait for the Lago service to come back up."