Download the PHP package lane4hub/logger without Composer
On this page you can find all versions of the php package lane4hub/logger. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download lane4hub/logger
More information about lane4hub/logger
Files in lane4hub/logger
Package logger
Short Description Jardis logger is a very powerful and flexible PHP logging library that allows you to log data in various formats and send it to different destinations such as files, databases, emails, or external services.
License MIT
Homepage https://github.com/lane4hub/logger
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package logger
Jardis Logger
Jardis Logger is a PSR-3 extended flexible and customizable logging system for PHP, ideal for context-based logging – such as in Domain-Driven Design (DDD) – and seamless integration into your projects.
Logger is a highly powerful and flexible PHP library that supports the logging of messages in a context-based system.
Datalog structures can be customized freely, logging handlers and specific formatters can be added to tailor and format log messages individually.
Features
- Logging Levels: Supports all common levels (Debug, Info, Notice, Warning, Error, Critical, Alert, Emergency).
- Context-Based Logging: Each logger instance can be created with a specific context, enabling clearly structured log output – ideal for modeling in Domain-Driven Design systems.
- Customizable Logging Handlers: Use
LogCommandInterfacefor your own implementations to adapt the logging logic to your needs. - Customizable Log Record Format: Extend the columns for log output per LogLevel as needed.
- Customizable Log User Format: Extend user data output in logs per LogLevel as required.
- Formatter for Output: Use the provided formatters, extend them, or create your own formatter.
- Log History: Retrieve a limited number of log histories per log level as needed.
Available Logger Commands
- LogConsole
- LogFile
- LogDatabase
- LogRedis
- LogErrorLog
- LogSysLog
- LogSlack
- LogStash
- LogNull
- ... extendable as per your requirements!
Available Log Data Formats
- LogData Record
- context (default)
- loglevel (default)
- message (default)
- data (default)
These columns can be expanded as desired. Log extensions, scalar types, arrays, or callables can be used for population.
For logging into an RDBMS, the columns must be appropriately created.
Available Extensions for Expanding Log Information
- LogDateTime
- LogClientIp
- LogMemoryUsage
- LogMemoryPeak
- LogUuid
- LogWebRequest
- ... extendable as per your requirements!
These log extensions can also be used to populate the default data field.
Available Logger Output Formats
- LogLineFormat
- LogJsonFormat
- LogHumanFormat
- ... extendable as per your requirements!
Using the Jardis Logger
Example Code to Create a Logger with Two Log Commands
A logger requires an explicit context (e.g., the name of a specific domain, component, or application) and at least one handler that processes the log messages.
Example Code for Using the Logger
Example Code for Expanding Data Output
Formatters serve to format log messages differently before output. For example, logs can be output in JSON format.
By default, the LogLineFormat is used.
Example Code for Expanding User Data in Logs
In this example, data is added to the data field in the log record.
Example Code for Expanding Log Record Data Columns
In this example, data is added as a new column in the log record.
If you want to use LogDatabase, you must first create the corresponding table in your database.
You can optionally rename the predefined table and/or add additional fields.
Example Code for Using LogDatabase with Default Structure
Quickstart with Composer
Install the package via Composer:
Quickstart GitHub
License
This project is licensed under the MIT License. See the license file for more details.
Jardis Framework
This tool is part of the development of our Domain-Driven Design framework Jardis (Just a reliable domain integration system).
Jardis consists of a collection of highly professional PHP software packages developed specifically for efficiently and sustainably solving complex business applications.
Our development is based on defined standards such as DDD and PSR, with the goal of delivering the highest possible quality of functional and non-functional requirements.
To ensure technical quality, we use PhpStan Level 8, PhpCS, and achieve full test coverage with PhpUnit.
Our software packages meet the following quality attributes:
- Analyzability
- Adaptability
- Expandability
- Modularity
- Maintainability
- Testability
- Scalability
- High performance
Enjoy using it!
All versions of logger with dependencies
psr/container Version ^2.0
psr/log Version ^1.1
ext-json Version *
ext-pdo Version *
ext-redis Version *
lane4hub/dotenv Version 1.0.0