* opentelemetry-instrumentation-system-metrics: add process metrics
Add process metrics as of 1.30.0 semconv to the system metrics instrumentation.
We still keep around the old process.runtime metrics because the semconv
suggest to not break current users. Still discourage their use in the
doc and state explicitly they are deprecated.
* Add Changelog
* Please pylint
* Apply suggestions from code review
* Remove print
* Remove process.count and fix system metrics enumeration in tests
* Cleanup metrics presence assertions
* Don't touch system metrics descriptions
* Add default for num_cpu in case it returns None to avoid division error
Follow-up on the apparently abbandonned https://github.com/open-telemetry/opentelemetry-python-contrib/pull/2114.
The asyncpg instrumentation attempts to fall back on using the database
name as the span name in case the first argument to the instrumented
method is falsey.
This has probably never worked since asyncpg defines the `_params`
attribute as an instance of `ConnectionParams`
(https://github.com/MagicStack/asyncpg/blob/master/asyncpg/connection.py#L62)
which is a NamedTuple instance and thus don't define `get`. The proper
way of safely accessing properties on a NamedTuple is using `getattr`.
The only case that I've actually found which triggers this branch is if
the supplied query is an empty string. This is something that causes an
`AttributeError` for `Connection.execute` but is fine for `fetch()`,
`fetchval()`, `fetchrow()` and `executemany()`.
The tests have been expanded to check these cases. Also, more status
code validation has been added where it was missing.
Co-authored-by: Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com>
* Create per-extension tracers if there's an extension available
* botocore: add user events for bedrock
* Remove pass of AWS env vars from tox.ini
* Remove handling for other types of messages
* Please pylint
* Add changelog
* Update CHANGELOG.md
Co-authored-by: Adrian Cole <64215+codefromthecrypt@users.noreply.github.com>
---------
Co-authored-by: Adrian Cole <64215+codefromthecrypt@users.noreply.github.com>
* Add basic handling for invoke.model
* Add changelog a please pylint
* Record converse cassettes against us-east-1
* Avoid double copy of streaming body
---------
Co-authored-by: Adrian Cole <64215+codefromthecrypt@users.noreply.github.com>
If we are not running inside AWS Lambda don't print warnings on missing
OTel lambda extension layer.
The instrumentation is installed by the OTel k8s operator and so this
warning may confuse users.
* botocore: add extension for bedrock runtime api
* Add tests and handle only non streaming responses
* Make it explicit we are handling only the converse operation
* Simplify test since all models behaves the same
* Add test for error case and rework things a bit
* Add converse example
* Generate workflows
* Add changelog
* Add type hints to Psycopg
* fix tests
* fix
* Add psycopg.Connection to nitpick
* Add py.typed
* add psycopg to nitpick again
* add psycopg to nitpick again
* move py.typed to the right folder
---------
Co-authored-by: Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com>
* Support PEP 561 to `opentelemetry-instrumentation-urllib`
* add future
---------
Co-authored-by: Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com>
* click: ignore click based servers
We don't want to create a root span for long running processes like servers
otherwise all requests would have the same trace id which is unfortunate.
---------
Co-authored-by: Tammy Baylis <96076570+tammy-baylis-swi@users.noreply.github.com>
* opentelemetry-instrumentation-falcon: expand supported version to v4
Falcon v4 has a mostly identical interface to v3, and is proved to be fully compatible with `opentelemetry-instrumentation-falcon`. Loose the version check to `<5.0.0` to avoid false `DependencyConflict` alarm.
* opentelemetry-instrumentation-falcon: generate tests for v4
* opentelemetry-instrumentation-falcon: prepare tests for v4
* opentelemetry-instrumentation-falcon: add test preset for `~=3.1.2`
* docs: add changelog for Falcon v4 instrumentation
* opentelemetry-instrumentation-falcon: adjust pylint mark for v4
* _has_fixed_http_target property
Signed-off-by: emdneto <9735060+emdneto@users.noreply.github.com>
* move changelog to the correct section
Signed-off-by: emdneto <9735060+emdneto@users.noreply.github.com>
* fix test and bootstrap_gen
Signed-off-by: emdneto <9735060+emdneto@users.noreply.github.com>
---------
Signed-off-by: emdneto <9735060+emdneto@users.noreply.github.com>
Co-authored-by: emdneto <9735060+emdneto@users.noreply.github.com>
Add "Repository" label to project urls pointing to the
opentelemetry-python repo root url.
Having within project urls one entry with the same value for all
packages released by the project will help tools for automatic
dependency management to suggest coherent upgrades for related packages.
