The way I have always done this is to write wrappers for all integrations, whether they are via SDK or direct HTTP calls to an API (they were generally called Clients like StripeClient). Each of these wrappers had a common purpose to abstract away the underlying integration (so if we wanted to switch Stripe out for another vendor, the changes were generally more self contained), but these wrappers also allowed us to capture telemetry about our integrations such as usage, versions, services they were called from.

Most of this telemetry either went to Datadog or Prometheus but we could also have them go to a central location that allowed us to build reports on usage and what all our integrations were.

Then we got all the tracking you mentioned for free whenever we implemented a new API. The initial lift was always a bit longer but very much worth it in the end

Hi, I thought I was alone in facing this problem.

I am working on an open source project to handle all third-party integrations pain, (OAuth2 including multi tenancy, Caching, Cors, Logging, Error Rates, Rate Limting).

Basically It will be dashboard where you can trace all logs, and SDK on frontend or backend to proxy the requests through it.

The next steps to work on tooling to mock APIs and test them.

This effort still in progress and will go out during next two weeks, the repository is incomplete. https://github.com/passr-dev/passr

Do you mind if i contact you to learn more from you and shape the project together? We have discord channel https://discord.gg/xaDV2Tuh4d