Talisker

Latest version: v0.21.3

Safety actively analyzes 630052 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 7 of 9

0.9.2

------------------

Bug fix release

* Fix celery metrics with eager tasks (70)
* Fix statsd cli args and metric format (71)
* Also fix depencecies on recent setuptools

0.9.1

------------------

This release has a couple of important bugfixes, upgrading is strongly encouraged.

* Feature: Add a generic script runner to run any python script with
talisker logging, primary usecase is django managment commands:

talisker.run myscript.py ...

* Improvement: DEVEL env var is no longer required (although still respected).
Talisker will assume DEVEL mode when stderr is a tty.

* Bugfix: re-add http metrics for gunicorn which were accidentaly dropped in
a refactor, with regression tests

* Bugfix: fix celery integration with 3.1.13+, with regression tests

* Bugfix: Add missing request_id to new accesslogs

* Bugfix: Fix issue 35, respect --log-level for gunicorn in DEVEL mode. This
means you can do --log-devel=debug and get debug level logging to your
console.

* Improvement: support raven 6

* Testing: now testing against pypy in CI, and also agains the minimum
supported versions of various dependencies too, to help prevent further
accidental dependencies on latest version apis (which is what broke celery
3.1.x integration)

0.9.0

------------------

The major feature in this release is support for sentry, which is integrated
with wsgi, logging, and celery. Also supports opt-in integration with
flask and django, see the relevant docs for more info.

Other changes

* refactor of how logging contexts were implemented. More flexible and
reliable. Note `talisker.logs.extra_logging` and
`talisker.logs.set_logging_context` are now deprecated, you should
use `talisker.logs.logging_context` and
`talisker.logs.logging_context.push`, respectively, as covered in the
updated logging docs.

* improved celery logging, tasks logs now have task_id and task_name
automatically added to their logs.

* improved logging messages when parsing TALISKER_NETWORKS at startup

0.8.0

------------------

* prometheus: add optinal support for promethues_client
* celery: request id automatically sent and logged, and support for 4.0
* docs: initial 'talisker contract'
* statsd: better client initialisation
* internal: refactoring of global variables, better /_status/ url dispatch

0.7.1

------------------

* remove use of future's import hooks, as they mess with raven's vendored imports
* slight tweak to logfmt serialisation, and update docs to match

0.7.0

------------------

*Upgrading*

This release includes a couple of minor backwards incompatible changes:

1) access logs now use the talisker format, rather than CLF. See the docs for
more info. If you are using access logs already, then the easiest upgrade
path is to output the access logs to stderr (access_logfile="-"), and delete
your old log files.

2) talisker no longer prefixes developer supplied tags with 'svc.'. This should
only matter if you've already set up dashboards or similar with the old
prefixed name, and you will need to remove the prefix

Changes:

* access logs now `in logfmt
<http://talisker.readthedocs.io/en/latest/logging.html#gunicorn-logs>`_
rather than CLF

* dummy statsd client is now useful `in testing
<http://talisker.readthedocs.io/en/latest/statsd.html#testing>`_

* logs are colored in development, to aid reading

* the 'svc' prefix for tags has been removed

Page 7 of 9

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.