You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our logging isn't robust enough and I want to make sure any info we get from stripe is persisted. We get raw JSON from Stripe which I'd like to store somewhere, either in its own separate table or as part of the existing Stripe activity we record.
The text was updated successfully, but these errors were encountered:
@ardalis Looking at the StripeWebhookEndpoints, it looks like we are logging some basic information, is that what you are referring to when you say "as part of the existing Stripe activity we record"? We can easily log the json string but I don't know what service you are using to consume and store the logs. I know many of them will make it easy to read json data in their logs. If that's our case, I think I'd probably favor that approach instead of saving that data in our own DB.
What do you think? Any preference between logging it vs saving it in the DB?
I haven't been happy with our logging solution, which is comprised of:
App Insights
Console
Mainly, Application Insights hasn't been set up properly as far as I can tell, so I can't really get to any of our logs there. Which means I can only see information if I'm in the Azure portal, actively logged in and watching the application logs (and I've configured them to be captured - which expires after a few hours).
So, instead of logging the information to the database, we could set up a better logging solution overall that I could count on. But not having that, I would just store them in the database alongside the transaction info we are already storing.
Our logging isn't robust enough and I want to make sure any info we get from stripe is persisted. We get raw JSON from Stripe which I'd like to store somewhere, either in its own separate table or as part of the existing Stripe activity we record.
The text was updated successfully, but these errors were encountered: