Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Extend Spanner client metrics #1327

Open
sebarthel89 opened this issue Aug 2, 2021 · 3 comments
Open

Extend Spanner client metrics #1327

sebarthel89 opened this issue Aug 2, 2021 · 3 comments
Assignees
Labels
api: spanner Issues related to the googleapis/java-spanner API. priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@sebarthel89
Copy link

Is your feature request related to a problem? Please describe.
We would like to receive more client metrics for spanner clients. Usually information like:

  • retries
  • latencies
  • requests per second

allows to trace down issues by service-instance that uses spanner. There are server-side metrics that can not provide the same insights as metrics independent of a deployed service.

Describe the solution you'd like
Right now, open census metrics are used to provide information about:

  • oc_worker_spans
  • sessions

It would be awesome if this list can be extended by

  • retries
  • latencies
  • requests per second.

Right now, we use the Prometheus open census exporter to export the metrics that we can expose via Prometheus. In an ideal scenario, metrics would also be exposed using micrometer because it's part of the popular spring boot stack.

Describe alternatives you've considered

  • building our custom metrics (Gauges, counters) for each service (already done in other teams, but this is a lot of work)
  • building our own abstraction layer that would allow us to build a reusable spanner client that exposes metrics that can be reused
  • not to do it and only rely on server metrics in combination with high-level client metrics like HTTP request latencies

Thanks in advance and keep up the good work!

@product-auto-label product-auto-label bot added the api: spanner Issues related to the googleapis/java-spanner API. label Aug 2, 2021
@yoshi-automation yoshi-automation added the triage me I really want to be triaged. label Aug 4, 2021
@olavloite olavloite added type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. and removed triage me I really want to be triaged. labels Aug 4, 2021
@thiagotnunes thiagotnunes assigned skuruppu and unassigned thiagotnunes Aug 6, 2021
@skuruppu skuruppu assigned asthamohta and unassigned skuruppu Aug 11, 2021
@skuruppu
Copy link
Contributor

Thanks for the feature request @sebarthel89. @asthamohta will take this on in a few weeks time when some other projects are wrapped up.

@olavloite
Copy link
Collaborator

@asthamohta @skuruppu I think it would make sense to pick up the feature request in #1268 together with this request, instead of separately add new metrics in different PRs.

@asthamohta
Copy link
Contributor

Hi @sebarthel89 I started looking into your request and was wondering if you could share more about the metrics that you would like. When you say number of retries and requests per second do you mean number of retries for a transaction and number of transactions per minute? Similarly for latencies it'd be great if you could expand a little on what you expect.

@ansh0l ansh0l added the priority: p3 Desirable enhancement or fix. May not be included in next release. label Feb 7, 2022
@rajatbhatta rajatbhatta assigned arpan14 and unassigned rajatbhatta Aug 17, 2023
@arpan14 arpan14 assigned rahul2393 and unassigned arpan14 Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: spanner Issues related to the googleapis/java-spanner API. priority: p3 Desirable enhancement or fix. May not be included in next release. type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Development

No branches or pull requests

10 participants