Often times developers are proud of their newly created, shiny and beautiful APIs. But what if they don't have the resources to analyze the real-life usage of their software? How will they ever be aware of bottlenecks and other problems in their API if they don's set up proper monitoring?
The issue with monitoring is however, that it is often not trivial to set up, as it might require you to build completely new infrastructure or modify your existing one or even implement your monitoring from scratch.
The other important aspect is pricing. The big players on the monitoring field are not cheap. You might be fine starting with some of the most common solutions out there, like DataDog or New Relic.
As your API usage grows however, you will notice that your monitoring costs will increase significantly with the traditional solutions. This is where you might consider either changing your vendor or building your own solution.
See full example on how to implement an API analytics solution for your API at: https://www.apilytics.io/blog/problem-with-api-monitoring
Top comments (0)