Take advantage of real-time notifications to automate application monitoring

Valerio Barbera

Hi, I’m Valerio software engineer, founder and CTO at Inspector.

In this post I would show you how notification channels work in Inspector. They are a powerfull tool for developers to save time and money with automatic bugs identification.

As notifications becomes increasingly central to the way our users stay informed about how their applications are performing, we have introduced Notification Channels in the monitoring dashboard.

In the beginning of my career I worked a lot with small businesses. This experiences showed me how hard it was for developers to avoid system crashes in their backend when the codebase gets bigger.

Small agencies have a strong connection with their customers and tend to deliver great software. But sometimes it gets harder to maintain the practices that made them successful as the team grow, or if the number of projects increase.

Software development is a time consuming job. Tools that speed up automation are really valuable in small and medium companies.

What are Notification Channels?

In a nutshell, Notification Channels are a new, unified way to organize and manage automatic messages sent through Inspector to you and your team members.

Notifications can be delivered not only via email as expected by default, but also via a variety of channels like Slack, Webhooks, SMS, and more.

Thanks to our integration you can connect your monitoring system with your favorite tools and create an automated and informed workplace.

How do Notification Channels works?

Notification Channels separate the notifications that Inspector sends into different routes. They allow users to have more control over the notifiction experience.

However, you will also have the option of activating multiple channels for the same application for different purposes. For instance, one channel for new error, another for every error occurrences, and a third for server side automation via webhooks.

Actually we support Email, Webhook, Slack, SMS, Pushover, PagerDuty, and more will be added in the future.

Why Were Notification Channels Created?

This move is very much in keeping with our ongoing focus to help developers to save time and money with automatic bugs identification.

Notification Channels can be a powerful way to reach developers with urgent messages about application status and availability. It can reduce the negative impact of software issues on application users.

Try Inspector for free and as long as you want

To let everyone interested try this new solution, Inspector offers a free tier with up to 30,000 monthly transactions. And it’s not a limited trial. So, you and your team can get familiar with Inspector without the pressure of a deadline.

Create your account

I hope you will try and enjoy the Inspector experience.

Join the “Scalable Applications” community

If you want to learn more about scaling up your application, join Scalable Applications. It’s an international community of professional developers sharing strategies and experiences for building scalable systems.

Join us now

Related Posts

Laravel Redis Throttle In Details: Tutorial

Redis Throttle is a fantastic feature provided by the Redis facade in the Laravel framework. It’s a convenient way to limit the rate at which certain actions can be performed. How Laravel Redis throttle works The throttle() method allows you to go through the following process:  What is an Atomic Lock in Redis An atomic

The Value Of Data: A Guide To Informed Decision-Making

What is the value of data? That is a huge question. I could go down so many different rabbit holes and make nuanced points about why data’s valuable. At a very high level the value of data is that it lowers your level of uncertainty when it comes time to make a decision or solve

Monitoring Agent: Elevate Your Observability With Inspector

The last fundamental concept to fully evaluate whether, and how, to invest in a monitoring stack is the type of monitoring agent. Very briefly, a monitoring system is always composed of two elements. The agent, which is a software package that you must install in your application or infrastructure. And the dashboard to view the