Random Log Generator
Generator of random logs for multiple types of technologies.
This tool can generate all kinds of logs starting from templates. You should create a pattern file in YAML format foreach log that you want to generate, like in conf/patterns examples.
If more than one patterns are specified in patterns folder, all logs are generated in parallel. It’s possible to generate 100 logs in parallel.
Install
Clone repository
git clone https://github.com/WuerthPhoenix/log-generator.git
and install with setup.py:
$ cd log-generator $ python setup.py install
or use pip:
$ pip install rlog-generator
Pattern file
A pattern file has many parameters.
Parameters |
Descriptions |
|---|---|
name |
name of log |
enabled |
enable/disable this pattern |
path |
path where store the log |
eps |
number of logs per seconds that will be generate |
correction |
eps correction percentage |
time_period |
how many seconds the generating is active |
generator_type |
you can choose which generator use. The common value is template, that generate the logs from a template |
examples |
logs of examples |
template |
template to use to generate logs |
fields |
fields used in template |
We can have two kinds of fields: - list: the list fields are used to generate random values from a given list - func: the func fields enable functions to generate the random values.
The func fields start with func_ and then have the name of function. It can also have parameters.
The func developed are: - func_randip: generate a random ip address - func_randint: generate a random integer from min to max
For more details see the examples in folder conf/patterns.
If you want to contribute with real templates, add them in patterns folder.
Command line
The installation stores on system the rlog-generator command line.
$ rlog-generator --help
Usage: rlog-generator [OPTIONS]
Random Logs Generator Tool.
Options:
-p, --patterns TEXT Path all log patterns files (only *.yml)
[default: ~/.config/rlog_generator/patterns]
-m, --max-concur-req INTEGER Max concurrent logs generating [default: 10]
-l, --log-level [CRITICAL|ERROR|WARNING|INFO|DEBUG|NOTSET]
Log level on stdout [default: WARNING]
--progress-bar / --no-progress-bar
Enable/Disable progress bar [default: False]
--help Show this message and exit.
Features
Random logging from template
Template can be a list of more formats
TODO
Generate logs from raw examples
Apache 2 Open Source License
This tool can be downloaded, used, and modified free of charge. It is available under the Apache 2 license.
History
0.1.0 (2019-05-05)
First release.
Metadata
Release files for rlog-generator 0.2.0
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 | |
|---|---|---|---|---|
| rlog-generator-0.2.0.tar.gz | 10.2 kB | Without provenance | Details |
Release files / rlog-generator-0.2.0.tar.gz
| Download URL | rlog-generator-0.2.0.tar.gz |
|---|---|
| Size | 10.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
150224cc5cb04c22beac9b53de7060534b72cfa23292927ec8e1c3994ecbd11b
|
|
BLAKE2b-256 checksum How to use checksums |
68755b1fe2cf1f0f0b492de6d4196bb3a038ac882829253a99f4450319edc825
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.22.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.31.1 CPython/3.6.7
|
Security for rlog-generator 0.2.0
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.