This release is a pre-release and may not be stable for production use.
Requset Log Middleware
======================
Request log middleware to capture meta data associated with each user request into mongo database. The write acknowledgement at time of save to mongo is disabled to ensure there is minimum performance lag due to this middleware.
Note: this is work in progress - expect bugs etc
Requirements
===========
* pymongo
* celery
* Mongo
* Elasti Search
* Tested on Django > 1.3
Setup / Installation
====================
* Install the package using pip
pip install requestlogs
Update settings.py
* Add app 'requestlogs' to your INSTALLED_APPS
* Add 'requestlogs.middleware.RequestLogMiddleware' to MIDDLEWARE_CLASSES after auth
* Set the app name, this will be used in the collection / index etc
RLOG_APP_NAME = 'app' # used to uniquely identify the collection
* Set the engine / db where you want the logs to be captured
RLOG_ENGINE = 'MONGO' or RLOG_ENGINE = 'ELASTICSEARCH'
* For MONGO: Customize the name and mongo connections
RLOG_MONGODB_URI = 'mongodb://127.0.0.1:27017/requestlogs_db?w=0' # mongodb to capture request logs
# mongodb://[username:password@]host1[:port1][,host2[:port2],...[,hostN[:portN]]][/[database][?options]]
# refer: http://docs.mongodb.org/manual/reference/connection-string/
- The collection name will be set to {RLOG_APP_NAME}_request_logs
* For ELASTICSEARCH: Customize the name and connections
ELASTICSEARCH_CONN = [{'host': 'localhost', 'port': 9200}, ]
RLOG_ELASTICSEARCH_TTL = "90d" # set the TTL for auto expiry
- The document type will be set to {RLOG_APP_NAME}-requestlogs
- The index name will be set to idx-{RLOG_APP_NAME}-requestlogs
- For Kibana - a customized dashboard has been created, change the type and index to use it
ToDos
=====
This package is still under development, following are the high level items to be implemented
* Capture custom session variable
* Add views to pull transactions by user
* Add views to search transactions by user and datetime
* Test cases
Metadata
Release files for RequestLogs 1.0dev
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 |
|---|---|---|---|---|
| RequestLogs-1.0dev.tar.gz | 7.6 kB | Without provenance | Details for RequestLogs-1.0dev.tar.gz |
Release files / RequestLogs-1.0dev.tar.gz
| Download URL | RequestLogs-1.0dev.tar.gz |
|---|---|
| Size | 7.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6d316ad4a3bfadd07f9d79a31c942e7d507fb7a1b3fb3f58b37d1adecde5a179
|
|
BLAKE2b-256 checksum How to use checksums |
0b22d9ec8458f922acecc5b0e9fc4eee20e7b95ee1223bbbda2ba3ba24e59acd
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for RequestLogs 1.0dev
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.