Skip to content

Best Practice for Defining Composite Metrics Without Excessive Schema Overhead #2611

Best Practice for Defining Composite Metrics Without Excessive Schema Overhead

Best Practice for Defining Composite Metrics Without Excessive Schema Overhead #2611

Triggered via issue September 10, 2024 10:55
Status Success
Total duration 19s
Artifacts

issue-labeler.yml

on: issues
Process Label Action
11s
Process Label Action
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
Process Label Action
The following actions uses node12 which is deprecated and will be forced to run on node16: hramos/label-actions@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Process Label Action
The following actions use a deprecated Node.js version and will be forced to run on node20: hramos/label-actions@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/