229 lines
9.3 KiB
Plaintext
229 lines
9.3 KiB
Plaintext
Metadata-Version: 2.1
|
|
Name: google-cloud-trace
|
|
Version: 1.16.1
|
|
Summary: Google Cloud Trace API client library
|
|
Home-page: https://github.com/googleapis/google-cloud-python/tree/main/packages/google-cloud-trace
|
|
Author: Google LLC
|
|
Author-email: googleapis-packages@google.com
|
|
License: Apache 2.0
|
|
Platform: Posix; MacOS X; Windows
|
|
Classifier: Development Status :: 5 - Production/Stable
|
|
Classifier: Intended Audience :: Developers
|
|
Classifier: License :: OSI Approved :: Apache Software License
|
|
Classifier: Programming Language :: Python
|
|
Classifier: Programming Language :: Python :: 3
|
|
Classifier: Programming Language :: Python :: 3.7
|
|
Classifier: Programming Language :: Python :: 3.8
|
|
Classifier: Programming Language :: Python :: 3.9
|
|
Classifier: Programming Language :: Python :: 3.10
|
|
Classifier: Programming Language :: Python :: 3.11
|
|
Classifier: Programming Language :: Python :: 3.12
|
|
Classifier: Programming Language :: Python :: 3.13
|
|
Classifier: Operating System :: OS Independent
|
|
Classifier: Topic :: Internet
|
|
Requires-Python: >=3.7
|
|
License-File: LICENSE
|
|
Requires-Dist: google-api-core[grpc]!=2.0.*,!=2.1.*,!=2.10.*,!=2.2.*,!=2.3.*,!=2.4.*,!=2.5.*,!=2.6.*,!=2.7.*,!=2.8.*,!=2.9.*,<3.0.0,>=1.34.1
|
|
Requires-Dist: google-auth!=2.24.0,!=2.25.0,<3.0.0,>=2.14.1
|
|
Requires-Dist: proto-plus<2.0.0,>=1.22.3
|
|
Requires-Dist: protobuf!=4.21.0,!=4.21.1,!=4.21.2,!=4.21.3,!=4.21.4,!=4.21.5,<7.0.0,>=3.20.2
|
|
Requires-Dist: proto-plus<2.0.0,>=1.25.0; python_version >= "3.13"
|
|
|
|
Python Client for Cloud Trace
|
|
=============================
|
|
|
|
|stable| |pypi| |versions|
|
|
|
|
`Cloud Trace`_: is a distributed tracing system that collects latency data from your applications and displays it in the Google Cloud Platform Console. You can track how requests propagate through your application and receive detailed near real-time performance insights.
|
|
|
|
- `Client Library Documentation`_
|
|
- `Product Documentation`_
|
|
|
|
.. |stable| image:: https://img.shields.io/badge/support-stable-gold.svg
|
|
:target: https://github.com/googleapis/google-cloud-python/blob/main/README.rst#stability-levels
|
|
.. |pypi| image:: https://img.shields.io/pypi/v/google-cloud-trace.svg
|
|
:target: https://pypi.org/project/google-cloud-trace/
|
|
.. |versions| image:: https://img.shields.io/pypi/pyversions/google-cloud-trace.svg
|
|
:target: https://pypi.org/project/google-cloud-trace/
|
|
.. _Cloud Trace: https://cloud.google.com/trace/docs
|
|
.. _Client Library Documentation: https://cloud.google.com/python/docs/reference/cloudtrace/latest/summary_overview
|
|
.. _Product Documentation: https://cloud.google.com/trace/docs
|
|
|
|
Quick Start
|
|
-----------
|
|
|
|
In order to use this library, you first need to go through the following steps:
|
|
|
|
1. `Select or create a Cloud Platform project.`_
|
|
2. `Enable billing for your project.`_
|
|
3. `Enable the Cloud Trace.`_
|
|
4. `Set up Authentication.`_
|
|
|
|
.. _Select or create a Cloud Platform project.: https://console.cloud.google.com/project
|
|
.. _Enable billing for your project.: https://cloud.google.com/billing/docs/how-to/modify-project#enable_billing_for_a_project
|
|
.. _Enable the Cloud Trace.: https://cloud.google.com/trace/docs
|
|
.. _Set up Authentication.: https://googleapis.dev/python/google-api-core/latest/auth.html
|
|
|
|
Installation
|
|
~~~~~~~~~~~~
|
|
|
|
Install this library in a virtual environment using `venv`_. `venv`_ is a tool that
|
|
creates isolated Python environments. These isolated environments can have separate
|
|
versions of Python packages, which allows you to isolate one project's dependencies
|
|
from the dependencies of other projects.
|
|
|
|
With `venv`_, it's possible to install this library without needing system
|
|
install permissions, and without clashing with the installed system
|
|
dependencies.
|
|
|
|
.. _`venv`: https://docs.python.org/3/library/venv.html
|
|
|
|
|
|
Code samples and snippets
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
Code samples and snippets live in the `samples/`_ folder.
|
|
|
|
.. _samples/: https://github.com/googleapis/google-cloud-python/tree/main/packages/google-cloud-trace/samples
|
|
|
|
|
|
Supported Python Versions
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
Our client libraries are compatible with all current `active`_ and `maintenance`_ versions of
|
|
Python.
|
|
|
|
Python >= 3.7
|
|
|
|
.. _active: https://devguide.python.org/devcycle/#in-development-main-branch
|
|
.. _maintenance: https://devguide.python.org/devcycle/#maintenance-branches
|
|
|
|
Unsupported Python Versions
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
Python <= 3.6
|
|
|
|
If you are using an `end-of-life`_
|
|
version of Python, we recommend that you update as soon as possible to an actively supported version.
|
|
|
|
.. _end-of-life: https://devguide.python.org/devcycle/#end-of-life-branches
|
|
|
|
Mac/Linux
|
|
^^^^^^^^^
|
|
|
|
.. code-block:: console
|
|
|
|
python3 -m venv <your-env>
|
|
source <your-env>/bin/activate
|
|
pip install google-cloud-trace
|
|
|
|
|
|
Windows
|
|
^^^^^^^
|
|
|
|
.. code-block:: console
|
|
|
|
py -m venv <your-env>
|
|
.\<your-env>\Scripts\activate
|
|
pip install google-cloud-trace
|
|
|
|
Next Steps
|
|
~~~~~~~~~~
|
|
|
|
- Read the `Client Library Documentation`_ for Cloud Trace
|
|
to see other available methods on the client.
|
|
- Read the `Cloud Trace Product documentation`_ to learn
|
|
more about the product and see How-to Guides.
|
|
- View this `README`_ to see the full list of Cloud
|
|
APIs that we cover.
|
|
|
|
.. _Cloud Trace Product documentation: https://cloud.google.com/trace/docs
|
|
.. _README: https://github.com/googleapis/google-cloud-python/blob/main/README.rst
|
|
|
|
Logging
|
|
-------
|
|
|
|
This library uses the standard Python :code:`logging` functionality to log some RPC events that could be of interest for debugging and monitoring purposes.
|
|
Note the following:
|
|
|
|
#. Logs may contain sensitive information. Take care to **restrict access to the logs** if they are saved, whether it be on local storage or on Google Cloud Logging.
|
|
#. Google may refine the occurrence, level, and content of various log messages in this library without flagging such changes as breaking. **Do not depend on immutability of the logging events**.
|
|
#. By default, the logging events from this library are not handled. You must **explicitly configure log handling** using one of the mechanisms below.
|
|
|
|
Simple, environment-based configuration
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
To enable logging for this library without any changes in your code, set the :code:`GOOGLE_SDK_PYTHON_LOGGING_SCOPE` environment variable to a valid Google
|
|
logging scope. This configures handling of logging events (at level :code:`logging.DEBUG` or higher) from this library in a default manner, emitting the logged
|
|
messages in a structured format. It does not currently allow customizing the logging levels captured nor the handlers, formatters, etc. used for any logging
|
|
event.
|
|
|
|
A logging scope is a period-separated namespace that begins with :code:`google`, identifying the Python module or package to log.
|
|
|
|
- Valid logging scopes: :code:`google`, :code:`google.cloud.asset.v1`, :code:`google.api`, :code:`google.auth`, etc.
|
|
- Invalid logging scopes: :code:`foo`, :code:`123`, etc.
|
|
|
|
**NOTE**: If the logging scope is invalid, the library does not set up any logging handlers.
|
|
|
|
Environment-Based Examples
|
|
^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
|
- Enabling the default handler for all Google-based loggers
|
|
|
|
.. code-block:: console
|
|
|
|
export GOOGLE_SDK_PYTHON_LOGGING_SCOPE=google
|
|
|
|
- Enabling the default handler for a specific Google module (for a client library called :code:`library_v1`):
|
|
|
|
.. code-block:: console
|
|
|
|
export GOOGLE_SDK_PYTHON_LOGGING_SCOPE=google.cloud.library_v1
|
|
|
|
|
|
Advanced, code-based configuration
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
You can also configure a valid logging scope using Python's standard `logging` mechanism.
|
|
|
|
Code-Based Examples
|
|
^^^^^^^^^^^^^^^^^^^
|
|
|
|
- Configuring a handler for all Google-based loggers
|
|
|
|
.. code-block:: python
|
|
|
|
import logging
|
|
|
|
from google.cloud.translate_v3 import translate
|
|
|
|
base_logger = logging.getLogger("google")
|
|
base_logger.addHandler(logging.StreamHandler())
|
|
base_logger.setLevel(logging.DEBUG)
|
|
|
|
- Configuring a handler for a specific Google module (for a client library called :code:`library_v1`):
|
|
|
|
.. code-block:: python
|
|
|
|
import logging
|
|
|
|
from google.cloud.translate_v3 import translate
|
|
|
|
base_logger = logging.getLogger("google.cloud.library_v1")
|
|
base_logger.addHandler(logging.StreamHandler())
|
|
base_logger.setLevel(logging.DEBUG)
|
|
|
|
Logging details
|
|
~~~~~~~~~~~~~~~
|
|
|
|
#. Regardless of which of the mechanisms above you use to configure logging for this library, by default logging events are not propagated up to the root
|
|
logger from the `google`-level logger. If you need the events to be propagated to the root logger, you must explicitly set
|
|
:code:`logging.getLogger("google").propagate = True` in your code.
|
|
#. You can mix the different logging configurations above for different Google modules. For example, you may want use a code-based logging configuration for
|
|
one library, but decide you need to also set up environment-based logging configuration for another library.
|
|
|
|
#. If you attempt to use both code-based and environment-based configuration for the same module, the environment-based configuration will be ineffectual
|
|
if the code -based configuration gets applied first.
|
|
|
|
#. The Google-specific logging configurations (default handlers for environment-based configuration; not propagating logging events to the root logger) get
|
|
executed the first time *any* client library is instantiated in your application, and only if the affected loggers have not been previously configured.
|
|
(This is the reason for 2.i. above.)
|