-
En exception opstår i Laravel-applikationen.
-
Laravel’s exception-system (via ExceptionHandler/Exceptions facade) kalder det reportable callback, som facaden (Facades\LaravelExceptionAnalyzer) har registreret i handles().
-
Facaden tjekker i config('laravel-exception-analyzer'), om analysen er slået til (isEnabled).
-
Hvis den er slået fra → der sker ikke mere.
-
Hvis den er slået til → facaden resolver LaravelExceptionAnalyzer-servicen fra containeren og kalder $analyzer->report($exception).
-
LaravelExceptionAnalyzer er hovedservicen. Den har en injiceret ReportClient og delegere arbejdet videre til den via report($exception).
-
ReportClient har en injiceret AiClient. I ReportClient::report():
- kalder den $this->aiClient->classify($exception).
- AiClient:
-
læser AI-config (enabled, api_key, endpoint, timeout)
-
hvis AI er deaktiveret eller config mangler → returnerer null
-
ellers saniterer den exceptionen via ExceptionSanitizer::sanitize()
-
sender den saniterede payload til AI-service via Http::post()
-
hvis AI svarer succesfuldt med JSON, mapper den svaret til et AiClassificationResult-objekt
- ReportClient får AiClassificationResult tilbage (eller null ved fejl).
-
Hvis resultatet findes, kan det logges eller gemmes i databasen.
-
I vores nuværende kode logges resultatet (eller er klar til at blive gemt, når DB-delen er klar).
- På den måde bliver hver exception automatisk klassificeret mht.:
category
source
severity
status_message
This is where your description should go. Limit it to a paragraph or two. Consider adding a small example.
We invest a lot of resources into creating best in class open source packages. You can support us by buying one of our paid products.
We highly appreciate you sending us a postcard from your hometown, mentioning which of our package(s) you are using. You'll find our address on our contact page. We publish all received postcards on our virtual postcard wall.
You can install the package via composer:
composer require 150657373-nikolajve/laravel-exception-analyzerYou can publish and run the migrations with:
php artisan vendor:publish --tag="laravel-exception-analyzer-migrations"
php artisan migrateYou can publish the config file with:
php artisan vendor:publish --tag="laravel-exception-analyzer-config"This is the contents of the published config file:
return [
];Optionally, you can publish the views using
php artisan vendor:publish --tag="laravel-exception-analyzer-views"$laravelExceptionAnalyzer = new NikolajVE\LaravelExceptionAnalyzer();
echo $laravelExceptionAnalyzer->echoPhrase('Hello, NikolajVE!');composer testPlease see CHANGELOG for more information on what has changed recently.
Please see CONTRIBUTING for details.
Please review our security policy on how to report security vulnerabilities.
The MIT License (MIT). Please see License File for more information.
