=================================================
Setup
-----
Before using this logging handler, td-agent must be properly configured at the
localhost. Please confirm these settings are in your
/etc/td-agent/td-agent.conf.
## built-in TCP input
<source>
type tcp
</source>
# Treasure Data output
# match events whose tag is td.DATABASE.TABLE
<match td.*.*>
type tdlog
apikey YOUR_API_KEY
</match>
For more information, please look at the documentation.
* http://docs.treasure-data.com/
Install
-------
$ easy_install td-logger
or
$ pip install td-logger
Usage
-----
Check out the tests folder for more samples.
import logging
from tdlog import logger
logging.basicConfig(level=logging.INFO)
l = logging.getLogger('td_logger.test')
l.addHandler(logger.TreasureDataHandler())
l.info('Some message')
js = { "semicolon" : ";", "at" : "@" }
l.info(js)
This will throw the log entries to the local td-agent. And there's an important
point. This logger accepts only 'dict' and 'json string'.
Also, these parameters are logged by default.
* sys_host
* sys_name
* sys_module
* sys_lineno
* sys_levelno
* sys_levelname
* sys_filename
* sys_funcname
* sys_exc_info
* msg
These parameters can be specified at TreasureDataHander constructor.
* host: td-agent host (default: 127.0.0.1)
* port: td-agent port (default: 24224)
* db: td database name (default: log)
* table: td table name (default: default)
* bufmax: buffer size max when td-agent is unavailable (default: 1*1024*1024)
* timeout: network timeout (default: 3.0)
Have fun!
How to Develop
--------------
Folloings are the way to setup development envionment on MacOSX.
$ sudo easy_install virtualenv
$ virtualenv --no-site-packages .
New python executable in ./bin/python
Installing setuptools............done.
Installing pip...............done.
$ source bin/activate
$ bin/pip install msgpack-python
$ python run_tests.py
Special Thanks
--------------
- [Joshua Kuntz](https://github.com/j3kuntz) for the original work
Metadata
Release files for td-logger 0.4.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| td-logger-0.4.3.tar.gz | 3.2 kB | Without provenance | Details for td-logger-0.4.3.tar.gz |
Release files / td-logger-0.4.3.tar.gz
| Download URL | td-logger-0.4.3.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f9fddcce516efb74d804d6b2a6882303685767ea4ffda5a8f3d7c9d322e63b5d
|
|
BLAKE2b-256 checksum How to use checksums |
99a09df479dbce371b783362b2185d23888c514b7279951d87ab629e7fc9ba33
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for td-logger 0.4.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.