Real-Time monitoring Webhooks

Valerio Barbera

Hi, I’m Valerio, software engineer from Italy, 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 have officially released.

What is a Webhook?

In general, a webhook is a way for an app developer to specify a URI to receive notifications based on some trigger. In the case of Inspector, notifications get sent to your webhook URI every time an error is detected inside your application or when a new transaction happen.

The payload of the webhook is the item details, so your app can respond accordingly when a new transaction or exception is detected in your application.

Why would you use such a thing?

In talking to our customers we discovered a bunch of different scenarios where a delivery webhook would be really useful. The most common use cases we heard about include:

  • Feed delivery events into a variety of internal systems to trigger additional actions on your end (such as update user information in your CRM).
  • Provide delivery events directly to your customers through a custom UI to cut down on complaints/queries about the report of certain issues.
  • Automatically create a ticket in your internal ticket system.

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

New to Inspector?

Are you looking for a “code-driven” monitoring tool instead of having to install things at the server level?

Get a monitoring environment specifically designed for software developers avoiding any server or infrastructure configuration.

Thanks to Inspector, you will never have the need to install things at the server level or make complex configuration in your cloud infrastructure to monitor your application in real-time.

Inspector works with a lightweight software library that you can install in your application like any other dependencies. In case of Laravel for example you can install our official Laravel package. Developers are not always comfortable installing and configuring software at the server level, because these installations are often managed by external teams, and they are out of the software development lifecycle.

Visit our website for more details: https://inspector.dev/laravel/

Related Posts

How to prevent users from registering into your app with insecure passwords

Hi, I’m Valerio, software engineer and CTO at Inspector. About one year ago one of our accounts on an external platform has been hacked. Our credit card was attached to this account so we had to warn the bank to block it. Fortunately, there were no consequences, neither for our bank account, nor for our

Is it better to BUILD an internal monitoring environment, or BUY a prepackaged solution?

“Build vs Buy” Bake-off: Which should you choose? Every case is different, and all of these factors should be considered carefully before making a decision. There are situations where building a solution makes sense, either because you have the time, your requirements aren’t very complex, or if your applications simply don’t have enough load to

How to extend Laravel with driver-based services

Hi, I’m Valerio, software engineer and CTO at Inspector. In this article I talk about a Laravel internal feature not mentioned in the official documentation called “Driver Manager”. It can completely change the way you design and develop your application solving critical architectural bottlenecks, allowing you to build large systems built around decoupled, independent and