Skip to content

Conversation

denisshevchenko
Copy link
Contributor

@denisshevchenko denisshevchenko commented May 6, 2020

Issue

  • Trace node's real up time.

  • This PR does not result in breaking changes to upstream dependencies.

Checklist

  • This PR contains all the work required to resolve the linked issue.

  • The work contained has sufficient documentation to describe what it does and how to do it.

  • The work has sufficient tests and/or testing.

  • I have committed clear and descriptive commits. Be considerate as somebody else will have to read these.

  • I have added the appropriate labels to this PR.

Copy link
Contributor

@CodiePP CodiePP left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's maybe easier to just get the time from a monotonic clock as we are interested in the time elapsed.

@denisshevchenko denisshevchenko force-pushed the cad-878-node-up-time branch from 6c9e5bd to 106dd4e Compare May 7, 2020 05:42
@denisshevchenko
Copy link
Contributor Author

@CodiePP Fixed.

@CodiePP CodiePP added this to the S12 2020-05-07 milestone May 7, 2020
@CodiePP CodiePP added priority medium issues/PRs that SHOULD be addressed. This should be done for the release, but acceptable if it doesn shelley testnet issues/PRs that need to be done for the Shelley testnet labels May 7, 2020
iohk-bors bot added a commit to input-output-hk/cardano-benchmarking that referenced this pull request May 7, 2020
46: CAD-878: Node's up time. r=CodiePP a=denisshevchenko

Previously RTView calculated "Node uptime" based on start time which was a time when the first `LogObject` was received. Now node sends `LogObject` with its real up time.

Corresponding changes in `cardano-node`: IntersectMBO/cardano-node#892

Co-authored-by: Denis Shevchenko <denis.shevchenko@iohk.io>
Co-authored-by: Alexander Diemand <codieplusplus@apax.net>
@denisshevchenko denisshevchenko force-pushed the cad-878-node-up-time branch from 106dd4e to c5367bc Compare May 7, 2020 11:21
@CodiePP CodiePP force-pushed the cad-878-node-up-time branch from c5367bc to da8e97a Compare May 8, 2020 14:57
@CodiePP
Copy link
Contributor

CodiePP commented May 8, 2020

bors r+

iohk-bors bot added a commit that referenced this pull request May 8, 2020
892: CAD-878: Trace node up time. r=CodiePP a=denisshevchenko

Issue
-----------

- Trace node's real up time.

- This PR **does not result** in breaking changes to upstream dependencies.

Checklist
---------
- [ ] This PR contains all the work required to resolve the linked issue.

- [ ] The work contained has sufficient documentation to describe what it does and how to do it.

- [ ] The work has sufficient tests and/or testing.

- [ ] I have committed clear and descriptive commits. Be considerate as somebody else will have to read these.

- [x] I have added the appropriate labels to this PR.


Co-authored-by: Denis Shevchenko <denis.shevchenko@iohk.io>
@iohk-bors
Copy link
Contributor

iohk-bors bot commented May 8, 2020

Build failed

Signed-off-by: Alexander Diemand <codieplusplus@apax.net>
@CodiePP CodiePP force-pushed the cad-878-node-up-time branch from e2498f3 to 9d73780 Compare May 8, 2020 18:51
@CodiePP
Copy link
Contributor

CodiePP commented May 8, 2020

bors r+

@iohk-bors
Copy link
Contributor

iohk-bors bot commented May 8, 2020

@iohk-bors iohk-bors bot merged commit 1dc0113 into master May 8, 2020
@iohk-bors iohk-bors bot deleted the cad-878-node-up-time branch May 8, 2020 19:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority medium issues/PRs that SHOULD be addressed. This should be done for the release, but acceptable if it doesn shelley testnet issues/PRs that need to be done for the Shelley testnet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants