apache/kyuubi

[Umbrella] Expose connection metrics for all frontend services

Open

#3,169 opened on Aug 1, 2022

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Scala (2,332 stars) (996 forks)batch import
good first issuehelp wantedkind:umbrellapriority:major

Description

Code of Conduct

Search before asking

  • I have searched in the issues and found no similar issues.

Describe the proposal

Now kyuubi supports multiple frontend services.

  • thrift binary
  • thrift http
  • mysql
  • rest

And now, there is only metrics for thrift http connection.

We need support that for all frontend services.

Task list

#3156 #3170 #3171

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Contributor guide

Tech stack
scala
Domain
backendobservability
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic ScalaKyuubi architectureMetrics concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Start by reviewing the existing connection metrics for thrift HTTP frontend (issue #3156). Understand the metrics registration and reporting mechanism. Then design similar metrics for thrift binary, MySQL, and REST frontend services, looking into respective frontend modules like kyuubi thrift binary and kyuubi mysql. Ensure consistent metric naming and exposure via Kyuubi's metrics endpoint.