Skip to content

[celery] Documentation Fixes #548

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 30, 2018
Merged

[celery] Documentation Fixes #548

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 2 additions & 8 deletions ddtrace/contrib/celery/__init__.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
The Celery integration will trace all tasks that are executed in the
background. Functions and class based tasks are traced only if the Celery API
is used, so calling the function directly or via the ``run()`` method will not
generate traces. On the other hand, calling ``apply()``, ``apply_async()`` and ``delay()``
generate traces. However, calling ``apply()``, ``apply_async()`` and ``delay()``
will produce tracing data. To trace your Celery application, call the patch method::

import celery
Expand All @@ -22,13 +22,7 @@ def run(self):

To change Celery service name, you can use the ``Config`` API as follows::

from ddtrace import Pin

app = celery.Celery()

@app.task
def compute_stats():
pass
from ddtrace import config

# change service names for producers and workers
config.celery['producer_service_name'] = 'task-queue'
Expand Down