Surge Analytics FAQ
Surge Analytics is a Voltage specific tool which is primarily used to surface details about your node's behavior. These details could be exact reasons channels close, forwarding information, peer information, and other behaviors that your node may be exhibiting that needs further investigation.
Surge is for everyone! However, those who might find very particular use out of it are those running their node as part of a business, wallet, or app service. Also, those running a high-performance routing node may also find usefulness with Surge.
Surge can be turned on at no additional cost. However, Surge will consume API credits. We recommend turning Surge on for most users. If your API credit allocation is used up during a billing period, then you will automatically be allocated more and charged at the end of the billing cycle.
Surge will unlock the Channel Analytics charts, send/receive activity, Peer list, and Activity Feed to access directly within your Voltage node dashboard.
On your node dashboard, simply toggle the switch next to the Surge logo to "on." You will then be greeted with a description of Surge, and expected costs of adding Surge to your Voltage experience. If you agree, type in your node password and Surge will turn on. With Surge, you will be able to easily see all activity on your node directly from the Voltage node dashboard.
Surge is an optional service meant to make node management and decision making much easier, thus saving you and your team time when making important liquidity decisions, or troubleshooting any payment problems.
Surge works by getting your node's information using a Voltage developed communication program called the Agent. The Agent is a continuously running program that communicates with your node via a read only macaroon. The Agent collects various node data and metrics. Voltage then processes this data and presents it to you through the Surge dashboard.
No. The Agent is only given permissions of "read-only" which means that it does not have access to sending or receiving lightning payments, generating invoices, channel opens/closes, the on-chain wallet, or other administrative level tasks. Payment preimage data is only collected after the invoice generated is settled or when a payment made to someone else is settled.
Surge is not an interface for opening, closing, or directly managing channels or payments. For direct node control, we still recommend either Thunderhub or Terminal Web, both easily accessible from the Voltage dashboard.
We plan on having the Agent code open source in the near future.
When data is sent to Surge we store it in databases that we manage. This data is not accessible outside of our environment and only selected employees have access to the database to ensure uptime, debug issues, and accomplish maintenance. This data is not shared with any person or entity outside of Voltage. We do not sell any data. This data could be used by Voltage to enhance our products in an anonymized way to the best of our ability. Currently this data is retained indefinitely and can be deleted on request.
No.
Yes, but if your node has data compaction on, compacted data will not be uploaded.
A Voltage hosted node will be required for initial launch of Surge. We do plan on releasing the Agent binary to run on infrastructure outside of Voltage at a later date. When the Agent binary is released, a Voltage hosted node will not be required, and you will still have full access to Surge.
