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
A nice enhancement to the dispute tracker is to be able to get additional information about dispute initiators, like hw information and OS. This would save a lot of time when trying to figure out who initiated disputes and why.
pub struct SysInfo {
/// The exact CPU model.
pub cpu: Option<String>,
/// The total amount of memory, in bytes.
pub memory: Option<u64>,
/// The number of physical CPU cores.
pub core_count: Option<u32>,
/// The Linux kernel version.
pub linux_kernel: Option<String>,
/// The exact Linux distribution used.
pub linux_distro: Option<String>,
/// Whether the node's running under a virtual machine.
pub is_virtual_machine: Option<bool>,
}
We just need to:
add option to specify a telemetry server
when configured, connect and search for validators network_id which should by address we have from chain
fetch the additional information that is sent when the connection to telemetry backend is made, see below
A nice enhancement to the dispute tracker is to be able to get additional information about dispute initiators, like hw information and OS. This would save a lot of time when trying to figure out who initiated disputes and why.
We just need to:
network_id
which should by address we have from chainThe text was updated successfully, but these errors were encountered: