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

Parallel Branches in Neuron AI Workflow

One of the things I didn’t expect when I started building Neuron AI was how much the design of the framework would be shaped by the people using it. I started this project to solve my own problems: I wanted PHP developers to have a clean, idiomatic way to integrate AI into their applications without

How to Stop a Streamed AI Response Mid-Flight in Neuron AI v3

One thing I didn’t anticipate when building Neuron AI was how many edge cases would surface not from the AI integration itself, but from the UI layer sitting on top of it. Developers don’t just want agents that work. They want agents that feel right to use. And the moment you start building chat interfaces

Conversational Data Collection: Introducing AIForm

One of the more interesting things about building an open-source framework is that the community often knows what to build next before you do. When I started Neuron AI, I had a fairly clear picture in my head of the core primitives: agents, tools, workflows, structured output. What I didn’t fully anticipate was how quickly