Download the PHP package t3n/flow-log without Composer
On this page you can find all versions of the php package t3n/flow-log. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Package flow-log
Short Description Small package that provides several Logger for the Flow Framework
License
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 flow-log
t3n.FlowLog
This package adds a few helper to log Flow Messages.
🔧 Still Work in Progress 🔧
ConsoleStorage
If you'd like to log your Exceptions to the console, for instance stderr or stdout, he ConsoleStorage is for you. It will log all throwables directly to the console as JSON. The JSON is formatted to be parsed by google Stackdriver.
To enable the ConsoleStorage you need to adjust your Settings.yaml like this:
The StreamName could either be stderr or stdout.
BigQueryLogger
The BigQueryLogger is an AbstractBackend so that you can use it like an normal Logger like FileBackend. If you want to log into BigQuery, here is your 3 Step manual:
- configure BigQuery (dataset, table, keyFile)
- create a
BigQueryLoggerviaPsrLoggerFactory - map your custom
BigQueryLoggerviaObjects.yamlto actually use it
1) Configure BigQueryLogger
ℹ️ All logs will be written into a partitioned table in BigQuery. This means that you have a "overall" table with multiple tables for each day. This day-tables can be deleted automatically via expirationMs. If you want to store your logs forever just ignore this Setting and let it blank.
2) Create your own Instance of BigQueryLogger
To actually use the BigQueryLogger you have to define your own in your Settings.yaml. The important part is loggerName ("applicationXyImportLogger") and the internal Name bigQueryLogger.
bigQueryLogger will be used in Step 3, loggerName is the actual name for the BigQueryTable (inserted for each row).
You can create as many loggers as you want. This is really usefull if you want to "split" your logs in your BigQueryTable. E.g. one Logger for Imports, one for User-Requests, etc.
3) Map your BigQueryLogger via Objects.yaml
Last but not least you have to define your Logging-Factory to use your BigQueryLogger.
Therefore edit your Objects.yaml like this:
Now you are able to use it:
ServiceContext
ℹ️ Important if you want to log multiple applications/environments (e.g.) in BigQuery.
You should also set the ServiceContext that is used by StackDriver and BigQueryLogger:
