wangyang0918 commented on a change in pull request #33: URL: https://github.com/apache/flink-kubernetes-operator/pull/33#discussion_r819215977
########## File path: README.md ########## @@ -84,3 +84,62 @@ Considering the cost of running the builds, the stability, and the maintainabili All the unit tests, integration tests, and the end-to-end tests will be triggered for each PR. Note: Please make sure the CI passed before merging. + +## Operator Metrics + +The operator extends the [Flink Metric System](https://nightlies.apache.org/flink/flink-docs-master/docs/ops/metrics/) that allows gathering and exposing metrics to centralized monitoring solutions. The well known [Metric Reporters](https://nightlies.apache.org/flink/flink-docs-master/docs/deployment/metric_reporters) are shipped in the operator image and are ready to use. + +### Slf4j +The default metrics reporter in the operator is Slf4j. It does not require any external monitoring systems, and it is enabled in the operator [Helm chart](helm/flink-operator/templates/flink-operator.yaml) by default, mainly for demonstrating purposes. +```properties +metrics.reporter.slf4j.factory.class: org.apache.flink.metrics.slf4j.Slf4jReporterFactory +metrics.reporter.slf4j.interval: 1 MINUTE +``` +To use a more robust production grade monitoring solution the configuration needs to be changed. + +### Prometheus +The following example shows how to enable the Prometheus metric reporter: +```properties +metrics.reporter.prom.class: org.apache.flink.metrics.prometheus.PrometheusReporter +metrics.reporter.prom.port: 9999 +``` +Some metric reporters, including the Prometheus, needs a port to be exposed on the container. This can be achieved be defining a value for the otherwise empty`metrics.port` variable. Review comment: ```suggestion Some metric reporters, including the Prometheus, needs a port to be exposed on the container. This can be achieved be defining a value for the otherwise empty `metrics.port` variable. ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
