{"id":20317524,"url":"https://github.com/dynatrace/oneagent-sdk-for-python","last_synced_at":"2025-04-11T17:55:05.172Z","repository":{"id":54794537,"uuid":"123154266","full_name":"Dynatrace/OneAgent-SDK-for-Python","owner":"Dynatrace","description":"Enables custom tracing of Python applications in Dynatrace","archived":false,"fork":false,"pushed_at":"2024-01-04T11:46:54.000Z","size":5091,"stargazers_count":26,"open_issues_count":1,"forks_count":10,"subscribers_count":12,"default_branch":"master","last_synced_at":"2024-11-10T18:53:37.461Z","etag":null,"topics":["agent","apm","data-ingestion","dev-program","dynatrace","oneagent","sdk","sdk-python"],"latest_commit_sha":null,"homepage":"https://www.dynatrace.com/support/help/extend-dynatrace/oneagent-sdk/what-is-oneagent-sdk/","language":"Python","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/Dynatrace.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2018-02-27T16:09:26.000Z","updated_at":"2024-01-04T14:50:39.000Z","dependencies_parsed_at":"2023-11-27T16:28:03.527Z","dependency_job_id":"2d2cec49-870d-47b1-9bf5-03eae1dc84f5","html_url":"https://github.com/Dynatrace/OneAgent-SDK-for-Python","commit_stats":{"total_commits":37,"total_committers":8,"mean_commits":4.625,"dds":0.6216216216216216,"last_synced_commit":"29ea31406d884215e8d7713a2b9149a7aad56491"},"previous_names":[],"tags_count":12,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Dynatrace%2FOneAgent-SDK-for-Python","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Dynatrace%2FOneAgent-SDK-for-Python/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Dynatrace%2FOneAgent-SDK-for-Python/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Dynatrace%2FOneAgent-SDK-for-Python/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/Dynatrace","download_url":"https://codeload.github.com/Dynatrace/OneAgent-SDK-for-Python/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":224673407,"owners_count":17350910,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["agent","apm","data-ingestion","dev-program","dynatrace","oneagent","sdk","sdk-python"],"created_at":"2024-11-14T18:32:58.724Z","updated_at":"2024-11-14T18:32:59.429Z","avatar_url":"https://github.com/Dynatrace.png","language":"Python","readme":"\u003e Read the latest version of this README, with working internal links, at [GitHub](https://github.com/Dynatrace/OneAgent-SDK-for-Python#readme).\n\n# Dynatrace OneAgent SDK for Python\n\nThis SDK enables Dynatrace customers to extend request level visibility into Python applications. It provides the Python implementation of the [Dynatrace OneAgent SDK](https://github.com/Dynatrace/OneAgent-SDK).\n\nFor the latest updates, see [Release notes and announcements](#release-notes-and-announcements)\nand make sure you are reading the [latest version of this document](https://github.com/Dynatrace/OneAgent-SDK-for-Python#readme).\n\n\u003c!-- Generate with https://github.com/jonschlinkert/markdown-toc --\u003e\n\n\u003c!-- toc --\u003e\n\n- [Requirements](#requirements)\n- [Using the OneAgent SDK for Python in your application](#using-the-oneagent-sdk-for-python-in-your-application)\n- [API Concepts](#api-concepts)\n  * [Initialization and SDK objects](#initialization-and-sdk-objects)\n  * [Tracers](#tracers)\n- [Features and how to use them](#features-and-how-to-use-them)\n  * [Remote calls](#remote-calls)\n  * [SQL database requests](#sql-database-requests)\n  * [Incoming web requests](#incoming-web-requests)\n  * [Outgoing web requests](#outgoing-web-requests)\n  * [Trace in-process asynchronous execution](#trace-in-process-asynchronous-execution)\n  * [Custom Request Attributes](#custom-request-attributes)\n  * [Custom services](#custom-services)\n  * [Messaging](#messaging)\n    + [Outgoing Messages](#outgoing-messages)\n    + [Incoming Messages](#incoming-messages)\n- [W3C trace context](#w3c-trace-context)\n- [Using the OneAgent SDK for Python with forked child processes (only available on Linux)](#using-the-oneagent-sdk-for-python-with-forked-child-processes-only-available-on-linux)\n- [Troubleshooting](#troubleshooting)\n  * [Extended SDK State](#extended-sdk-state)\n  * [Shutdown crashes](#shutdown-crashes)\n- [Repository contents](#repository-contents)\n- [Help \u0026 Support](#help--support)\n  * [Read the manual](#read-the-manual)\n  * [Let us help you](#let-us-help-you)\n- [Release notes and announcements](#release-notes-and-announcements)\n  * [Announcements in November 2023](#announcements-in-november-2023)\n  * [Version 1.5.1](#version-151)\n  * [Version 1.5.0](#version-150)\n- [License](#license)\n\n\u003c!-- tocstop --\u003e\n\n\u003ca name=\"requirements\"\u003e\u003c/a\u003e\n## Requirements\n\nThe latest release of the SDK supports Python 3 only, see below for exact support status of Python versions.\n\nOnly the official CPython (that is, the \"normal\" Python, i.e. the Python implementation\nfrom \u003chttps://python.org\u003e) is supported and only on Linux (musl libc which is used, e.g., on Alpine Linux, is currently not supported)\nand Windows with the x86 (including x86-64) architecture.\nIt is always advised to use the latest patch version of your minor versoin of Python, as these usually contain security\nfixes and other important bugfixes.\n\nAdditionally, `pip` with the `wheel` and `setuptools` package installed is required for installation,\nand on Linux, the system needs to be [`manylinux1`-compatible](https://www.python.org/dev/peps/pep-0513/).\n`pip` versions before 8.1.0 are known not to work, but generally it is advised to always use the latest pip version.\nDue to factors such as changes in package hosting by PyPI and Python itself,\nDynatrace cannot guarantee that SDK installation is, or will continue to be,\npossible with old pip versions.\n\nThe Dynatrace OneAgent SDK for Python is a wrapper of the [Dynatrace OneAgent SDK for C/C++](https://github.com/Dynatrace/OneAgent-SDK-for-C)\nand therefore the SDK for C/C++ is required and delivered with the Python SDK. See\n[here](https://github.com/Dynatrace/OneAgent-SDK-for-C#requirements)\nfor its requirements, which also apply to the SDK for Python.\n\nThe version of the SDK for C/C++ that is included in each version of the SDK for Python is shown in the following table along with the required\nDynatrace OneAgent version (it is the same as\n[listed in the OneAgent SDK for C/C++'s documentation](https://github.com/Dynatrace/OneAgent-SDK-for-C/blob/master/README.md#compatibility-of-dynatrace-oneagent-sdk-for-cc-releases-with-oneagent-releases)).\n\n\u003e Note: The OneAgent SDK is not supported on serverless code modules, including those for AWS Lambda.\n\u003e Consider using [OpenTelemetry](https://www.dynatrace.com/support/help/shortlink/opentel-lambda) instead in these scenarios.\n\n\u003ca name=\"pycversiontab\"\u003e\u003c/a\u003e\n\n|OneAgent SDK for Python|Bundled OneAgent SDK for C/C++|Required OneAgent|Required Python       |Support status |\n|:----------------------|:-----------------------------|:----------------|:---------------------|:--------------|\n|1.5.x                  |1.7.1                         |≥1.251           |≥3.5                  |🟢 Supported|\n|1.4.x                  |1.6.1                         |≥1.179           |3.4.x-3.11.x          |ℹ️ Deprecated with support ending 2024-06-01|\n|1.3.x                  |1.5.1                         |≥1.179           |2.7.x or 3.4.x-3.11.x |❌ Unsupported since 2023-07-01|\n|1.2.x                  |1.4.1                         |≥1.161           |2.7.x or 3.4.x-3.11.x |❌ Unsupported since 2023-07-01|\n|1.1.x                  |1.3.1                         |≥1.151           |2.7.x or 3.4.x-3.11.x |❌ Unsupported since 2023-07-01|\n|1.0.x                  |1.1.0                         |≥1.141           |2.7.x or 3.4.x-3.11.x |❌ Unsupported since 2023-07-01|\n\nNote that this table only states the support status of the mentioned OneAgent SDK for Python version\nwith the included OneAgent SDK for C/C++, not the OneAgent itself.\n\nThe \"required Python\" column indicates the Python versions with which the SDK version was developed and tested (where marked with *,\nthe minimum version has been updated to adjust for Python deprecations from the table below).\nWe may additionally announce deprecations for older versions of Python in combination with specific or all versions of the SDK,\nmeaning that we will no longer provide support for these combinations after the given date, even if the SDK version itself\nis supported and technically running on that Python version.\nWe also strongly advise against using Python versions that are no longer supported by your Python vendor.\n\nWe intend to deprecate Python versions effective around 6 months after the Python project stops supporting them as documented by the\nPython project: \u003chttps://devguide.python.org/versions/\u003e. We will announce every deprecation explicitly, usually 6 months before\nit becomes effective.\n\n\u003ca name=\"pysupporttab\"\u003e\u003c/a\u003e\n\n| Python version | Deprecation status |\n|:---------------|:---------------|\n| Any later 3.x  |🟢 Supported unless announced otherwise. Pre-releases are not supported. |\n| 3.8.x          |🟢 Supported. Expected to be deprecated with support ending around May 2025 |\n| 3.7.x          |⚠️ Deprecated with SDK support ending 2024-09-01; Declared EOL by Python.org |\n| 3.4.x-3.6.x    |⚠️ Deprecated with SDK support (with compatible SDK versions) ending 2024-06-01; Declared EOL by Python.org |\n| 2.7.x          |❌ Unsuspported since 2023-07-01 |\n\n\n\u003ca name=\"#using-the-oneagent-sdk-for-python-in-your-application\"\u003e\u003c/a\u003e\n## Using the OneAgent SDK for Python in your application\n\n\u003ca name=\"installation\"\u003e\u003c/a\u003e\n\nTo install the latest version of the OneAgent SDK for Python, use the PyPI package\n`oneagent-sdk`:\n\n```bash\npython -m pip install --upgrade oneagent-sdk\n```\n\n`pip`, `setuptools` and `wheel` need to be installed and should be up to date before running this command.\n\nTo verify your installation, execute\n\n```bash\npython -c \"import oneagent; print(oneagent.initialize())\"\n```\n\nIf the installation was successful, you should get an output ending with `InitResult(status=0, error=None)`. Otherwise, see the [Troubleshooting](#troubleshooting) section.\n\nTo load the OneAgent SDK into your application, just add the following line at the top of your script:\n\n```python\nimport oneagent\n```\n\nHere is a quick \"Hello World\" that will produce a service call in Dynatrace:\n\n```python\nimport oneagent\n\nif not oneagent.initialize():\n    print('Error initializing OneAgent SDK.')\n\nwith oneagent.get_sdk().trace_incoming_remote_call('method', 'service', 'endpoint'):\n    pass\n\nprint('It may take a few moments before the path appears in the UI.')\ninput('Please wait...')\noneagent.shutdown()\n```\n\nA more detailed [sample application is available here](https://github.com/Dynatrace/OneAgent-SDK-for-Python/blob/master/samples/basic-sdk-sample/basic_sdk_sample.py).\nSee also the Quickstart section in the [API documentation](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/quickstart.html).\n\n\n\u003ca name=\"api-concepts\"\u003e\u003c/a\u003e\n## API Concepts\n\nCommon concepts of the Dynatrace OneAgent SDK are explained in the [Dynatrace OneAgent SDK repository](https://github.com/Dynatrace/OneAgent-SDK#apiconcepts).\n\n\u003ca name=\"initialization-and-sdk-objects\"\u003e\u003c/a\u003e\n### Initialization and SDK objects\n\nBefore first using any other SDK functions, you need to initialize the SDK.\n\n```python\ninit_result = oneagent.initialize()\nprint('OneAgent SDK initialization result' + repr(init_result))\nif init_result:\n    print('SDK should work (but agent might be inactive).')\nelse:\n    print('SDK will definitely not work (i.e. functions will be no-ops):', init_result)\n```\n\nSee the API documentation for the [`initialize` function](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.initialize)\nand the [`InitResult` class](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.InitResult) for more information.\n\nTo use the SDK, get a reference to the [`SDK`](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.sdk.SDK)\nsingleton by calling the oneagent static [`get_sdk`](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.get_sdk)\nmethod. The first thing you may want to do with this object, is checking if the agent is active by comparing the value of the\n[`agent_state`](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.sdk.SDK.agent_state)\nproperty to the [`oneagent.common.AgentState`](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.common.AgentState)\nconstants. You can also have a look at the [extended SDK state information](#extended-sdk-state).\n\n```python\nimport oneagent\nfrom oneagent.common import AgentState\n# Initialize oneagent, as above\n\nsdk = oneagent.get_sdk()\nif sdk.agent_state not in (AgentState.ACTIVE, AgentState.TEMPORARILY_INACTIVE):\n    print('Too bad, you will not see data from this process.')\n```\n\nAs a development and debugging aid it is recommended to set a diagnostic callback. The callback will be used by the SDK to inform about unusual events.\n\nUnusual events that prevent an operation from completing successfully include:\n* API usage errors\n* other unexpected events (like out of memory situations)\n\n\u003e **NOTE**: Use this as a development and debugging aid only. Your application should not rely on a calling sequence or any message content being set\nor passed to the callback.\n\nDuring development, it is additionally recommended to use the \"verbose callback\" which also informs about other events that may be benign\nbut can be very helpful in debugging, e.g. a PurePath that was not created because a Tracer is disabled by configuration, etc.\n\n```python\ndef _diag_callback(unicode_message):\n\tprint(unicode_message)\n\nsdk.set_diagnostic_callback(_diag_callback)\nsdk.set_verbose_callback(_diag_callback) # Do not use this callback in production\n```\n\n\n\u003ca name=\"tracers\"\u003e\u003c/a\u003e\n### Tracers\n\nTo trace any kind of call you first need to create a\n[Tracer](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.sdk.tracers.Tracer),\nusing one of the various `trace_*` methods of the\n[`SDK`](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.sdk.SDK)\nobject. The Tracer object controls the “life cycle” of a trace: Entering a\n`with`-block with a tracer starts the trace, exiting it ends it. Exiting the\n`with` block with an exception causes the trace to be marked as failed with the\nexception message (if you do not want or need this behavior, tracers have\nexplicit methods for starting, ending and attaching error information too; see the\n[documentation](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.sdk.tracers.Tracer)).\n\nA Tracer instance can only be used from the thread on which it was created.\nWhenever you start a tracer, the tracer becomes a child of the previously active tracer\non this thread and the new tracer then becomes the active tracer. You may only end the active tracer.\nIf you do, the tracer that was active before it (its parent) becomes active again.\nPut another way, tracers must be ended in reverse order of starting them\n(you can think of this being like HTML tags where you must also close the child tag before you can close the parent tag).\nWhile the tracer's automatic parent-child relationship works very intuitively in most cases,\nit does not work with **asynchronous patterns**, where the same thread handles multiple logically\nseparate operations in an interleaved way on the same thread. If you need to instrument\nsuch patterns with the SDK, you need to end your tracer before the thread is potentially reused\nby any other operation (e.g., before yielding to the event loop). To later continue the trace,\ncapture an in-process link before and later resume using the in-process link tracer, as explained in\n[Trace in-process asynchronous execution](#trace-in-process-asynchronous-execution). This approach is rather awkward and\nmay lead to complex and difficult to interpret traces. If your application makes extensive use of\nasynchronous patterns of the kind that is difficult to instrument with the SDK, consider using\nthe [OpenTelemetry support of Dynatrace](https://www.dynatrace.com/support/help/shortlink/opent-python) instead.\n\nThere are different tracer types requiring different information for creation.\nAs an example, to trace an incoming remote call, this would be the most simple\nway to trace it:\n\n```python\nimport oneagent\n\nwith oneagent.get_sdk().trace_incoming_remote_call('method', 'service', 'endpoint'):\n    pass # Here you would do the actual work that is timed\n```\n\nSee the section on [remote calls](#remote-calls) for more information.\n\nSome tracers also support attaching additional information before ending it.\n\n**Important:** In Python 2, tracers accept both byte (“normal”) and unicode\nstrings. Byte strings must always use the UTF-8 encoding!\n\n\n\u003ca name=\"features-and-how-to-use-them\"\u003e\u003c/a\u003e\n## Features and how to use them\n\nThe feature sets differ slightly with each language implementation. More functionality will be added over time, see\n[Planned features for OneAgent SDK](https://answers.dynatrace.com/spaces/483/dynatrace-product-ideas/idea/198106/planned-features-for-oneagent-sdk.html)\nfor details on upcoming features.\n\nA more detailed specification of the features can be found in [Dynatrace OneAgent SDK](https://github.com/Dynatrace/OneAgent-SDK#features).\n\n|Feature                                   |Required OneAgent SDK for Python version|\n|:-----------------------------------------|:--------|\n|W3C trace context for log enrichment      |≥1.5.0   |\n|Custom services                           |≥1.2.0   |\n|Messaging                                 |≥1.2.0   |\n|In-process linking                        |≥1.1.0   |\n|Custom request attributes                 |≥1.1.0   |\n|Outgoing web requests                     |≥1.1.0   |\n|Incoming web requests                     |≥1.0.0   |\n|SQL database requests                     |≥1.0.0   |\n|Trace incoming and outgoing remote calls  |≥1.0.0   |\n\n\u003ca name=\"remote-calls\"\u003e\u003c/a\u003e\n### Remote calls\n\nYou can use the SDK to trace communication from one process to another. This will enable you to see full Service Flow, PurePath and Smartscape topology\nfor remoting technologies that Dynatrace is not aware of.\n\nTo trace any kind of remote call you first need to create a Tracer. The Tracer object represents the endpoint that you want to call, thus you need to\nsupply the name of the remote service and method. In addition, you need to transport a tag in your remote call from the client side to the server side\nif you want to trace it end to end.\n\nOn the client side, you would trace the outgoing remote call like this:\n\n```python\noutcall = sdk.trace_outgoing_remote_call(\n    'remoteMethodToCall', 'RemoteServiceName', 'rmi://Endpoint/service',\n    oneagent.sdk.Channel(oneagent.sdk.ChannelType.TCP_IP, 'remoteHost:1234'),\n    protocol_name='RMI/custom')\nwith outcall:\n    # Note: You can access outgoing_dynatrace_*_tag only after the trace\n    # has started!\n    strtag = outcall.outgoing_dynatrace_string_tag\n    do_actual_remote_call(extra_headers={'X-dynaTrace': strtag})\n```\n\nOn the server side, you would trace it like this:\n\n```python\nincall = sdk.trace_incoming_remote_call(\n    'remoteMethodToCall', 'RemoteServiceName', 'rmi://Endpoint/service',\n    protocol_name='RMI/custom',\n    str_tag=my_remote_message.get_header_optional('X-dynaTrace'))\nwith incall:\n    pass # Here you would do the actual work that is timed\n```\n\nSee the documentation for more information:\n\n* [`trace_incoming_remote_call`](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.sdk.SDK.trace_incoming_remote_call)\n* [`trace_outgoing_remote_call`](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.sdk.tracers.trace_outgoing_remote_call)\n* [General information on tagging](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/tagging.html)\n\n\u003ca name=\"sql-database-requests\"\u003e\u003c/a\u003e\n### SQL database requests\n\nTo trace database requests you need a database info object which stores the information about your database which does not change between individual\nrequests. This will typically be created somewhere in your initialization code (after initializing the SDK):\n\n```python\ndbinfo = sdk.create_database_info(\n    'Northwind', oneagent.sdk.DatabaseVendor.SQLSERVER,\n    oneagent.sdk.Channel(oneagent.sdk.ChannelType.TCP_IP, '10.0.0.42:6666'))\n```\n\nThen you can trace the SQL database requests:\n\n```python\nwith sdk.trace_sql_database_request(dbinfo, 'SELECT foo FROM bar;') as tracer:\n    # Do actual DB request\n    tracer.set_rows_returned(42) # Optional\n    tracer.set_round_trip_count(3) # Optional\n```\n\nNote that you need to release the database info object. You can do this by calling `close()` on it or using it in a `with` block.\n\nSee the documentation for more information:\n\n* [`create_database_info`](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.sdk.SDK.create_database_info)\n* [`trace_sql_database_request`](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.sdk.SDK.trace_sql_database_request)\n* [`DatabaseRequestTracer`](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.sdk.tracers.DatabaseRequestTracer)\n\nPlease note that SQL database traces are only created if they occur within some other SDK trace (e.g. incoming remote call).\n\n\u003ca name=\"incoming-web-requests\"\u003e\u003c/a\u003e\n### Incoming web requests\n\n[Same as with database infos](#sql-database-requests), to trace incoming web requests you need a web application info object which stores the\ninformation about your web application which does not change:\n\n```python\nwappinfo = sdk.create_web_application_info(\n    virtual_host='example.com',\n    application_id='MyWebApplication',\n    context_root='/my-web-app/')\n```\n\nThen you can trace incoming web requests:\n\n```python\nwreq = sdk.trace_incoming_web_request(\n    wappinfo,\n    'http://example.com/my-web-app/foo?bar=baz',\n    'GET',\n    headers={'Host': 'example.com', 'X-foo': 'bar'},\n    remote_address='127.0.0.1:12345')\n\nwith wreq:\n    wreq.add_parameter('my_form_field', '1234')\n    # Process web request\n    wreq.add_response_headers({'Content-Length': '1234'})\n    wreq.set_status_code(200) # OK\n```\n\nNote that you need to release the web application info object. You can do this by calling `close()` on it or using it in a `with` block.\n\nIncoming web request tracers support some more features not shown here. Be sure to check out the documentation:\n\n* [`create_web_application_info`](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.sdk.SDK.create_web_application_info)\n* [`trace_incoming_web_request`](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.sdk.SDK.trace_incoming_web_request)\n* [`IncomingWebRequestTracer`](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.sdk.tracers.IncomingWebRequestTracer)\n\n\n\u003ca name=\"outgoing-web-requests\"\u003e\u003c/a\u003e\n### Outgoing web requests\n\nTo trace an outgoing web request you need to create an 'Outgoing Web Request Tracer' object. You pass the destination URL, the HTTP method and\nrequest headers as parameters.\n\nLet's have a look at a web request example:\n```python\nfrom urllib.request import Request\n\n# Create your web request.\nurl = 'http://example.com'\n\nreq = Request(url)\nreq.add_header('header1', '1234')\nreq.add_header('header2', '5678')\n```\n\nAfter creating/setting up the request you have to create the tracer object and pass the parameters.\n\n```python\n# Create the tracer.\ntracer = sdk.trace_outgoing_web_request(url, req.get_method(), req.headers)\n```\n\nThe next step is to start the tracer and then to retrieve the outgoing Dynatrace tag. The tag is being used to trace a transaction from end-to-end.\nYou have to send the tag to the destination via an additional request header which is called\n[`DYNATRACE_HTTP_HEADER_NAME`](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.common.DYNATRACE_HTTP_HEADER_NAME).\n[Here you can find more information on tagging](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/tagging.html).\n\n```python\nwith tracer:\n\t# Get and set the Dynatrace tag.\n\ttag = tracer.outgoing_dynatrace_string_tag\n \treq.add_header(DYNATRACE_HTTP_HEADER_NAME, tag)\n\n\t# Here you process and send the web request.\n\tresponse = _process_your_outgoing_request(req)\n```\n\nFinally, get the response headers you want to trace and the status code of the response and add them to the tracer.\n\n```python\n        tracer.add_response_headers({'Content-Length': response.get_content_length()})\n        tracer.set_status_code(response.get_status_code())\n```\n\nBe sure to check out the documentation:\n* [`trace_outgoing_web_request`](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.sdk.SDK.trace_outgoing_web_request)\n* [`OutgoingWebRequestTracer`](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.sdk.tracers.OutgoingWebRequestTracer)\n* [General information on tagging](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/tagging.html)\n\n\n\u003ca name=\"trace-in-process-asynchronous-execution\"\u003e\u003c/a\u003e\n### Trace in-process asynchronous execution\n\nYou can use the SDK to trace asynchronous in-process code execution. This might be useful if the OneAgent does not support the threading framework\nor specific asynchronous libraries. In-process linking should be used to link other services (Database, Webrequests, ...) between thread or\nqueueing boundaries currently not supported out-of-the-box by the OneAgent.\n\nTo link asynchronous execution, you need to create an in-process link, where the execution forks:\n\n```python\nin_process_link = sdk.create_in_process_link()\n```\n\nThe provided in-process link must not be serialized and can only be used inside the process in which it was created. It must be used to start\ntracing where the asynchronous execution takes place:\n\n```python\nwith sdk.trace_in_process_link(in_process_link):\n \t# Do the asynchronous job\n \t:\n```\n\n\u003ca name=\"custom-request-attributes\"\u003e\u003c/a\u003e\n### Custom Request Attributes\n\nYou can use the SDK to add custom request attributes to the currently traced service. Custom request attributes allow you to do easier/better\nfiltering of your requests in Dynatrace.\n\nAdding custom request attributes to the currently traced service call is pretty simple. Just call the `add_custom_request_attribute` method\nwith your key and value (only int, float and string values are currently supported):\n\n```python\nsdk.add_custom_request_attribute('errorCount', 42)\nsdk.add_custom_request_attribute('gross weight', 2.39)\nsdk.add_custom_request_attribute('famous actor', 'Benedict Cumberbatch')\n```\n\nCheck out the documentation at:\n* [`add_custom_request_attribute`](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.sdk.SDK.add_custom_request_attribute)\n\n\n\u003ca name=\"custom-services\"\u003e\u003c/a\u003e\n### Custom services\nYou can use the SDK to trace custom service methods. A custom service method is a meaningful part\nof your code that you want to trace but that does not fit any other tracer. An example could be\nthe callback of a periodic timer.\n\n```python\nwith sdk.trace_custom_service('onTimer', 'CleanupTask'):\n\t# Do the cleanup task\n```\n\nCheck out the documentation at:\n* [`trace_custom_service`](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.sdk.SDK.trace_custom_service)\n\n\n\u003ca name=\"messaging\"\u003e\u003c/a\u003e\n### Messaging\n\nYou can use the SDK to trace messages sent or received via a messaging system. When tracing messages,\nwe distinguish between:\n\n* sending a message\n* waiting for and receiving a message\n* processing a received message\n\n\u003ca name=\"outgoing-messaging\"\u003e\u003c/a\u003e\n#### Outgoing Messages\n\nAll messaging related tracers need a messaging system info object which you have to create prior\nto the respective messaging tracer, which is an outgoing message tracer in the example below.\n\n```python\nmsi_handle = sdk.create_messaging_system_info(\n\t'myMessagingSystem', 'requestQueue', MessagingDestinationType.QUEUE,\n\toneagent.sdk.Channel(oneagent.sdk.ChannelType.TCP_IP, '10.11.12.13'))\n\nwith msi_handle:\n\twith sdk.trace_outgoing_message(msi_handle) as tracer:\n\t\t# Get and set the Dynatrace tag.\n\t\ttag = tracer.outgoing_dynatrace_string_tag\n\t\tmessage_to_send.add_header_field(oneagent.sdk.DYNATRACE_MESSAGE_PROPERTY_NAME, tag)\n\n\t\t# Send the message.\n\t\tthe_queue.send(message_to_send)\n\n\t\t# Optionally set message and/or correlation IDs\n\t\ttracer.set_vendor_message_id(message_to_send.get_message_id())\n\t\ttracer.set_correlation_id(message_to_send.get_correlation_id())\n```\n\n\u003ca name=\"incoming-messaging\"\u003e\u003c/a\u003e\n#### Incoming Messages\n\nOn the incoming side, we need to differentiate between the blocking receiving part and processing\nthe received message. Therefore two different tracers are being used:\n\n* IncomingMessageReceiveTracer\n* IncomingMessageProcessTracer\n\n```python\nmsi_handle = sdk.create_messaging_system_info(\n\t'myMessagingSystem', 'requestQueue', MessagingDestinationType.QUEUE,\n\toneagent.sdk.Channel(oneagent.sdk.ChannelType.TCP_IP, '10.11.12.13'))\n\nwith msi_handle:\n\t# Create the receive tracer for incoming messages.\n\twith sdk.trace_incoming_message_receive(msi_handle):\n\t\t# This is a blocking call, which will return as soon as a message is available.\n\t\tMessage query_message = the_queue.receive()\n\n\t\t# Get the Dynatrace tag from the message.\n\t\ttag = query_message.get_header_field(oneagent.sdk.DYNATRACE_MESSAGE_PROPERTY_NAME)\n\n\t\t# Create the tracer for processing incoming messages.\n\t\ttracer = sdk.trace_incoming_message_process(msi_handle, str_tag=tag)\n\t\ttracer.set_vendor_message_id(query_message.get_vendor_id())\n\t\ttracer.set_correlation_id(query_message.get_correlation_id())\n\n\t\twith tracer:\n\t\t\t# Now let's handle the message ...\n\t\t\tprint('handle incoming message')\n```\n\nIn case of non-blocking receive (e. g. using an event handler), there is no need to use an\nIncomingMessageReceiveTracer - just trace processing of the message by using the IncomingMessageProcessTracer:\n\n```python\nmsi_handle = sdk.create_messaging_system_info(\n\t'myMessagingSystem', 'requestQueue', MessagingDestinationType.QUEUE,\n\toneagent.sdk.Channel(oneagent.sdk.ChannelType.TCP_IP, '10.11.12.13'))\n\ndef on_message_received(message):\n\t# Get the Dynatrace tag from the message.\n\ttag = message.get_header_field(oneagent.sdk.DYNATRACE_MESSAGE_PROPERTY_NAME)\n\n\t# Create the tracer for processing incoming messages.\n\ttracer = sdk.trace_incoming_message_process(msi_handle, str_tag=tag)\n\ttracer.set_vendor_message_id(message.get_vendor_id())\n\ttracer.set_correlation_id(message.get_correlation_id())\n\n\twith tracer:\n\t\t# Now let's handle the message ...\n\t\tprint('handle incoming message')\n```\n\nSee the documentation for more information:\n\n* [`create_messaging_system_info`](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.sdk.SDK.create_messaging_system_info)\n* [`trace_outgoing_message`](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.sdk.tracers.trace_outgoing_message)\n* [`trace_incoming_message_receive`](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.sdk.tracers.trace_incoming_message_receive)\n* [`trace_incoming_message_process`](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.sdk.tracers.trace_incoming_message_process)\n* [General information on tagging](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/tagging.html)\n* [Messaging tracers in the specification repository](https://github.com/Dynatrace/OneAgent-SDK#messaging)\n\n\u003ca name=\"w3c-trace-context\"\u003e\u003c/a\u003e\n## W3C trace context\n\nThis feature allows you to retrieve a W3C TraceContext trace ID and span ID referencing the current PurePath node,\nas defined in \u003chttps://www.w3.org/TR/trace-context\u003e.\n\nThis trace ID and span ID information is not intended for tagging and\ncontext-propagation scenarios and primarily designed for log-enrichment use\ncases. Refer to [General information on tagging](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/tagging.html)\nfor tagging traces (see also the usage examples elsewhere in this document).\n\nThe following example shows how to print the current trace \u0026 span ID to stdout\nin a format that works well with Dynatrace Log Monitoring\n(see \u003chttps://www.dynatrace.com/support/help/shortlink/log-monitoring-log-enrichment\u003e for more):\n\n```python\nwith sdk.trace_custom_service('onTimer', 'CleanupTask'): # Or any other tracer\n\ttinfo = sdk.tracecontext_get_current()\n\tprint('[!dt dt.trace_id={},dt.span_id={}] handle incoming message'.format(tinfo.trace_id, tinfo.span_id))\n```\n\nSee the documentation for more information:\n\n* [`tracecontext_get_current`](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/sdkref.html#oneagent.sdk.SDK.tracecontext_get_current)\n* [Information on trace tagging](https://dynatrace.github.io/OneAgent-SDK-for-Python/docs/tagging.html)\n* [W3C trace context in the SDK specification repository](https://github.com/Dynatrace/OneAgent-SDK#tracecontext)\n\n\n\n\u003ca name=\"forking\"\u003e\u003c/a\u003e\n\u003ca name=\"using-the-oneagent-sdk-for-python-with-forked-child-processes-only-available-on-linux\"\u003e\u003c/a\u003e\n## Using the OneAgent SDK for Python with forked child processes (only available on Linux)\n\nSome applications, especially web servers, use a concurrency model that is based on forked child processes.\nTypically a master process is started which is responsible only for creating and managing child processes by means of forking.\nThe child processes do the real work, for example handling web requests.\n\nThe recommended way to use the Python SDK in such a scenario is as follows: You initialize the SDK in the master process setting\nthe `forkable` argument to `True`.\n\n```python\noneagent.initialize(sdk_options, forkable=True)\n```\n\nThis way you will not be able to use the SDK in the master process (attempts to do so will be ignored, if applicable with\nan error code), but all forked child processes will share the same agent. This has a lower overhead, for example the\nstartup of worker processes is not slowed down, and the per-worker memory overhead is reduced.\n\nFor more information on forked child processes, take a look at those resources:\n* [Documentation on forking for the Dynatrace OneAgent SDK for C/C++](https://github.com/Dynatrace/OneAgent-SDK-for-C/blob/master/README.md#forking)\n* [Forking sample application](./samples/fork-sdk-sample/fork_sdk_sample.py)\n\n\u003ca name=\"troubleshooting\"\u003e\u003c/a\u003e\n## Troubleshooting\n\n\u003ca name=\"installation-issues\"\u003e\u003c/a\u003e\n\u003ca name=\"post-installation-issues\"\u003e\u003c/a\u003e\n\nTo debug your OneAgent SDK for Python installation, execute the following Python code:\n\n```python\nimport logging\nimport time\nimport oneagent\n\nlog_handler = logging.StreamHandler()\nlog_formatter = logging.Formatter(\n    '%(asctime)s.%(msecs)03d UTC [%(thread)08x]'\n    ' %(levelname)-7s [%(name)-6s] %(message)s',\n    '%Y-%m-%d %H:%M:%S')\nlog_formatter.converter = time.gmtime\nlog_handler.setFormatter(log_formatter)\noneagent.logger.addHandler(log_handler)\noneagent.logger.setLevel(1)\ninit_result = oneagent.initialize(['loglevelsdk=finest', 'loglevel=finest'])\nprint('InitResult=' + repr(init_result))\n```\n\nIf you get output containing `InitResult=InitResult(status=0, error=None)`, your installation should be fine. Otherwise, the output is helpful in\ndetermining the issue. The [extended SKD state](#extended-sdk-state) might also help to diagnose your problem.\n\nKnown gotchas:\n\n* `ImportError` or `ModuleNotFoundError` in line 1 that says that there is no module named `oneagent`.\n\n  Make sure that the `pip install` or equivalent succeeded (see [here](#installation)). Also make sure you use the `pip` corresponding to your\n  `python` (if in doubt, use `python -m pip` instead of `pip` for installing).\n\n* Output ending in a message like `InitResult=InitResult(status=-2, error=SDKError(-1342308345, 'Failed loading SDK stub from .../site-packages/oneagent/_impl/native/libonesdk_shared.so: \"/.../libonesdk_shared.so: cannot open shared object file: No such file or directory\". Check your installation of the oneagent-sdk Python package, e.g., try running `pip install --verbose --force-reinstall oneagent-sdk`.'))`.\n\n  Follow the advice of the message and run `python -m pip install --verbose --force-reinstall oneagent-sdk`\n  (or the equivalent pip invocation with the `--verbose` and `--force-reinstall` flags).\n  It is likely that you will now see another message like\n\n        ******************************************************************************\n        *** You are trying to build the Python SDK from source.                    ***\n        *** This could mean that you are using an outdated version of pip (older   ***\n        *** than 8.1.0) or you are attempting to install the SDK on an             ***\n        *** unsupported platform. Please check the requirements at                 ***\n        *** https://github.com/Dynatrace/OneAgent-SDK-for-Python#requirements      ***\n        ******************************************************************************\n\n  Make sure you are using pip to install a prebuilt package wheel for your system from PyPI, as described in [Using the OneAgent SDK for\n  Python in your application](#installation). Also make sure you are using an up-to date version of `pip`, `setuptools` and `wheel`. You can\n  try upgrading them with `python -m pip install --upgrade pip setuptools wheel` (make sure to use the same `python` that you use to install\n  the `oneagent-sdk` package). ATTENTION: If you use the system-provided pip (e.g. installed via `apt-get` on Ubuntu) you should instead use\n  a `pip` inside a `virtualenv` (the same as your project), as upgrading system-provided packages via `pip` may cause issues.\n\n  If this does not resolve the issue, make sure you are using a supported platform, as listed in [Requirements](#requirements). If you *are*\n  using a supported system, you can try downloading the [OneAgent SDK for C/C++](https://github.com/Dynatrace/OneAgent-SDK-for-C) in the\n  version corresponding to your OneAgent SDK for Python as listed in [the table in Requirements](#requirements). Then set the\n  `DT_PYSDK_CSDK_PATH` environment variable to the `.so`/`.dll` file corresponding to your platform in the `lib` subdirectory of the C SDK\n  and retry the installation (e.g. in a bash shell, use `export DT_PYSDK_CSDK_PATH=path/to/onesdk_shared.so`). If there is no corresponding\n  directory, your platform is not supported. Otherwise, regardless if it works with that method or not, please report an issue as described\n  in [Let us help you](#let-us-help-you).\n\n\u003ca name=\"extended-sdk-state\"\u003e\u003c/a\u003e\n### Extended SDK State\n\nFor debugging and/or diagnosing purposes you can also use the extended SDK state information.\n```python\n# The agent state is one of the integers in oneagent.sdk.AgentState.\nprint('Agent state:', oneagent.get_sdk().agent_state)\n\n# The instance attribute 'agent_found' indicates whether an agent could be found or not.\nprint('Agent found:', oneagent.get_sdk().agent_found)\n\n# If an agent was found but it is incompatible with this version of the SDK for Python\n# then 'agent_is_compatible' would be set to false.\nprint('Agent is compatible:', oneagent.get_sdk().agent_is_compatible)\n\n# The agent version is a string holding both the OneAgent version and the\n# OneAgent SDK for C/C++ version separated by a '/'.\nprint('Agent version:', oneagent.get_sdk().agent_version_string)\n```\n\u003ca name=\"shutdown-crashes\"\u003e\u003c/a\u003e\n### Shutdown crashes\n\nIf your are experiencing crashes when your application exits, make\nsure you uninitialized the SDK properly by calling its `shutdown`\nfunction.\n\n\u003ca name=\"repository-contents\"\u003e\u003c/a\u003e\n## Repository contents\n\nIf you are viewing the [GitHub repository](https://github.com/Dynatrace/OneAgent-SDK-for-Python), you will see:\n\n- `LICENSE`: License under which the whole SDK and sample applications are\n  published.\n- `src/`: Actual source code of the Python OneAgent SDK.\n- `docs/`: Source files for the ([Sphinx](https://sphinx-doc.org)-based) HTML\n  documentation. For the actual, readable documentation, see\n  [here](#documentation).\n- `tests/`, `test-util-src/`: Contains tests and test support files that are\n  useful (only) for developers wanting to contribute to the SDK itself.\n- `setup.py`, `setup.cfg`, `MANIFEST.in`, `project.toml`: Development files\n  required for creating e.g. the PyPI package for the Python OneAgent SDK.\n- `tox.ini`, `pylintrc`: Supporting files for developing the SDK itself. See\n  \u003chttps://tox.readthedocs.io/en/latest/\u003e and \u003chttps://www.pylint.org/\u003e.\n\n\u003ca name=\"help--support\"\u003e\u003c/a\u003e\n## Help \u0026 Support\n\n**Support policy**\n\nThe Dynatrace OneAgent SDK for Python has GA status. The features are fully supported by Dynatrace.\n\nFor detailed support policy see [Dynatrace OneAgent SDK help](https://github.com/Dynatrace/OneAgent-SDK#help).\n\n\u003ca name=\"documentation\"\u003e\u003c/a\u003e\n\u003ca name=\"read-the-manual\"\u003e\u003c/a\u003e\n### Read the manual\n\n* The most recent version of the documentation for the Python SDK can be viewed at\n\u003chttps://dynatrace.github.io/OneAgent-SDK-for-Python/\u003e.\n* A high level documentation/description of OneAgent SDK concepts is available at\n\u003chttps://github.com/Dynatrace/OneAgent-SDK/\u003e.\n* Of course, [this README](#) also contains lots of useful information.\n\n\u003ca name=\"let-us-help-you\"\u003e\u003c/a\u003e\n### Let us help you\n\nMake sure your issue is not already solved in the [available documentation](#documentation) before you ask for help. Especially the\n[troubleshooting section in this README](#troubleshooting) may prove helpful.\n\n**Get Help**\n* Ask a question in the [product forums](https://answers.dynatrace.com/spaces/482/view.html).\n* Read the \u003ca href=\"https://www.dynatrace.com/support/help/\" target=\"_blank\"\u003eproduct documentation\u003c/a\u003e\n\n**Open a [GitHub issue](https://github.com/Dynatrace/OneAgent-SDK-for-Python/issues) to:**\n  * Report minor defects or typos.\n  * Ask any questions related to the community effort.\n\nSLAs don't apply for GitHub tickets.\n\n**Customers can open a ticket on the \u003ca href=\"https://support.dynatrace.com/supportportal/\" target=\"_blank\"\u003eDynatrace support portal\u003c/a\u003e to:**\n* Get support from the Dynatrace technical support engineering team\n* Manage and resolve product related technical issues\n\nSLAs apply according to the customer's support level.\n\n\u003ca name=\"release-notes\"\u003e\u003c/a\u003e\n\u003ca name=\"release-notes-and-announcements\"\u003e\u003c/a\u003e\n## Release notes and announcements\n\nFor additional updates, see also [OneAgent release notes](https://docs.dynatrace.com/docs/shortlink/release-notes-oneagent)\nand [End of support announcements](https://docs.dynatrace.com/docs/shortlink/eos-announcements#dynatrace-oneagent).\n\n\n### Announcements in November 2023\n\n* ⚠️ **Deprecation announcement for older SDK versions:** Version 1.4 has been put on the path to deprecation and will no longer be supported starting June 1, 2024. Only version 1.5 of the SDK (or any newer version) will be supported from that date on.\n* ⚠️ **Deprecation announcement for using any SDK version with older Python versions:** SDK support for Python 3.4.x, 3.5.x, 3.6.x and 3.7.x has been put on the path to deprecation and no version of the SDK will be supported on Python 3.4.x, 3.5.x and 3.6.x starting June 1, 2024.\n  Usage of the SDK on 3.7.x will remain supported until September 1, 2024.\n  All Python versions below 3.8.x are already declared End of Life by the Python.org project, and customers are encouraged to upgrade to a newer Python version that is also supported by Python.org.\n\n### Version 1.5.1\n\nChanges:\n\n* Fixes support of Python 3.12 and newer\n\n### Version 1.5.0\n\nChanges:\n\n* Adds limited [W3C trace context](#w3c-trace-context) support (for log enrichment).\n* This version **no longer supports Python 2 (Python 2.7.x)**.\n* This version **no longer supports Python 3.4.x**.\n\nAnnouncements:\n\n* ⚠️ **Deprecation announcement for older SDK versions:** Version 1.3 and all older versions have been put on the path to deprecation and will no longer be supported starting July 1, 2023. We strongly advise customers to upgrade to newest versions to avoid incompatibility and security risks. Customers need to upgrade to at least 1.4 but are encouraged to upgrade to the newest available version (1.5) if using Python \u003e3.4 as there are no known incompatibilities or breaking changes other than the increased minimum Python version.\n* ⚠️ **Deprecation announcement for using any SDK version with older Python versions:** Python 2.7.x has been put on the path to deprecation and no version of the SDK will be supported on this Python version starting July 1, 2023. Furthermore, we intend to release a similar deprecation announcement regarding versions 3.4-3.6 (which are no longer maintained by the Python project) soon (we plan that this will not become effective before 2023-07-01).\n\nSee \u003chttps://github.com/Dynatrace/OneAgent-SDK-for-Python/releases\u003e for older releases.\n\n\u003ca name=\"license\"\u003e\u003c/a\u003e\n## License\n\nSee the LICENSE file for details. It should be included in your distribution.\nOtherwise, see the most recent version on\n[GitHub](https://github.com/Dynatrace/OneAgent-SDK-for-Python/blob/master/LICENSE).\n\nSummary: This software is licensed under the terms of the Apache License Version\n2.0 and comes bundled with the [six library by Benjamin\nPeterson](http://six.readthedocs.io/), which is licensed under the terms of the\nMIT license.\n\n\u003c!-- vim: set tw=140 linebreak: --\u003e\n","funding_links":[],"categories":[],"sub_categories":[],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdynatrace%2Foneagent-sdk-for-python","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fdynatrace%2Foneagent-sdk-for-python","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fdynatrace%2Foneagent-sdk-for-python/lists"}