diff options
| -rw-r--r-- | .gitignore | 1 | ||||
| -rw-r--r-- | python-celery-opentracing.spec | 228 | ||||
| -rw-r--r-- | sources | 1 |
3 files changed, 230 insertions, 0 deletions
@@ -0,0 +1 @@ +/Celery-OpenTracing-0.0.1.tar.gz diff --git a/python-celery-opentracing.spec b/python-celery-opentracing.spec new file mode 100644 index 0000000..10ec350 --- /dev/null +++ b/python-celery-opentracing.spec @@ -0,0 +1,228 @@ +%global _empty_manifest_terminate_build 0 +Name: python-Celery-OpenTracing +Version: 0.0.1 +Release: 1 +Summary: OpenTracing support for Celery +License: Apache Software License v2 +URL: http://github.com/signalfx/python-celery +Source0: https://mirrors.nju.edu.cn/pypi/web/packages/7c/b3/8ab55641fb3b9ebbd8bf5e71b5f6bc79f43e0be1afc350657f07c426d2a1/Celery-OpenTracing-0.0.1.tar.gz +BuildArch: noarch + + +%description +# Celery OpenTracing + +This package enables tracing task execution in a [Celery 3.1+](http://www.celeryproject.org/) application via [The OpenTracing Project](http://opentracing.io). Once a production system contends with real concurrency or splits into many services, crucial (and formerly easy) tasks become difficult: user-facing latency optimization, root-cause analysis of backend errors, communication about distinct pieces of a now-distributed system, etc. Distributed tracing follows a request on its journey from inception to completion from mobile/browser all the way to the microservices. + +As core services and libraries adopt OpenTracing, the application builder is no longer burdened with the task of adding basic tracing instrumentation to their own code. In this way, developers can build their applications with the tools they prefer and benefit from built-in tracing instrumentation. OpenTracing implementations exist for major distributed tracing systems and can be bound or swapped with a one-line configuration change. + +If you want to learn more about the underlying Python API, visit the Python [source code](https://github.com/signalfx/python-celery/). + +## Installation + +Run the following command: + +``` +$ pip install celery-opentracing +``` + +## Usage + +The provided `celery.app.base.Celery` subclass allows the tracing of task scheduling and execution using the OpenTracing API. All that it requires is for a `CeleryTracing` instance to be initialized using an instance of an OpenTracing tracer and treated as a standard `Celery` application. + +### Initialize + +`CeleryTracing` takes the `Tracer` instance that is supported by OpenTracing and an optional dictionary of desired tags for each created span. You can also specify whether you'd like the initial task publish events to be represented by a span whose trace context is propagated via request headers to the worker executing the task (enabled by default). To create a `CeleryTracing` object, you can either pass in a tracer object directly or default to the `opentracing.tracer` global tracer that's set elsewhere in your application: + +```python +from celery_opentracing import CeleryTracing + +opentracing_tracer = # some OpenTracing tracer implementation +traced_app = CeleryTracing(tracer=opentracing_tracer, propagate=True, # propagation allows distributed tracing from + span_tags=dict(my_helpful='tag')) # publisher over broker to workers. + +@traced_app.task(bind=True) +def my_task(self): + return True +``` + +or + +```python +from celery_opentracing import CeleryTracing +import opentracing + +opentracing.tracer = # some OpenTracing tracer implementation +traced_app = CeleryTracing(propagate=False) # Tracer defaults to opentracing.tracer. No publish span creation or propagation to worker execution context will configured as well. + +@traced_app.task(bind=True) +def my_task(self): + return True +``` + +## Further Information + +If you're interested in learning more about the OpenTracing standard, please visit [opentracing.io](http://opentracing.io/). If you would like to implement OpenTracing in your project and need help, feel free to send us a note at [community@opentracing.io](community@opentracing.io). + +%package -n python3-Celery-OpenTracing +Summary: OpenTracing support for Celery +Provides: python-Celery-OpenTracing +BuildRequires: python3-devel +BuildRequires: python3-setuptools +BuildRequires: python3-pip +%description -n python3-Celery-OpenTracing +# Celery OpenTracing + +This package enables tracing task execution in a [Celery 3.1+](http://www.celeryproject.org/) application via [The OpenTracing Project](http://opentracing.io). Once a production system contends with real concurrency or splits into many services, crucial (and formerly easy) tasks become difficult: user-facing latency optimization, root-cause analysis of backend errors, communication about distinct pieces of a now-distributed system, etc. Distributed tracing follows a request on its journey from inception to completion from mobile/browser all the way to the microservices. + +As core services and libraries adopt OpenTracing, the application builder is no longer burdened with the task of adding basic tracing instrumentation to their own code. In this way, developers can build their applications with the tools they prefer and benefit from built-in tracing instrumentation. OpenTracing implementations exist for major distributed tracing systems and can be bound or swapped with a one-line configuration change. + +If you want to learn more about the underlying Python API, visit the Python [source code](https://github.com/signalfx/python-celery/). + +## Installation + +Run the following command: + +``` +$ pip install celery-opentracing +``` + +## Usage + +The provided `celery.app.base.Celery` subclass allows the tracing of task scheduling and execution using the OpenTracing API. All that it requires is for a `CeleryTracing` instance to be initialized using an instance of an OpenTracing tracer and treated as a standard `Celery` application. + +### Initialize + +`CeleryTracing` takes the `Tracer` instance that is supported by OpenTracing and an optional dictionary of desired tags for each created span. You can also specify whether you'd like the initial task publish events to be represented by a span whose trace context is propagated via request headers to the worker executing the task (enabled by default). To create a `CeleryTracing` object, you can either pass in a tracer object directly or default to the `opentracing.tracer` global tracer that's set elsewhere in your application: + +```python +from celery_opentracing import CeleryTracing + +opentracing_tracer = # some OpenTracing tracer implementation +traced_app = CeleryTracing(tracer=opentracing_tracer, propagate=True, # propagation allows distributed tracing from + span_tags=dict(my_helpful='tag')) # publisher over broker to workers. + +@traced_app.task(bind=True) +def my_task(self): + return True +``` + +or + +```python +from celery_opentracing import CeleryTracing +import opentracing + +opentracing.tracer = # some OpenTracing tracer implementation +traced_app = CeleryTracing(propagate=False) # Tracer defaults to opentracing.tracer. No publish span creation or propagation to worker execution context will configured as well. + +@traced_app.task(bind=True) +def my_task(self): + return True +``` + +## Further Information + +If you're interested in learning more about the OpenTracing standard, please visit [opentracing.io](http://opentracing.io/). If you would like to implement OpenTracing in your project and need help, feel free to send us a note at [community@opentracing.io](community@opentracing.io). + +%package help +Summary: Development documents and examples for Celery-OpenTracing +Provides: python3-Celery-OpenTracing-doc +%description help +# Celery OpenTracing + +This package enables tracing task execution in a [Celery 3.1+](http://www.celeryproject.org/) application via [The OpenTracing Project](http://opentracing.io). Once a production system contends with real concurrency or splits into many services, crucial (and formerly easy) tasks become difficult: user-facing latency optimization, root-cause analysis of backend errors, communication about distinct pieces of a now-distributed system, etc. Distributed tracing follows a request on its journey from inception to completion from mobile/browser all the way to the microservices. + +As core services and libraries adopt OpenTracing, the application builder is no longer burdened with the task of adding basic tracing instrumentation to their own code. In this way, developers can build their applications with the tools they prefer and benefit from built-in tracing instrumentation. OpenTracing implementations exist for major distributed tracing systems and can be bound or swapped with a one-line configuration change. + +If you want to learn more about the underlying Python API, visit the Python [source code](https://github.com/signalfx/python-celery/). + +## Installation + +Run the following command: + +``` +$ pip install celery-opentracing +``` + +## Usage + +The provided `celery.app.base.Celery` subclass allows the tracing of task scheduling and execution using the OpenTracing API. All that it requires is for a `CeleryTracing` instance to be initialized using an instance of an OpenTracing tracer and treated as a standard `Celery` application. + +### Initialize + +`CeleryTracing` takes the `Tracer` instance that is supported by OpenTracing and an optional dictionary of desired tags for each created span. You can also specify whether you'd like the initial task publish events to be represented by a span whose trace context is propagated via request headers to the worker executing the task (enabled by default). To create a `CeleryTracing` object, you can either pass in a tracer object directly or default to the `opentracing.tracer` global tracer that's set elsewhere in your application: + +```python +from celery_opentracing import CeleryTracing + +opentracing_tracer = # some OpenTracing tracer implementation +traced_app = CeleryTracing(tracer=opentracing_tracer, propagate=True, # propagation allows distributed tracing from + span_tags=dict(my_helpful='tag')) # publisher over broker to workers. + +@traced_app.task(bind=True) +def my_task(self): + return True +``` + +or + +```python +from celery_opentracing import CeleryTracing +import opentracing + +opentracing.tracer = # some OpenTracing tracer implementation +traced_app = CeleryTracing(propagate=False) # Tracer defaults to opentracing.tracer. No publish span creation or propagation to worker execution context will configured as well. + +@traced_app.task(bind=True) +def my_task(self): + return True +``` + +## Further Information + +If you're interested in learning more about the OpenTracing standard, please visit [opentracing.io](http://opentracing.io/). If you would like to implement OpenTracing in your project and need help, feel free to send us a note at [community@opentracing.io](community@opentracing.io). + +%prep +%autosetup -n Celery-OpenTracing-0.0.1 + +%build +%py3_build + +%install +%py3_install +install -d -m755 %{buildroot}/%{_pkgdocdir} +if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi +if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi +if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi +if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi +pushd %{buildroot} +if [ -d usr/lib ]; then + find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/lib64 ]; then + find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/bin ]; then + find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst +fi +if [ -d usr/sbin ]; then + find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst +fi +touch doclist.lst +if [ -d usr/share/man ]; then + find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst +fi +popd +mv %{buildroot}/filelist.lst . +mv %{buildroot}/doclist.lst . + +%files -n python3-Celery-OpenTracing -f filelist.lst +%dir %{python3_sitelib}/* + +%files help -f doclist.lst +%{_docdir}/* + +%changelog +* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 0.0.1-1 +- Package Spec generated @@ -0,0 +1 @@ +b8dcbf2d169d0f67db741416cd92561f Celery-OpenTracing-0.0.1.tar.gz |