developer-delphi-horse-exception-logger

Log Horse pipeline exceptions to disk or console with configurable format variables.

Updated Jan 6, 2026
One-click install
npx skills add https://github.com/cslsoftwares/ParamentersORM --skill developer-delphi-horse-exception-logger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: developer-delphi-horse-exception-logger
Source: https://github.com/cslsoftwares/ParamentersORM/tree/main/.cursor/skills/developer-delphi-horse-exception-logger_V1.0.0
Command: npx skills add https://github.com/cslsoftwares/ParamentersORM --skill developer-delphi-horse-exception-logger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Middleware that logs exceptions from the Horse pipeline to disk or console with a configurable format for auditing.

Core Features & Use Cases

  • Factory-based THorseExceptionLogger.New and THorseExceptionLogger.New(format, dir) for default and custom formatting.
  • Format variables: ${time}, ${request_clientip}, ${request_method}, ${request_path_info}, ${request_version}, ${response_status}, ${exception}.
  • Pipeline position: should be used after HandleException to capture unhandled errors and persist them for auditing.
  • Scope: Delphi THorse HTTP services that require auditable error logs and reproducible incident records.

Quick Start

Integrate THorseExceptionLogger in your THorse app to start logging exceptions.

Frequently Asked Questions about developer-delphi-horse-exception-logger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I log exceptions in a Delphi Horse HTTP service for auditing?

To log exceptions in a Delphi Horse HTTP service for auditing, use middleware that captures unhandled errors from the pipeline and records details like client IP, method, path, and status to disk or console with a configurable format.

What format variables can I use to customize Horse exception logging?

Horse exception logging supports format variables including ${time}, ${request_clientip}, ${request_method}, ${request_path_info}, ${request_version}, ${response_status}, and ${exception} for customizing auditable log line output.

Where should I place exception logging middleware in the Horse pipeline?

Exception logging middleware should be placed after HandleException in the Horse pipeline to accurately capture unhandled HTTP errors and persist them for reproducible incident auditing.

Can I configure a custom log directory for Horse exception logs?

Yes, you can configure a custom log directory for Horse exception logs by instantiating the logger with a specific format string and directory path parameter during setup.

What is the best way to capture HTTP client IP and request path in Delphi Horse error logs?

The best way to capture HTTP client IP and request path in Delphi Horse error logs is using auditable exception logging middleware that formats these request variables directly into disk or console output.