You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2022/11/17 18:14:33 UTC

[GitHub] [flink-kubernetes-operator] jiangzho opened a new pull request, #445: [FLINK-29939]Add metrics for Kubernetes Client Response 5xx count and…

jiangzho opened a new pull request, #445:
URL: https://github.com/apache/flink-kubernetes-operator/pull/445

<!--
*Thank you very much for contributing to the Apache Flink Kubernetes Operator - we are happy that you want to help us improve the project. To help the community review your contribution in the best possible way, please go through the checklist below, which will get the contribution into a shape in which it can be best reviewed.*

## Contribution Checklist

- Make sure that the pull request corresponds to a [JIRA issue](https://issues.apache.org/jira/projects/FLINK/issues). Exceptions are made for typos in JavaDoc or documentation files, which need no JIRA issue.

- Name the pull request in the form "[FLINK-XXXX] [component] Title of the pull request", where *FLINK-XXXX* should be replaced by the actual issue number. Skip *component* if you are unsure about which is the best component.
Typo fixes that have no associated JIRA issue should be named following this pattern: `[hotfix][docs] Fix typo in event time introduction` or `[hotfix][javadocs] Expand JavaDoc for PuncuatedWatermarkGenerator`.

- Fill out the template below to describe the changes contributed by the pull request. That will give reviewers the context they need to do the review.

- Make sure that the change passes the automated tests, i.e., `mvn clean verify` passes. You can read more on how we use GitHub Actions for CI [here](https://nightlies.apache.org/flink/flink-kubernetes-operator-docs-main/docs/development/guide/#cicd).

- Each pull request should address only one issue, not mix up code from multiple issues.

- Each commit in the pull request has a meaningful commit message (including the JIRA id)

- Once all items of the checklist are addressed, remove the above text and this checklist, leaving only the filled out template below.

**(The sections below can be removed for hotfixes of typos)**
-->

## What is the purpose of the change

This PR adds metrics of `count` and `rate` for Kubernetes Client HTTP response code 1xx / 2xx / 3xx / 4xx / 5xx.
It also introduces `rate` per response code, in addition to `count`

## Brief change log

- Add Kubernetes Client metrics for count and rate of Http Response Codes

## Verifying this change

This change is already covered by existing unit test `org.apache.flink.kubernetes.operator.metrics.KubernetesClientMetricsTest` .

The unit test has been updated to cover additional metrics.

## Does this pull request potentially affect one of the following parts:

- Dependencies (does it add or upgrade a dependency): (no)
- The public API, i.e., is any changes to the `CustomResourceDescriptors`: (no)
- Core observer or reconciler logic that is regularly executed: (no)

## Documentation

- Does this pull request introduce a new feature? (yes)
- If yes, how is the feature documented? ( [docs updated](https://github.com/jiangzho/flink-kubernetes-operator/blob/7683b22687badb594bcb40652308ec109ff9c296/docs/content/docs/operations/metrics-logging.md#kubernetes-client-metrics) )

--
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: issues-unsubscribe@flink.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org