Description
The Celery integration installation steps are pretty outdated.
I've worked out that I can configure it this way with autodiscovery as follows on a Deployment hosting Celery Flower:
metadata:
name: celery-flower
spec:
replicas: 2
template:
metadata:
annotations:
ad.datadoghq.com/celery-flower.checks: |
{
"celery": {
"init_config": {},
"instances": [
{
"openmetrics_endpoint": "http://%%host%%:%%port%%/metrics",
"metrics": [
".*"
]
}
]
}
}
My datadog agent complains about this integration:
Error: {
"Core Check Loader": "Check celery not found in Catalog",
"Python Check Loader": "unable to import module 'celery': No module named 'celery'"
}
I have also tried to set this at the node agent level pointing to a Service like this:
apiVersion: datadoghq.com/v2alpha1
kind: DatadogAgent
metadata:
name: datadog
namespace: datadog-system
spec:
override:
nodeAgent:
extraConfd:
configDataMap:
celery.yaml: |-
init_config: {}
instances:
- openmetrics_endpoint: http://celery-flower.default.svc.cluster.local:5555/metrics
This resulted in the same issue.
I can update the autodiscovery config like this to make the metrics part of the openmetrics check, but this is not what I want since I am trying to get the data into the celery integration for use with the Data Streams Monitoring product line:
{
"openmetrics": {
"init_config": {},
"instances": [
{
"openmetrics_endpoint": "http://%%host%%:%%port%%/metrics",
....
Please advise. Not sure how I am to install the Celery module on the agent since the documentation for the integration states:
The Celery check is included in the Datadog Agent package. No additional installation is needed on your server.