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

Trace NodeState: demo #3591

Merged
merged 2 commits into from
Feb 17, 2022
Merged

Trace NodeState: demo #3591

merged 2 commits into from
Feb 17, 2022

Conversation

denisshevchenko
Copy link
Contributor

@denisshevchenko denisshevchenko commented Feb 10, 2022

This is the first step toward NodeState tracing. The NodeState represents the current state of the node. So any external application (for example, cardano-wallet or cardano-tracer) will be able to ask this state (as a DataPoint) and use it.

Currently, NodeState is almost useless, it only demonstrates the changing the state of a node in real-time.

This PR introduces demo-acceptor as well: a tiny application allowing to ask DataPoint from the node.

Copy link
Contributor

@deepfire deepfire left a comment

Choose a reason for hiding this comment

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

bors r+

iohk-bors bot added a commit that referenced this pull request Feb 16, 2022
3591: Trace NodeState: demo r=deepfire a=denisshevchenko

This is the first step toward `NodeState` tracing. The `NodeState` represents the current state of the node. So any external application (for example, `cardano-wallet` or `cardano-tracer`) will be able to ask this state (as a `DataPoint`) and use it.

Currently, `NodeState` is almost useless, it only demonstrates the changing the state of a node in real-time.

This PR introduces `demo-acceptor` as well: a tiny application allowing to ask `DataPoint` from the node.

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

iohk-bors bot commented Feb 16, 2022

This PR was included in a batch that successfully built, but then failed to merge into master. It will not be retried.

Additional information:

{"message":"Waiting on code owner review from DavidEichmann, JaredCorduan, Jimbo4350, dcoutts, erikd, nc6, and/or newhoggy.","documentation_url":"https://docs.github.com/articles/about-protected-branches"}

Copy link
Contributor

@Jimbo4350 Jimbo4350 left a comment

Choose a reason for hiding this comment

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

Can we also squash the first two commits?

cardano-node/src/Cardano/Node/StateRep.hs Outdated Show resolved Hide resolved
cardano-tracer: seq tests, disable some log tests for Windows.
@denisshevchenko
Copy link
Contributor Author

@Jimbo4350 Done, now there are only 2 commits.

@nc6
Copy link
Contributor

nc6 commented Feb 17, 2022

bors merge

@iohk-bors
Copy link
Contributor

iohk-bors bot commented Feb 17, 2022

Build succeeded:

@iohk-bors iohk-bors bot merged commit 2e5f87d into master Feb 17, 2022
@iohk-bors iohk-bors bot deleted the trace-node-state branch February 17, 2022 08:16
iohk-bors bot added a commit that referenced this pull request Mar 15, 2022
3656: cardano-node-3644: node state ADT expand. r=deepfire a=denisshevchenko

As a result of #3591, we now have a new `DataPoint` called `NodeState`. An external application (for example, `cardano-wallet`) can ask for this `DataPoint` to know the current state of the node.

Initially, `NodeState` was a primitive ADT and contained a very small portion of information. Now it's expanded.

Also, this PR moved node's peers info in a separate `DataPoint`.

The documentation is at: https://github.com/input-output-hk/cardano-node/wiki/cardano-node-and-DataPoints:-demo

3707: Workbench:  make geneses effectively cacheable in CI, by pinning the producing workbench r=deepfire a=deepfire

This makes workbench-produced geneses effectively cacheable in CI, by pinning the producing workbench as a new flake input.

Co-authored-by: Denis Shevchenko <denis.shevchenko@iohk.io>
Co-authored-by: Kosyrev Serge <serge.kosyrev@iohk.io>
iohk-bors bot added a commit that referenced this pull request Mar 15, 2022
3656: cardano-node-3644: node state ADT expand. r=deepfire a=denisshevchenko

As a result of #3591, we now have a new `DataPoint` called `NodeState`. An external application (for example, `cardano-wallet`) can ask for this `DataPoint` to know the current state of the node.

Initially, `NodeState` was a primitive ADT and contained a very small portion of information. Now it's expanded.

Also, this PR moved node's peers info in a separate `DataPoint`.

The documentation is at: https://github.com/input-output-hk/cardano-node/wiki/cardano-node-and-DataPoints:-demo

Co-authored-by: Denis Shevchenko <denis.shevchenko@iohk.io>
iohk-bors bot added a commit that referenced this pull request Mar 16, 2022
3656: cardano-node-3644: node state ADT expand. r=deepfire a=denisshevchenko

As a result of #3591, we now have a new `DataPoint` called `NodeState`. An external application (for example, `cardano-wallet`) can ask for this `DataPoint` to know the current state of the node.

Initially, `NodeState` was a primitive ADT and contained a very small portion of information. Now it's expanded.

Also, this PR moved node's peers info in a separate `DataPoint`.

The documentation is at: https://github.com/input-output-hk/cardano-node/wiki/cardano-node-and-DataPoints:-demo

Co-authored-by: Denis Shevchenko <denis.shevchenko@iohk.io>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

tracing: implement the node status datapoints
4 participants