Libraries tagged by Application Logging

Implement the logging of your application into the rouda.online dashboard.

Go to Download

A clean and simple Laravel 5 activity logger for logging website / application actions.

Go to Download

Log management package for logging all types of logs from Omni applications

Go to Download

Build a fully custom headless storefront - your own web app, mobile app, or POS - against a single OE Commerce store. Every endpoint below is namespaced under `/api/v1/store/...`. Building admin/back-office tooling instead? See [/docs/admin](/docs/admin). New here? [/guides/store](/guides/store) walks through getting a key, the anonymous cart session, and calling your first endpoints step by step - this page is the field-level reference to come back to afterward. ## Getting Started 1. Click the **Authorize** button at the top of this page. 2. Provide credentials: - **X-Commerce-Key** (always required) - your store's Store Access Key from Backoffice > Settings > Application APIs. `pk_store_...` (publishable) is safe for browser/mobile code; `sk_store_...` (secret) is server-to-server only and is rejected outright if a browser Origin header is present. - **Bearer** (only for endpoints acting on a specific customer - Account, Orders, Wishlists, etc.) - the token from **Auth > register** or **Auth > login**. Once authorized, you can explore and test all available endpoints directly from this interface. ## Anonymous Carts A guest cart is tracked by an `X-Session-Ref` header, not a cookie - the server generates one on your first request and echoes it back on every response after. Keep sending back whatever value you last received. Logging in carries that same cart forward onto the customer's account automatically, with no separate merge step. ## Errors Failures use RFC 9457 Problem Details (`application/problem+json`) with a stable `code` field for programmatic handling, e.g. `store_key_invalid`, `store_key_revoked`, `store_key_scope_denied`, `rate_limited`. A rejected *business* action (e.g. adding fewer than a product's minimum order quantity to the cart) instead comes back as HTTP 200 with `"success": false` and a human-readable `message` - always check `success` in the body, not just the HTTP status code. ## Rate Limits Requests are limited per Store Access Key (200/minute). The credential-stuffing surface (register/login/forgot-password/reset-password) is limited more tightly per caller IP (10 per 5 minutes). A 429 response includes a `Retry-After` header.

Go to Download

GDPR/DSGVO compliance toolkit for Laravel applications: consent, data export, erasure, legal hold, audit logging and package inventory.

Go to Download

Developer Tools aimed at debugging/profiling/logging actions that are executed within a standard Zend\Mvc application

Go to Download

PSR-3 application logging for Altair, backed by Monolog and wired from LOG_* env vars. JSON-lines to stderr by default.

Go to Download

Application Logging

Go to Download

A robust, flexible, and PSR-3 compliant logging component for the KaririCode Framework, providing comprehensive logging capabilities for PHP applications.

Go to Download

MongoDB-backed structured application logging for Laravel.

Go to Download

Provides logging for Laravel applications in Google Cloud Logging environment

Go to Download

A comprehensive logging library for Laravel applications.

Go to Download

Configurable PSR-3 logging setup and runtime logging integrations for PHP applications.

Go to Download

PSR-3 logging primitives for Annabel applications.

Go to Download

Robust logging library for every application.

Go to Download