Libraries tagged by error level

Rollbar Integration for SilverStripe. Rollbar automates error monitoring and triaging, so developers can fix errors that matter within minutes, and build software quickly and painlessly. See rollbar.com for more information.

Go to Download

Telebugs Laravel is an integration for Laravel applications with Telebugs (https://telebugs.com). Telebugs is a simple error monitoring tool for developers. With Telebugs, you can track production errors in real-time and report them to Telegram.

Go to Download

Telebugs for PHP is an error reporting library for Telebugs (https://telebugs.com/), a simple error monitoring tool for developers. With Telebugs, you can track production errors in real-time and report them to Telegram.

Go to Download

Provides A Powerful Error Response System For Both Development And Production

Go to Download

BC Error Pages Bundle for Symfony 3. Provides a basic solution to override the default Symfony error pages template code and styles with designer friendly alternatives. Great for developers seeking to override default error pages in Symfony.

Go to Download

Advanced API error handling for Laravel with multiple format support, smart debugging, and developer-friendly features

Go to Download

Adds an error copy button to Laravel 500 pages. Clipboard + VS Code integration for AI-assisted debugging.

Go to Download

A modern, comprehensive PHP SDK for the Facebook Graph API with enhanced error handling, pagination support, rate limiting, and extensive API coverage.

Go to Download

Allows developers to handle the results in any way they choose.

Go to Download

The Cartwryte Sleuth: a reactive error handler that investigates issues and provides clues for OpenCart development.

Go to Download

A modern, extensible PHP library for validating primitive data types, files, nested objects, and arrays of objects with reusable and centralized validation rules.

Go to Download

This module provides a toolbar for your project's development to easily fetch memory usage information, tail of Apache's access and error logs as well as phpinfo(), all from their own tab in the toolbar.

Go to Download

A powerful, lightweight debugging and profiling tool for PHP applications.

Go to Download

Real-time log streaming dashboard for Laravel. Monitor requests, errors, external APIs, jobs, and scheduled tasks with zero configuration.

Go to Download

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.41) is used. For example, calling `/info` is the same as calling `/v1.41/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download