Hi, I’m Valerio software engineer and CTO at Inspector.
As notifications becomes increasingly central to the way that our users stay informed about how their applications are performing, we have recently introduced Notification Channels.
My early work with small businesses showed me first-hand how hard it was for software agencies and developers to understand or avoid system crashes in their backend as they scaled — and how desperately the market needed a solution that was accessible to businesses of all sizes.
Small businesses and creators 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 with two or more developers, or if the number of projects increase.
Software development is a time consuming job, tools that can bring automation in our life 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 messages sent through Inspector to you and your team members.
How do Notification Channels works?
Channels separate the notifications that Inspector sends into different routes, allowing users to have more control over the messaging experience. They are created and named by each service that want to send notifications to users who are part of your organization.
However, you will also have the option of activating multiple channels for different purposes — for instance, one channel for new error detected, another for every error occurrences, and a third for server side automation.
Actually we support three channels (Email, Webhook, Slack), more will be added in the next months.
Why Were Notification Channels Created?
This move is very much in keeping with our ongoing focus to build an autonomous monitoring tool that can bring more free time in our users’ hands.
Notification Channels can be a powerful way to reach developers with urgent messages about application status and availability reducing the negative impact of software issues on application users.