-
Notifications
You must be signed in to change notification settings - Fork 90
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
MINIFICPP-2022 Add valid repository size metrics for all repositories #1490
Closed
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
lordgamez
force-pushed
the
MINIFICPP-2028
branch
from
January 11, 2023 15:14
8c899cc
to
83e0af6
Compare
lordgamez
force-pushed
the
MINIFICPP-2022
branch
from
January 11, 2023 15:24
68eb3af
to
c19d760
Compare
lordgamez
force-pushed
the
MINIFICPP-2028
branch
from
January 11, 2023 15:58
83e0af6
to
8824555
Compare
lordgamez
force-pushed
the
MINIFICPP-2022
branch
from
January 11, 2023 16:00
c19d760
to
c739339
Compare
szaszm
reviewed
Feb 2, 2023
8 tasks
lordgamez
force-pushed
the
MINIFICPP-2022
branch
from
February 23, 2023 10:14
577a559
to
c5d48af
Compare
lordgamez
force-pushed
the
MINIFICPP-2028
branch
from
February 24, 2023 11:41
8824555
to
a17acac
Compare
lordgamez
force-pushed
the
MINIFICPP-2022
branch
from
February 24, 2023 14:03
c5d48af
to
954b33d
Compare
lordgamez
force-pushed
the
MINIFICPP-2022
branch
from
March 10, 2023 10:47
0e8c07a
to
6caeb7c
Compare
adamdebreceni
approved these changes
Mar 10, 2023
szaszm
reviewed
Mar 10, 2023
lordgamez
force-pushed
the
MINIFICPP-2022
branch
2 times, most recently
from
March 14, 2023 13:03
1f7c8fc
to
50e8581
Compare
lordgamez
force-pushed
the
MINIFICPP-2022
branch
2 times, most recently
from
March 21, 2023 16:15
eb0b4a8
to
e5ff9b6
Compare
8 tasks
szaszm
reviewed
Apr 19, 2023
lordgamez
force-pushed
the
MINIFICPP-2022
branch
from
April 20, 2023 07:42
e5ff9b6
to
d192f3d
Compare
fgerlits
reviewed
Apr 26, 2023
lordgamez
force-pushed
the
MINIFICPP-2022
branch
from
April 28, 2023 10:08
9754f40
to
4c763c8
Compare
lordgamez
force-pushed
the
MINIFICPP-2022
branch
from
April 28, 2023 16:47
4c763c8
to
9d29e98
Compare
fgerlits
approved these changes
May 2, 2023
szaszm
approved these changes
May 3, 2023
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.
Calculate and report repository sizes (memory for volatile, disk space for persistent repositories) on C2 and Prometheus interfaces. Additionally add max repository size metric where available.
https://issues.apache.org/jira/browse/MINIFICPP-2022
Depends on #1485 and #1489
Thank you for submitting a contribution to Apache NiFi - MiNiFi C++.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
Does your PR title start with MINIFICPP-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
Has your PR been rebased against the latest commit within the target branch (typically main)?
Is your initial contribution a single, squashed commit?
For code changes:
For documentation related changes:
Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI results for build issues and submit an update to your PR as soon as possible.