You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2019/12/29 07:56:12 UTC

[GitHub] [druid] tomscut opened a new pull request #9105: Add a metric(segment/totalCount) about total number on each historical node

tomscut opened a new pull request #9105: Add a metric(segment/totalCount) about total number on each historical node
URL: https://github.com/apache/druid/pull/9105
 
 
   <!-- Replace XXXX with the id of the issue fixed in this PR. Remove this section if there is no corresponding issue. Don't reference the issue in the title of this pull-request. -->
   
   <!-- If you are a committer, follow the PR action item checklist for committers:
   https://github.com/apache/incubator-druid/blob/master/dev/committer-instructions.md#pr-and-issue-action-item-checklist-for-committers. -->
   
   ### Description
   
   <!-- Describe the goal of this PR, what problem are you fixing. If there is a corresponding issue (referenced above), it's not necessary to repeat the description here, however, you may choose to keep one summary sentence. -->
   
   <!-- Describe your patch: what did you change in code? How did you fix the problem? -->
   
   <!-- If there are several relatively logically separate changes in this PR, create a mini-section for each of them. For example: -->
   
   #### Added a metric(segment/totalCount) about total number of available segments on each historical node. This metric was emited to ambari metric collector, and could be shown on grafana.
   ![image](https://user-images.githubusercontent.com/55134131/71553841-1fa75900-2a51-11ea-899c-325a87325278.png)
   
   <!--
   In each section, please describe design decisions made, including:
    - Choice of algorithms
    - Behavioral aspects. What configuration values are acceptable? How are corner cases and error conditions handled, such as when there are insufficient resources?
    - Class organization and design (how the logic is split between classes, inheritance, composition, design patterns)
    - Method organization and design (how the logic is split between methods, parameters and return types)
    - Naming (class, method, API, configuration, HTTP endpoint, names of emitted metrics)
   -->
   
   
   <!-- It's good to describe an alternative design (or mention an alternative name) for every design (or naming) decision point and compare the alternatives with the designs that you've implemented (or the names you've chosen) to highlight the advantages of the chosen designs and names. -->
   
   <!-- If there was a discussion of the design of the feature implemented in this PR elsewhere (e. g. a "Proposal" issue, any other issue, or a thread in the development mailing list), link to that discussion from this PR description and explain what have changed in your final design compared to your original proposal or the consensus version in the end of the discussion. If something hasn't changed since the original discussion, you can omit a detailed discussion of those aspects of the design here, perhaps apart from brief mentioning for the sake of readability of this PR description. -->
   
   <!-- Some of the aspects mentioned above may be omitted for simple and small changes. -->
   
   <hr>
   
   This PR has:
   - [ ] been self-reviewed.
   - [ ] added unit tests or modified existing tests to cover new code paths.
   - [ ] been tested in a test Druid cluster.
   - [ ] been running in our formal Druid cluster.
   
   <!-- Check the items by putting "x" in the brackets for the done things. Not all of these items apply to every PR. Remove the items which are not done or not relevant to the PR. None of the items from the checklist above are strictly necessary, but it would be very helpful if you at least self-review the PR. -->
   
   <hr>
   
   ##### Key changed/added classes in this PR
    * `HistoricalMetricsMonitor`
    * `HistoricalMetricsMonitorTest`
   
   ##### Key changed/added files in this PR
    * `metrics.md`
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org


[GitHub] [druid] stale[bot] closed pull request #9105: Add a metric(segment/totalCount) about total number on each historical node

Posted by GitBox <gi...@apache.org>.
stale[bot] closed pull request #9105: Add a metric(segment/totalCount) about total number on each historical node
URL: https://github.com/apache/druid/pull/9105
 
 
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org


[GitHub] [druid] stale[bot] commented on issue #9105: Add a metric(segment/totalCount) about total number on each historical node

Posted by GitBox <gi...@apache.org>.
stale[bot] commented on issue #9105: Add a metric(segment/totalCount) about total number on each historical node
URL: https://github.com/apache/druid/pull/9105#issuecomment-614986663
 
 
   This pull request/issue has been closed due to lack of activity. If you think that is incorrect, or the pull request requires review, you can revive the PR at any time.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org


[GitHub] [druid] tomscut commented on issue #9105: Add a metric(segment/totalCount) about total number on each historical node

Posted by GitBox <gi...@apache.org>.
tomscut commented on issue #9105: Add a metric(segment/totalCount) about total number on each historical node
URL: https://github.com/apache/druid/pull/9105#issuecomment-569864279
 
 
   This is useful for monitoring the number of segments on each hitorical node.
   ![image](https://user-images.githubusercontent.com/55134131/71610553-00353b00-2bcd-11ea-96c7-b9085fce8405.png)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org


[GitHub] [druid] tomscut edited a comment on issue #9105: Add a metric(segment/totalCount) about total number on each historical node

Posted by GitBox <gi...@apache.org>.
tomscut edited a comment on issue #9105: Add a metric(segment/totalCount) about total number on each historical node
URL: https://github.com/apache/druid/pull/9105#issuecomment-569864279
 
 
   This is useful for monitoring the number of segments on each hitorical node.
   
   ![image](https://user-images.githubusercontent.com/55134131/71610553-00353b00-2bcd-11ea-96c7-b9085fce8405.png)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org


[GitHub] [druid] stale[bot] commented on issue #9105: Add a metric(segment/totalCount) about total number on each historical node

Posted by GitBox <gi...@apache.org>.
stale[bot] commented on issue #9105: Add a metric(segment/totalCount) about total number on each historical node
URL: https://github.com/apache/druid/pull/9105#issuecomment-600972771
 
 
   This pull request has been marked as stale due to 60 days of inactivity. It will be closed in 4 weeks if no further activity occurs. If you think that's incorrect or this pull request should instead be reviewed, please simply write any comment. Even if closed, you can still revive the PR at any time or discuss it on the dev@druid.apache.org list. Thank you for your contributions.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org


[GitHub] [druid] tomscut commented on issue #9105: Add a metric(segment/totalCount) about total number on each historical node

Posted by GitBox <gi...@apache.org>.
tomscut commented on issue #9105: Add a metric(segment/totalCount) about total number on each historical node
URL: https://github.com/apache/druid/pull/9105#issuecomment-575954741
 
 
   @jihoonson Hi, could you please review this PR?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org