A few thoughts:<p>1) It would be clearer what this was if you linked to the SaaS page rather than the client libraries on Github. Or even put in the readme that these are just client libraries for the SaaS app.<p>2) For the Django code, if you converted that to generic wsgi middleware, it would work with most Python frameworks. If you also created asgi middleware, it would also work with the newer async frameworks (including DJango 3.1). You could also keep the framework specific middleware for ease of integration for those who want, but the generic middleware would be a basic framework agnostic option.
Nice work building something!<p>It seems the node stuff only works with express? There are lots of other server frameworks and libraries in the node ecosystem.<p>The way you configure the token needs some work, too. It really should be passed in in the client code instead of having people edit your library.<p>You may want to give clients a way to redact or suppress stuff in case they don't want to send any sensitive URLs over.<p>Have you done any benchmarks to see what sort of load this puts on a client app?
Would be nice to see a little more about the company & people behind this. I'm actually in the market for app monitoring for both node and django apps thanks to an awful experience with New Relic salespeople.