Forem: Markus Blomqvist

Flask open source monitoring middleware

Markus Blomqvist — Mon, 28 Mar 2022 10:09:33 +0000

Apilytics is an easy-to-install zero configuration monitoring solution for Flask backends. Set up in five minutes and instantly access all of your most important application metrics.

Learn more at https://www.apilytics.io/for/flask

Application monitoring for serverless applications

Markus Blomqvist — Thu, 10 Mar 2022 12:01:45 +0000

Apilytics is the tool you've been waiting for to montor your applications running in serverless environments. Our way of logging the application metrics directly from an API middleware makes it a perfect solution for any serverless application.

Monitor individual functions

With Apilytics you have the freedom to monitor individual serverless functions or you can set up a broader middleware that monitors all of your functions.

Works with every cloud provider

You can be sure that Apilytics works in every serverless environment so you will never face a vendor-lock situation.

Combine with other APIs

If your application is consisting of multiple APIs, some of which might be running in serverless environments, you can simply use the same API key to monitor them and you will see metrics from them as separate endpoints in the same dashboard.

Check out our live demo at: apilytics.io

Monitoring dynamic API routes

Markus Blomqvist — Fri, 28 Jan 2022 07:39:37 +0000

When it comes to monitoring endpoint specific data from your applications, your data can easily become noisy as the amount of your endpoints gets bigger. This is no longer the case with Apilytics as we are rolling out our support for dynamic API routes! Read our announcement about this major new feature at: https://www.apilytics.io/blog/monitoring-dynamic-api-routes

The Problem With API Monitoring

Markus Blomqvist — Sun, 16 Jan 2022 23:03:17 +0000

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