ApplicationDiagnostics class - jetleaf_core library

High-level diagnostics orchestrator combining both:

1. Exception diagnoser discovery
2. Exception diagnosis reporting

This class acts as the central diagnostics engine of an application. It automatically:

Discovers all available ExceptionDiagnosers
Discovers all available ExceptionDiagnosisReporters
Delegates exception analysis to diagnosers
Forwards the resulting ExceptionDiagnosis to all reporters

ApplicationDiagnostics is therefore the runtime component responsible for transforming raw exceptions into structured diagnostics and ensuring the results are delivered to all registered reporting mechanisms.

🔧 Construction

On instantiation, the constructor immediately:

Calls super.getDiagnosers() to load diagnosers discovered via reflection
Calls super.getReporters() to load reporting sinks

This makes the diagnostics pipeline fully operational with zero manual setup.

🔍 Diagnosis Flow

The pipeline operates as follows:

An exception is sent to reportException
Internally, diagnose iterates through all diagnosers
The first diagnoser that returns a non-null ExceptionDiagnosis wins
The diagnosis is then forwarded to all reporters via report()

If:

No diagnoser recognizes the exception, or
No reporters are available

…then the exception is considered unhandled by the diagnostics system and false is returned.

All internal errors are safely swallowed so that a faulty diagnoser or reporter cannot break the diagnostics pipeline.

Example

final diagnostics = ApplicationDiagnostics(context);

try {
  throw InvalidConfigurationException("Missing file");
} catch (e) {
  diagnostics.reportException(e);
}

This will automatically:

Find a diagnoser capable of interpreting InvalidConfigurationException
Generate a structured diagnosis
Forward it to all registered reporters (file logs, telemetry, console, etc.)

ApplicationDiagnostics class final

🔧 Construction

🔍 Diagnosis Flow

Example

Constructors

Properties

Methods

Operators

jetleaf_core library