Real-Time application monitoring Webhooks

Valerio Barbera

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

Inspector’s integration capabilities just got significantly better in the last few months. We are delighted to announce that Inspector Webhooks has been officially released.

What is a Webhook?

In general, a webhook is a way for an application to deliver notifications to a specific URI based on some trigger. Inspector send notifications to your webhook URI every time an error is detected inside your application or when a new transaction happen.

The payload of the webhook will contains all the details to investigate the event. So, your application can respond accordingly when a new exception is detected.

Why would you use Webhook notification channels?

Talking with our customers we discovered a bunch of different scenarios where webhooks would be really useful. The most common use cases include:

  • Delivery events into a variety of internal systems to trigger additional actions on your end (such as update user information in your CRM);
  • Delivery events directly to your customers through a custom UI to cut down on complaints;
  • Automatically create a ticket in your internal ticket system.

To get started using webhooks in your application, check out the short video tutorial below and let us know if you have any feedback:

Application monitoring

If you found this post interesting and want to drastically change your developers’ life for the better, you can give Inspector a try.

Inspector is an easy to use Code Execution Monitoring tool that helps developers to identify bugs and bottlenecks in their application automatically. Before customers do.

screenshot inspector code monitoring timeline

It is completely code-driven. You won’t have to install anything at the server level or make complex configurations in your cloud infrastructure.

It works with a lightweight software library that you can install in your application like any other dependency. Check out the supported technologies in the GitHub organization.

Create an account, or visit the website for more information: https://inspector.dev

Related Posts

The Neuron Facade: Talking to Your AI Agent in Laravel

Before this release, using Neuron AI inside Laravel meant creating a dedicated agent class, extending Agent, implementing a provider() method, and wiring the system prompt yourself. That pattern is the right one once your agent has a personality, a set of tools, and a role in your application. But it is a lot of ceremony

LLM Provider Fallback in PHP: Automatic Failover in Neuron AI Router

When I published the first article about the Neuron AI Router, I expected questions about routing rules. Which rule to use for structured output, how to write a custom one, how the round robin behaves under load. Some of those questions arrived, but the most frequent one was different, and it wasn’t really about routing