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

Make metrics config more flexible #222

Closed
no1seman opened this issue Apr 4, 2021 · 2 comments · Fixed by #268
Closed

Make metrics config more flexible #222

no1seman opened this issue Apr 4, 2021 · 2 comments · Fixed by #268
Assignees
Labels
feature A new functionality

Comments

@no1seman
Copy link
Contributor

no1seman commented Apr 4, 2021

Let's divide all metrics to groups(classes) and make it possible to select which metrics turned on. Also if no any settings was set simply turn on default metrics groups(classes). Groups could be configurable with set_export() or Cartridge Role config.

Reason: each metric occupy some space in Prometheus or InfluxDB and for example not every application uses http, in that case don't need to collect tnt_http_* metrics.

@yngvar-antonsson yngvar-antonsson added the feature A new functionality label Apr 6, 2021
@github-actions
Copy link

github-actions bot commented Jun 5, 2021

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days

@DifferentialOrange
Copy link
Member

Btw, if you don't use HTTP metrics in your app (i.e. do not set any HTTP middleware on any endpoints) there isn't any http_ metrics in Tarantool default metrics.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature A new functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants