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.

Our agent now supports:

• Python 2.7. Check out the compatibility matrix for further details.
• httpcore client
• twisted client

Brand new features:

• request /response body shape hashes feature (helps our detection engine)
• request/response body size filters (new anomaly feature)
• request/response body data filters (new anomaly feature))
• Duration filter (new anomaly feature)

We just released new versions of our Node and Ruby agents with new features!

• Node and Ruby agents are now in version 3.2

Common changes are:

• request /response body shape hashes feature (helps our detection engine)
• request/response body size filters (new anomaly feature)
• request/response body data filters (new anomaly feature))
• Duration filter (new anomaly feature)

Ruby specific change:

• NOT filter implemented to enable new filtering option in the dashboard. (other agents already support it)

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!

New Dashboard

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.

Introducing our rebuilt logging feature: Log Collections

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:

• The built-in collections are dedicated to logs captured by Anomaly and Remediation rules.
• Custom log collections, defined by your own needs.

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.

Enhanced Anomalies & Remediations

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.

New Built-In Rules

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.

New Environments settings

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.

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!

• Anomalies now have a Severity level attached. Edit the rules to customize it.
• We group them and count out their occurrences for better readability.
• Bearer-provided anomalies have a “paternity” system, allowing Bearer’s team to update their behavior as long as you are not customizing them. -In the future, we will add more new anomaly templates!

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!

Check out the feature's full documentation.

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:

• Enable notifications in a click from rule configuration dashboards
• Set up notifications once for each application: you no longer need to reconfigure them for each rule.

• Choose any email or email-list configuration you like to receive our notifications.
• Continue to configure slack integration in a minute!
• Feature-flip your App with the webhook notification.

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.

We have released the very first piece of a feature we call “Fleet control”. It allows you to instantly see the version and location of all your deployed Bearer Agents.

This cool new feature is available in the “Agents” tab of your application’s settings.

Hostname detection is not available with agent version 3.0, but it will be available for everyone in our agent's version 3.1 release, coming for mid-may!

Next on our roadmap: receive notifications when agents are down in your environments.

Until now, Bearer offered 3 fixed environments per application: Production, Staging, and Development. We have released a brand new method of environment management that is scalable, configurable, and dynamic!

• There is now only one authentication key per Application
• Auto-detection of env_variables.
• Newly detected environments are created automatically.
• By default, every new environment is active. You can change this to “disabled” by default in the settings.
• Each environment can be activated or deactivated from the dashboard. It will disable all the agents that are associated with that environment.

To enjoy this new feature, you need to have at least Agent V3.0.0 and to update your agent's configuration. Legacy configuration and authentication keys are still valid. Migrate when you wish!

Check out our documentation to find the new settings:

• Node agent's documentation
• Ruby agent's documentation

You can find the new configuration in the Application’s General settings.

Last but not least, there is a cool color picker. Choose the color scheme you fancy!