Skip to content

Welcome to

What is is a new monitoring platform that makes it easier than ever for anyone that writes code to make monitoring part of their development process. helps you and your team take ownership of monitoring.

How does it work? can monitor almost anything you can think of with just a few simple concepts.

Quick introduction

With you can send data by using one of our integrations, or straight to our API.

Apache Airflow Integration

Hawkflow Airflow integration gives you access to all Hawkflow monitoring features by simply adding a single line of code to any of your Airflow DAGs. Check out the repository for detailed instructions here GitHub Repository for hawkflow-airflow.

Hawkflow API

Our API has three different end points using one of our pre-built packages, or by sending data straight to our API by coding it yourself.

  • Timed API: Here you either send a start and end message, or use a decorator to time any part of your code.
  • Metrics API: Here you send key value pairs to record any numerical value. This can be anything you can think of, from model accuracy to number of rows in a database table.
  • Exceptions: Here you can send any exceptions and their content.

The Timed and Metrics end points will automatically analyse your data and let you know all kinds of interesting and important information about your code. Trends, anomalies, changes in time, and much more.

Code examples on GitHub

Take a look at our hawkflow code examples repo.

Detailed development guide

Check out our detailed development guide here.

Hawkflow Time monitoring:

You can time anything you can think of, have all the charts and stats at your fingertips, and then be alerted if anything out of the ordinary is happening. Two great early warning signs that there is a problem in the code:

  • A piece of code is running slower or faster than it normally does.
  • Code that runs on a schedule has stopped running

Whether you would like to time the training of a Machine Learning model, steps of an ETL process, or know if a scheduled program has run, is the fastest way to get answers and start understanding parts of your code like never before. With time monitoring, you can monitor cron jobs, heartbeats, user activity, ETls, long-running processes, database queries, basically anything you can think of, and you have complete control over what you send in to the system, so you'll never get overloaded with useless information.

Hawkflow Metric monitoring:

With Metric monitoring, Hawkflow allows you to send any numerical value as a key value pair. Just like with time monitoring, you'll have all the charts and stats at your fingertips, and then be alerted if anything out of the ordinary is happening.

You can track number of rows being inserted in to a database, machine learning models accuracy, model drift, number of users, you are really only limited here by your creativity.

Hawkflow Exception monitoring:

To tie it all together, also allows you to send exceptions through to our API.

Each API offers a wealth of value and insights, but when you combine all three APIs, Time, Metrics, and Exceptions, you can gain visibility over your entire codebase and architecture in a quick, easy to implement, cost-effective way. Making this part of your development process means you will never have unmonitored code again. was designed to work with very low effort and training.

Check out our development guide to see how to do this.

Why does exist?

There are many great monitoring platforms already in the market so why create another one?

Existing platforms offer great features, and is not designed to completely replace them. In fact, compliments a lot of these monitoring platforms very well.

Do you recognise any of these challenges in your own code or team?

  • The monitoring you have in place raises too many alerts, so everyone ignores them?
  • Your team releases new code without any monitoring?
  • There are too many places you have to check to know that everything is ok?
  • The one person that put monitoring in place has left your team?
  • The best monitoring solutions are too expensive for you system?
  • You need a DevOps team to create and use your monitoring?

Monitor First Development

With you can make monitoring part of your development process. Just like writing tests, going through QA, or writing clean code, adopting a Monitoring First approach to development means that you can ensure all your business and other valuable logic is monitored, not only from the moment you release your code in to production, but also during the development process itself.

The creators of set out to build something that gave a lot of value to anyone that writes code, but required no training to use and no permissions to install or use.

When to use

The simple answer, whenever you are writing code.

Where to start? is extremely simple to use, check out our development guide here.