-
Notifications
You must be signed in to change notification settings - Fork 897
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
Allow individual tables to be specified for metrics #17051
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kbrock
changed the title
Allow individual tables to be specified for metrics
[WIP] Allow individual tables to be specified for metrics
Feb 26, 2018
kbrock
force-pushed
the
metrics_indexes
branch
from
February 26, 2018 21:28
d0f307e
to
cec9d3b
Compare
kbrock
force-pushed
the
metrics_indexes
branch
from
February 27, 2018 02:29
cec9d3b
to
77a8224
Compare
kbrock
changed the title
[WIP] Allow individual tables to be specified for metrics
Allow individual tables to be specified for metrics
Feb 27, 2018
someone may want to backport this - so separating from the original PR |
3 tasks
Checked commit kbrock@77a8224 with ruby 2.3.3, rubocop 0.52.0, haml-lint 0.20.0, and yamllint 1.10.0 |
kbrock
added
bug
enhancement
providers/metrics
and removed
core/alerts
api
appliance/console
labels
Feb 27, 2018
If so, please add the gaprindashvili label 🙇 |
gtanzillo
pushed a commit
to gtanzillo/manageiq
that referenced
this pull request
Mar 8, 2018
Allow individual tables to be specified for metrics (cherry picked from commit ac0e949)
gtanzillo
pushed a commit
to gtanzillo/manageiq
that referenced
this pull request
Mar 8, 2018
Allow individual tables to be specified for metrics (cherry picked from commit ac0e949)
simaishi
pushed a commit
that referenced
this pull request
Mar 9, 2018
Allow individual tables to be specified for metrics (cherry picked from commit ac0e949) https://bugzilla.redhat.com/show_bug.cgi?id=1553797
Gaprindashvili backport details:
|
Backported to Fine via #17124 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
pulled out of #17017
Allows us to specify which metrics table we want to use (still defaulting to an hour from now)
functionality added in #16929
This also fixes 2 bugs:
metrics_1
should bemetrics_01
metrics_24
should bemetrics_00
https://bugzilla.redhat.com/show_bug.cgi?id=1551021