logio
Parse log file as input and export the data to database as output.
Install
pip install logio
Installed Command Utils
- logio
Usage
C:\Workspace\logio>logio --help
Usage: logio [OPTIONS] COMMAND [ARGS]...
Parse log file as input and export the data to database as output.
Options:
-c, --config TEXT Config file path. The config file must in yaml format.
[required]
--help Show this message and exit.
Commands:
scan Try example settings on a test file.
server Start log handler server.
test Parse the example text and print out parse result.
Settings
- input
- type: stdin, file, tail
- ignore-blank-lines: true, false
- encoding: utf-8, gb18030, ...
- for type=file
- filename
- for type=tail
- filename
- offset-file
- read-from-end
- backup-patterns
- sleep-interval
- non-blocking
- blocking
- output
- type: mysql, stdout, print-not-matched-line
- buffer-size
- for type=mysql
- ignore-not-matched-lines
- keep-failed-lines
- inserts: list<string, string>
- key: DEFAULT, some other key
- sql_template
- parser
- type: regex, json
- keeep-not-matched-lines: bool
- for type=regex
- use-default-rules
- transforms
- rules
- matches: list<string, string>
- matched_name
- regex
Example config
input:
type: tail
filename: tests\nginx.access.log
parser:
type: regex
matches:
simple: "{SIMPLE_NGINX_ACCESS}"
transforms:
- field: time_local
type: strftime
strptime: "%d/%b/%Y:%H:%M:%S %z"
- field: request_time
type: str2number
- field: request_time
type: formula
formula: "{request_time} * 1000000"
- field: request_time
type: int
output:
type: mysql
mysql:
host: 127.0.0.1
port: 3306
user: root
password: password
database: database
inserts:
simple:
sql: insert into table_name (add_time, path, response_time) values (%s, %s, %s)
fields:
- time_local
- request_path
- request_time
Releases
v0.1.21 2025/10/24
- Add RequestBody transformer.
- Add LogToHttp output.
v0.1.19 2022/01/18
- Add sympy in requirements.txt.
- Remove mysqlclient from requirements.txt.
- Fix license file missing problem.
v0.1.18 2021/02/22
- Set default buffer-size to 10.
- Add log in loop.
- Use fastutils.logutils.setup.
V0.1.13 2021/02/18
- Add Nginx Access Log Rules.
- Add LogFilter subsystem.
- Add transforms support in LogParser.
v0.1.10 2020/10/10
- Add json parser.
v0.1.9 2020/09/10
- Change package's home url.
v0.1.8 2020/09/09
- Translate help informations to english.
- Add License.
- Add LogToStdout.
v0.1.7
- Some bad old release, ignore them...
Metadata
Release files for logio 0.1.21
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 |
|---|---|---|---|---|
| logio-0.1.21.tar.gz | 15.5 kB | Without provenance | Details for logio-0.1.21.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| logio-0.1.21-py3-none-any.whl | Python 3 | none | any | Details for logio-0.1.21-py3-none-any.whl |
Total release size: 31.9 kB
Release files / logio-0.1.21.tar.gz
| Download URL | logio-0.1.21.tar.gz |
|---|---|
| Size | 15.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0a81694f58d9bc050a197a2c4d1f72c3c455d14c5a08cd00d802efcd6791a9ec
|
|
BLAKE2b-256 checksum How to use checksums |
b16970dcf894ac545e954a59a6dbff3a533ea9d3cef09c421d4e64964862f60f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.12
|
Release files / logio-0.1.21-py3-none-any.whl
| Download URL | logio-0.1.21-py3-none-any.whl |
|---|---|
| Size | 16.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
d6e6eb02d82d9731e2c46897b3a8f58b643d92650fdd3034b0ab63052c324cf9
|
|
BLAKE2b-256 checksum How to use checksums |
3298a6afaef0e47d6a0fecf341653ad18f138260963ffc5f55ca21b355dcc123
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.11.12
|
Security for logio 0.1.21
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.