===============
199Fix
===============
199Fix provides a logging handler to push exceptions and other errors to https://199fix.com/.
Installation
============
Installation with ``pip``:
::
$ pip install 199fix
Get an API Key here https://199fix.com/signup/
Add ``'199fix.handlers.I99FixHandler'`` as a logging handler:
::
LOGGING = {
'version': 1,
'disable_existing_loggers': False,
'filters': {
'require_debug_false': {
'()': 'django.utils.log.RequireDebugFalse'
}
},
'handlers': {
'199fix': {
'level': 'ERROR',
'class': 'i99fix.handlers.I99FixHandler',
'filters': ['require_debug_false'],
'api_key': '[your-api-key]',
'env_name': 'production',
},
},
'loggers': {
'django': {
'handlers': ['199fix'],
'level': 'ERROR',
'propagate': True,
},
}
}
Settings
========
``level`` (built-in setting)
Change the ``level`` to ``'ERROR'`` to disable logging of 404 error messages.
``api_key`` (required)
API key , Get one here https://199fix.com/.
``env_name`` (required)
Name of the environment (e.g. production, development)
Contributing
============
* Fork the repository on GitHub and start hacking.
* Run the tests.
* Send a pull request with your changes.
199Fix
===============
199Fix provides a logging handler to push exceptions and other errors to https://199fix.com/.
Installation
============
Installation with ``pip``:
::
$ pip install 199fix
Get an API Key here https://199fix.com/signup/
Add ``'199fix.handlers.I99FixHandler'`` as a logging handler:
::
LOGGING = {
'version': 1,
'disable_existing_loggers': False,
'filters': {
'require_debug_false': {
'()': 'django.utils.log.RequireDebugFalse'
}
},
'handlers': {
'199fix': {
'level': 'ERROR',
'class': 'i99fix.handlers.I99FixHandler',
'filters': ['require_debug_false'],
'api_key': '[your-api-key]',
'env_name': 'production',
},
},
'loggers': {
'django': {
'handlers': ['199fix'],
'level': 'ERROR',
'propagate': True,
},
}
}
Settings
========
``level`` (built-in setting)
Change the ``level`` to ``'ERROR'`` to disable logging of 404 error messages.
``api_key`` (required)
API key , Get one here https://199fix.com/.
``env_name`` (required)
Name of the environment (e.g. production, development)
Contributing
============
* Fork the repository on GitHub and start hacking.
* Run the tests.
* Send a pull request with your changes.
1 maintainer
Metadata
1 maintainer
Release files for 199Fix 1.1.2
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 | |
|---|---|---|---|---|
| 199Fix-1.1.2.tar.gz | 4.3 kB | Without provenance | Details |
Release files / 199Fix-1.1.2.tar.gz
| Download URL | 199Fix-1.1.2.tar.gz |
|---|---|
| Size | 4.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
05f8b3aa807c6d1f27d6fbba7af9fc2f9cd8cbafbb13b5440f29ec9fb85ba548
|
|
BLAKE2b-256 checksum How to use checksums |
b008009a1724b20c12ca35f3b8022db7df53ec6fb94826eb036d8b501f94a2e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for 199Fix 1.1.2
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.
