opentelemetry-python-contrib

opentelemetry-python-contrib copied to clipboard

Flask Instrumentation doesn't work with "from flask import Flask"

9

**Describe your environment** **Steps to reproduce** Flask does not work with "from flask import Flask": ```python from flask import Flask from opentelemetry.instrumentation.flask import FlaskInstrumentor FlaskInstrumentor().instrument() app = Flask(__name__) @app.route("/") def...

jeremydvoss

Improved logging instrumentor

3

# Description ## Logging fields customization Having connected this tool, I was surprised that the names of the logging fields were hard-coded. The naming convention for such fields in my...

Olegt0rr

Audit all packages to ensure NoOpTracerProvider works

5

An [issue](https://github.com/open-telemetry/opentelemetry-python-contrib/issues/956) was found in the wsgi instrumentation by integration tests in the core repository. The issue should have been caught by unit tests in the instrumentation using the NoOpTracerProvider....

codeboten

sqlalchemy intrument missing operation span

1

**Describe your environment** We are using otel in a lambda with Python3.9, to get the opentelemtry library we are using the [otel layer for aws](https://aws-otel.github.io/docs/getting-started/lambda/lambda-python) (v1.17/0.38b0) the latest version. **Steps...

rodrilp

kafka-python Instrument temporary fork, kafka-python-ng inside kafka-python's instrumentation

2

# Description Related PR (Another Option): https://github.com/open-telemetry/opentelemetry-python-contrib/pull/2532 This PR adds kafka-python-ng, a temporary fork of kafka-python due to pypi access issues, to the kafka-python instrumentation. ## Type of change -...

rjduffner

Adds NoOpTracerProvider test case for botocore instrumentation

2

# Description Adds NoOpTracerProvider test cases for botocore instrumentation. Fixes [#988](https://github.com/open-telemetry/opentelemetry-python-contrib/issues/988) # How Has This Been Tested? tox -e test-instrumentation-botocore # Does This PR Require a Core Repo Change? No.

shwejanraj

Django instrumentation - Trace request attributes also in the response

3

_Sorry, but I'm slightly confused whether I should create an issue in this repository or https://github.com/open-telemetry/opentelemetry-python-contrib. If it's the other one, i'll gladly reopen it there._ --- **Is your feature...

Zajozor

Route used in Django span name is resolved incorrectly and inefficiently

3

See the conversation in https://github.com/open-telemetry/opentelemetry-python-contrib/pull/2624/files#r1646685931 corresponding to changes in https://github.com/open-telemetry/opentelemetry-python-contrib/commit/dc42bdd986cd136559fda6a3032061d4eed7e517#r1646685931 In summary, only using the route obtained in `process_view` is more reliably correct and more efficient than calling `resolve(request.path)` when...

alexmojaki

# Description Right now we only have the `error.type` for HTTP status code, but we should handle the exceptions and set it in `error.type` as well Fixes #2699 ## Type...

emdneto

opentelemetry-instrumentation-asgi: emit `error.type` attribute when having exceptions

3

### Describe your environment instrumentation-asgi: 0.47b0.dev ### What happened? instrumentation-asgi isn't setting `error.type` during exceptions and we should set it in the new semconv as defined [here](https://github.com/open-telemetry/semantic-conventions/blob/main/docs/http/http-spans.md#http-server-semantic-conventions) ### Steps to...

emdneto