django-request-logging | Django middleware that logs http request body | HTTP library

by Rhumbix Python Version: 0.7.5 License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | django-request-logging Summary

django-request-logging is a Python library typically used in Networking, HTTP applications. django-request-logging has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can install using 'pip install django-request-logging' or download it from GitHub, PyPI.

Django middleware that logs http request body.

Support

Quality

Security

License

Reuse

Support

django-request-logging has a low active ecosystem.

It has 261 star(s) with 80 fork(s). There are 30 watchers for this library.

It had no major release in the last 12 months.

There are 15 open issues and 39 have been closed. On average issues are closed in 79 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of django-request-logging is 0.7.5

Quality

django-request-logging has 0 bugs and 0 code smells.

Security

django-request-logging has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

django-request-logging code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

django-request-logging is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

django-request-logging releases are not available. You will need to build from source code and install.

Deployable package is available in PyPI.

Build file is available. You can build the component from source.

Installation instructions are not available. Examples and code snippets are available.

django-request-logging saves you 308 person hours of effort in developing the same functionality from scratch.

It has 918 lines of code, 100 functions and 7 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed django-request-logging and discovered the below as its top functions. This is intended to give you an instant insight into django-request-logging implemented functionality, and help decide if they suit your requirements.

Log an error
Log a message
Get the package version
Logs a message to the console
Log an error message
Read content of file

Get all kandi verified functions for this library.

django-request-logging Key Features

No Key Features are available at this moment for django-request-logging.

django-request-logging Examples and Code Snippets

No Code Snippets are available at this moment for django-request-logging.

Community Discussions

Trending Discussions on django-request-logging

DRF: HTTP 401 logged at ERROR level. How to lower logging level?

QUESTION

DRF: HTTP 401 logged at ERROR level. How to lower logging level?

Asked 2018-Sep-05 at 22:36

I am trying to enable email alerts when HTTP 500 errors happens. Everything works fine, except that a Authentication credentials were not provided (HTTP 401) error is logged at ERROR level, which is way too verbose for email alerts.

Here is the email content (Django settings omitted here):

Report at /

[35mb'{"detail":"Authentication credentials were not provided."}' [0m

Request Method: GET

Request URL: https://myapi.org/dev/

Django Version: 2.0.2

Python Executable: /var/lang/bin/python3.6

Python Version: 3.6.1

Also, I am using the django-request-logging module to print requests' content.

Here is my logging config:

...

ANSWER

Answered 2018-Sep-05 at 03:08

From the documentation for django-request-logger:

If HTTP status code is between 400 - 599, URIs are logged at ERROR level, otherwise they are logged at INFO level.

See REQUEST_LOGGING_HTTP_4XX_LOG_LEVEL setting to override this.

And the documentation for that setting explains how to change the log level:

By default, HTTP status codes between 400 - 499 are logged at ERROR level. You can set REQUEST_LOGGING_HTTP_4XX_LOG_LEVEL = logging.WARNING (etc) to override this.

Source https://stackoverflow.com/questions/52174993

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install django-request-logging

You can install using 'pip install django-request-logging' or download it from GitHub, PyPI.
You can use django-request-logging like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: