-
Notifications
You must be signed in to change notification settings - Fork 788
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
method to monitor offical TESTNET & full RPC node #3101
Comments
If you are part of the testnet then you deal with logs on your end, in a way you like and in a way it fits your infrastructure, workflow, etc, etc. |
@Gandalf-the-Grey - I think There was a mistake/confusion in what I wrote. I end up mixing up TESTNET, full RPC nodes, test condensor etc. To be precise, what we need is, A mechanism to monitor the logs when we generate transactions on
reason Next Steps |
Any witness having a test node connected to the testnet could install an APM on it. However if Steemit Inc change their node more frequently than they provide us with a release then it’s better if they have one themselves. Additionally an APM for the RPC nodes, the seed and also the condenser can also be very useful. You could aggregate the data from all of them and links events together. Maybe something happened on a specific version of the condenser that triggers a specific behaviour on the RPC triggering in turn a bug on the witness node? On top of that, add a helper that also records resource usage and you could do more |
We need a method to monitor the logs generated in the TESTNET while generating transactions. This can be something like a plain old log aggregation or an APM.
The text was updated successfully, but these errors were encountered: