You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Monitoring interface of any one node can be abused if exposed externally. Observing some metrics may be disclosing node-specific information regarding its performance limitations, which can be used to mount an effective DDOS attack.
Scaling Considerations
Changes are node-local and not in consensus.
Test Plan
Mostly manual for now. Some automation is possible.
Upgrade Considerations
This will be rolled out as part of standard release process, likely over several iterations.
The text was updated successfully, but these errors were encountered:
closes: #10883
refs: #10882
## Description
Add metrics for the following action types:
- CORE_EVAL
- DELIVER_INBOUND
- IBC_EVENT
- INSTALL_BUNDLE
- PLEASE_PROVISION
- VBANK_BALANCE_UPDATE
- WALLET_ACTION
- WALLET_SPEND_ACTION
- VTRANSFER_IBC_EVENT
- KERNEL_UPGRADE_EVENTS
### Security Considerations
Metrics may expose inner state which could be used to mount an effective attack.
### Scaling Considerations
No impact on a local node performance expected.
### Documentation Considerations
Metric names and their meaning need to be documented as now available via standard reporting interface.
### Testing Considerations
manual testing?
### Upgrade Considerations
This will roll out as part of standard release.
What is the Problem Being Solved?
We need to be able to monitor all of the key aspects to SwingSet Kernel's inner workings for proactive development and ease of troubleshooting.
Description of the Design
Identify critical metrics, collect them internally, and make them available for outside monitoring.
https://docs.google.com/document/d/11fjd0A2S-mgrkN7i7IePYMpuGdpbEZwhfHRJAxJjoPU/edit?tab=t.0#heading=h.vzrutkd4jeh7
Security Considerations
Monitoring interface of any one node can be abused if exposed externally. Observing some metrics may be disclosing node-specific information regarding its performance limitations, which can be used to mount an effective DDOS attack.
Scaling Considerations
Changes are node-local and not in consensus.
Test Plan
Mostly manual for now. Some automation is possible.
Upgrade Considerations
This will be rolled out as part of standard release process, likely over several iterations.
The text was updated successfully, but these errors were encountered: