We have just released a new part of Bearer that we have been working on for a while: Endpoint detection and monitoring. You can now see more granular data about APIs with multiple endpoints through our dashboard’s graphs.
Just click on any API listed and you will get a detailed perspective on its endpoints statistics!
We are super excited to release our first beta versions of our Golang & PHP agents! Our panel of supported stacks is now complete. Go & PHP agents version 1.0 support all our monitoring and discovery features. Remediations are not available yet.
Compatibility :
Health status is a new feature of our dashboard V2, which provides at-a-glance insights into the reliability of your application’s integrations. We’ve updated it to give more granular feedback, represented by a letter score from A (great!) to F (something is very wrong).
Health score is calculated based on the anomalies we detect and their severity. The more severe an anomaly is, and the more calls that are impacted, the worse the health score is going to be.
Check out our documentation for more details about Health Score.
We just released a brand new version of our Python Agent, version 1.1.
We just released new versions of our Node and Ruby agents with new features!
Common changes are:
Ruby specific change:
It’s time for a major update to Bearer! Today, we are releasing a brand new Dashboard providing many requested API performance metrics, a rebuilt logging system, a new UI, many new default anomaly detection rules, and more!
Designed for better readability, ease of navigation, and packed with cool new features! We now present 4 top Key Performance Indicators (KPIs) that will give you instant insight into your app’s health, performance, and reliability. Select each one to see a detailed overview!
We created four brand-new sections: Health, Errors, Performance, and Requests. Each provides specific insights into your API behaviors, along with a detailed graph so you can dig deeper into each KPI.
Located in the Logs tab, collections are now the centerpiece of our logging capabilities and represent a reimagining of our logging approach. Find out more in our dedicated blog post here.
We have two kinds of collections:
Custom log collections are based on a dedicated filtering rule. They are a handy way to record all occurrences of a specific type of API call.
We have updated the interface to provide a clearer understanding of what each rule is matching, when they were last triggered, and convenient access to the logs generated by the rule.
We now provide a set of 10 Anomaly rules and 2 Remediation rules that are built-in as key elements of our product. They span the most common behaviors of API integrations.
You can now configure default settings at each environment's level to your liking.
We have changed the way APIs are automatically detected by Bearer so that they are now separated by subdomains. This will allow for domains with many different APIs (Amazon Webservices, Microsoft, …) to be monitored independently. The API’s name is derived from the Fully Qualified Domain Name (FQDN).
To make it easier for our users, we automatically associate a service tag for all APIs in the same root domain.
Bearer’s Python agent is available today in Beta and includes all the passive features of our Node.js & Ruby agents, which include monitoring, anomaly detection, and logging. Don’t worry remediations will come in a future release.
To start using the Python agent, create a new application, and configure it with its App key!
You can also check out our full Python agent’s documentation here.
We have split the rules configuration by which feature they take advantage of. You can now find Anomaly rules in the Anomaly section, and remediation rules in the Remediation section.
This provides a better configuration flow for Anomaly & Remediation rules. They are now truly turn-key and can allow you to:
We also rebuilt the Custom Rule forms: they are now specialized for Anomalies and Remediations. This will come in handy when you start debugging complex issues.
With this release, we are delivering a major change to Bearer. Our incidents feature has been overhauled and renamed “Anomaly Detection”. It allows for easier use of our rule system to identify what’s wrong in your app’s integrations. Of course, you can still be notified when an incident occurs, but now we can also do way more than that!
We have built the Anomaly feature around our Generic Rules system. We provide a set of starter rules that are enabled by default and already at work on your integrations!
