* Tag workflow related metrics with process definition code (workflow id)
* Clean up related metrics when deleting workflow definition
* Add license headers
* Update related UT cases
* Add an example in grafana-demo
* Add related docs
* Filtering data by application in grafana-demo worker dashboard example
* Update dolphinscheduler-api/src/main/resources/swagger.properties
Co-authored-by: chunlai.xu <chunlai.xu@zhaopin.com.cn>
Co-authored-by: kezhenxu94 <kezhenxu94@apache.org>
* Fix remaining style errors and wildcard imports
* Upgrade spotless to the latest stable version, exclude .github folder from spotless check and fix dead link
* Fix spotless matching scope of markdown files
* [Improvement][Metrics] Add metrics for alert server (#11131)
* Update related docs of metrics
* Add grafana demo dashboards for alert server metrics
* Refactor metric classes with UtilityClass annotation
* Refactor meter names in camelCase for checkstyle
* [Improvement][Metrics] Switch to use tags to indicate task / workflow execution status for metrics (#10867)
* Update docs and grafana demo dashboards
* [Feature][Metrics] Add resource download related metrics for workers (#9324)
* [Feature][Metrics] Fix bugs and add grafana demos for worker resource download metrics (#9324)
* [Feature][Metrics] Add docs to resource related metrics (#9324)
* [Feature][Metrics] Use tags to indicate status in metrics (#9324)
* [Feature][Metrics] Fix demos, docs and remove redundant code (#9324)
* [Feature][Metrics] Remove .pnpm-debug.log (#9324)
* [Feature][Metrics] Fix style check (#9324)
* [Feature][Metrics] Replace KB with bytes for the unit of resource file size in metrics (#9324)
* [Feature][Metrics] Make code neat (#9324)
* Apply micrometer naming convention to worker metrics
* Apply micrometer naming convention all current metrics
* Fix remaining metrics names, update English docs and add Chinese docs
* Fix metrics names in grafana-demo dashboards
* Split the components into individual package
A follow-up PR will be made to build dedicated Docker images for each
component, so that every component Docker image has minimal jars, which
is easy to maintain and good for security fixes.
* Split the components into individual package
A follow-up PR will be made to build dedicated Docker images for each
component, so that every component Docker image has minimal jars, which
is easy to maintain and good for security fixes.
* Split the components into individual package
A follow-up PR will be made to build dedicated Docker images for each
component, so that every component Docker image has minimal jars, which
is easy to maintain and good for security fixes.
Wenjun Ruan