Signalfx-tracing

Instrumentations

psycopg2

* Upgraded `dbapi-opentracing` to v0.0.5post1 (`pip install https://github.com/signalfx/python-dbapi/tarball/v0.0.5post1#egg=dbapi-opentracing`)
* This version of dbapi-opentracing adds support for psycopg2 Composed queries.

Features

- Added support for `SIGNALFX_TRACING_DEBUG`.
- Removed internal parallel logging exporter.
- Added logging to main exporter/reporter.

Features

- Adds `signalfx.tracing.library` and `signalfx.tracing.version` tags to local root span for each trace.

New Features

* Added Falcon 2.0+ support for Python3+

Changes:

- Support automatic trace context injection into logs.
- Fix issue with Jaeger client uninstalling in some cases.
- Updated documentation.

Breaking Changes
- Use SignalFx semantic conventions to represent errors in spans as attributes.

Errors will now be recorded in spans as attributes. The following
attributes will be used to represent errors:

- `error`: A boolean field set to true in case an operation resulted in an error.
- `sfx.error.kind`: The short name for type or “kind” of an error (only for event="error" logs). E.g., "Exception", "OSError".
- `sfx.error.object`: The type or “kind” of an error e.g., "subprocess.CalledProcessError".
- `sfx.error.stack`: A stack trace in platform-conventional format; may or may not pertain to an error. E.g., "File \"example.py\", line 7, in \<module\>\ncaller()\nFile \"example.py\", line 5, in caller\ncallee()\nFile \"example.py\", line 2, in callee\nraise Exception(\"Yikes\")\n"
- `sfx.error.message`: A concise, human-readable, one-line message explaining the error . E.g., "Could not connect to backend", "Cache invalidation succeeded"