Download the PHP
package vortos/vortos-logger without Composer
On this page you can find all versions of the php package
vortos/vortos-logger. It is possible to download/install
these versions without Composer. Possible dependencies are resolved
automatically.
Vendor vortos Package vortos-logger Short Description Vortos logger — Monolog PSR-3 integration License
MIT
FAQ
After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.
Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.
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 PHP packages are not free to download and because of that hosted in private repositories.
In this case some credentials are needed to access such packages.
Please use the auth.json textarea to insert credentials, if a package is coming from a private repository.
You can look here for more information.
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.
The logger module provides PSR-3/Monolog logging with secure production defaults and explicit enterprise controls.
Defaults
app, http, cqrs, messaging, cache, security, and query channels are registered.
Production logs are JSON records on stderr.
Development logs use local rotating files.
Log buffering is enabled and flushed at HTTP terminate, console terminate, and console error events.
Trace correlation is enabled when the tracing module is present.
Sensitive keys are redacted from context and extra.
Structured fields are attached: service.name, service.version, deployment.environment, event.dataset, and log.logger.
Request context is bounded to method, path, client address, user agent, tenant id, and user id.
Introspection is enabled only in dev; it is disabled outside dev to avoid source path leakage and extra stack work.
Configuration
Redaction
Redaction is enabled by default for common auth and PII keys such as password, token, authorization, api_key, email, phone, and ssn.
Add domain-specific keys with redaction(true, keys: [...]). Redaction is recursive with a bounded depth, so large or cyclic payloads do not create unbounded work.
Do not log request bodies, full headers, payment data, access tokens, refresh tokens, or raw identity provider payloads. Prefer stable ids and event names.
Alert Sinks
Sentry is supported as an error sink. If Sentry is configured but sentry/sentry is not installed, container compilation fails by default. This prevents a production deployment that appears configured but silently drops incidents.
Slack and email handlers are synchronous emergency sinks. Keep their minimum level high, such as Critical, and use Sentry, OpenTelemetry logs, or centralized log aggregation for primary production alerting.
Set failOnMissingIntegrations(false) only in local prototypes.
Composer command for our command line client (download client)This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free.Standard composer command
The package vortos/vortos-logger contains the following files
Loading the files please wait ...
Loading please wait ...
Before you can download the PHP files, the dependencies should be resolved. This can take some minutes. Please be patient.
