Skip to content

[pull] master from cube-js:master - #678

Merged
pull[bot] merged 1 commit into
code:masterfrom
cube-js:master
Aug 20, 2026
Merged

[pull] master from cube-js:master#678
pull[bot] merged 1 commit into
code:masterfrom
cube-js:master

Conversation

@pull

@pull pull Bot commented Aug 20, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

…11597)

* docs(monitoring): document log fields and metric labels (CUB-2879)

Monitoring Integrations documented inputs, sinks and metric names but nothing
about the tags attached to what actually gets exported. Add, from the code:

- the fields attached to every exported log record (deployment_id,
  deployment_name, hostname, pod_name, service, level, status, origin), plus
  the Datadog-only ddsource/ddtags and the per-sink `ddtags` option;
- the Prometheus labels on exported metrics (pod_name on cpu/memory,
  deployment_id/api_type/request_source on cube_requests_*), which is what
  gives a per-API request and latency breakdown;
- query_history_link in the Query History export field table, and a note that
  Query History records carry a different field set than container logs.

* docs(monitoring): address review — ddtags defaults in prose, trim example (CUB-2879)

- describe the ddtags defaults in prose instead of $DEPLOYMENT_NAME,$HOSTNAME, which
  read as user-settable env vars next to the CUBE_CLOUD_MONITORING_* section above;
- trim the third near-identical [sinks.datadog] block to the new option only;
- note on the `service` row that query-history records use a fifth value.
@pull pull Bot locked and limited conversation to collaborators Aug 20, 2026
@pull pull Bot added the ⤵️ pull label Aug 20, 2026
@pull
pull Bot merged commit 9b08d35 into code:master Aug 20, 2026
2 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant