[airflow_otel] add new content pack#17786
Conversation
Vale Linting ResultsSummary: 2 warnings found
|
| File | Line | Rule | Message |
|---|---|---|---|
| packages/airflow_otel/docs/README.md | 3 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'. |
| packages/airflow_otel/docs/README.md | 21 | Elastic.Latinisms | Latin terms and abbreviations are a common source of confusion. Use 'using' instead of 'via'. |
The Vale linter checks documentation changes against the Elastic Docs style guide.
To use Vale locally or report issues, refer to Elastic style guide for Vale.
|
I ran Results
Upgrade and post-upgrade compile succeeded with 0.4.0. Suggested commands: uvx --from kb-dashboard-cli==0.4.0 kb-dashboard upgrade --input-dir packages/airflow_otel/_dev/shared --write
uvx --from kb-dashboard-cli==0.4.0 kb-dashboard compile --input-dir packages/airflow_otel/_dev/shared --output-dir packages/airflow_otel/kibana/dashboard --format elastic-integrations |
There was a problem hiding this comment.
Is it possible to load (or even stress test) the airflow a bit with some DAGs so that dashboard has some data, not just "0" and "N/A"? Maybe with the help of Claude/Cursor/...
packages/airflow_otel/changelog.yml
Outdated
| changes: | ||
| - description: initial release | ||
| type: enhancement | ||
| link: "" |
There was a problem hiding this comment.
| link: "" | |
| link: "https://github.com/elastic/integrations/pull/17786" |
| ```yaml | ||
| receivers: | ||
| statsd: | ||
| endpoint: 0.0.0.0:8125 | ||
| transport: udp | ||
|
|
||
| exporters: | ||
| elasticsearch/otel: | ||
| endpoints: [<ES_ENDPOINT>] | ||
| api_key: ${env:ELASTICSEARCH_API_KEY} | ||
| mapping: | ||
| mode: otel | ||
|
|
||
| service: | ||
| pipelines: | ||
| metrics: | ||
| receivers: [statsd] | ||
| exporters: [elasticsearch/otel] | ||
| ``` |
There was a problem hiding this comment.
not sure if that's an improvement here, but it is possible to change the dataset data stream name like in this example: https://github.com/elastic/integrations/pull/17757/changes#diff-cef028242d40a61d0afab7399295d79d745fc777b027ca8f8227ae94ff2cf930R51-R56
So that we can have something like airflow.otel instead of statsdreceiver.otel which is generic
There was a problem hiding this comment.
We should have the service specific data stream name. Please add it via a processor in the config of OTel and also update it to the README.
There was a problem hiding this comment.
Updated dataset. Thanks!
|
packages/airflow_otel/kibana/alerting_rule_template/airflow_otel-dag-processor-timeouts.json
Outdated
Show resolved
Hide resolved
💚 Build Succeeded
History
|
|
Package airflow_otel - 0.1.0 containing this change is available at https://epr.elastic.co/package/airflow_otel/0.1.0/ |
Proposed commit message
Generated Kibana content for Apache Airflow monitoring via the OTel Airflow receiver: 4 dashboards (overview, tasks, DAG processing, scheduler capacity), 11 alert rules (heartbeat, executor saturation, task failures, scheduling delays, DAG import errors, etc.) and 3 SLO templates (task success rate, scheduler loop duration, DAG import error rate).
Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots