Apply suggestion from @Dennis-Mircea

Co-authored-by: Dennis-Mircea Ciupitu <dennis.mircea.ciupitu@gmail.com>

Author: gyfora

docs/content/posts/2026-05-04-release-kubernetes-operator-1.15.0.md

@@ -49,7 +49,10 @@ standardize on Logback or rely on Logback-specific appenders and integrations.
 The operator Helm chart now bundles several additional Flink metric reporter JARs out of the box, making it easier to
 integrate with popular monitoring stacks without manual dependency management. The metrics documentation has also been
 substantially expanded with detailed configuration examples covering common setups such as Prometheus, InfluxDB, and
-StatsD.
+ ### Bundled Metric Reporters and Expanded Metrics Documentation
+                                                                                                                                                                                                           The operator Helm chart now bundles the `flink-metrics-dropwizard` reporter out of the box, removing the need for users to add the JAR manually when integrating with monitoring stacks that consume Dropwizard metrics.  
+
+The operator metrics documentation has also been substantially reworked: it now explains how operator-scoped metric identifiers are built, documents the `kubernetes.operator.metrics.*` prefix for operator-scoped reporter configuration, and walks through an end-to-end Prometheus monitoring setup. Most importantly, every metric the operator exposes is now documented in one place, with dedicated sections covering `FlinkDeployment` / `FlinkSessionJob` lifecycle and `JobStatus` tracking, `FlinkBlueGreenDeployment`, `FlinkStateSnapshot`, and autoscaler metrics, each with a clear explanation of what the metric measures and when it's emitted, so users finally have a complete picture of what's available out of the box.  
 
 ### Flink 2.2 Compatibility