𝐓𝐡𝐞 𝐀𝐜𝐜𝐞𝐬𝐬 𝐏𝐚𝐬𝐬 𝐁𝐞𝐡𝐢𝐧𝐝 𝐅𝐞𝐫𝐦𝐚𝐡’𝐬 𝐏𝐫𝐨𝐯𝐞𝐫 𝐌𝐨𝐧𝐢𝐭𝐨𝐫𝐢𝐧𝐠 GFermah Fellas One detail in @fermah_xyz’s node setup that I found interesting is the role of the Grafana API key. It acts as the access pass between a prover node and the monitoring stack, allowing telemetry data to reach dashboards and alerts. Without this connection, it becomes much harder to understand what is happening inside the node and whether it is operating as expected. ━━━━━━━━━━━━━━━━━━━━━━━━━ ⋤ 𝑻𝒉𝒆 𝑨𝒄𝒄𝒆𝒔𝒔 𝑷𝒂𝒔𝒔 𝑭𝒐𝒓 𝑷𝒓𝒐𝒗𝒆𝒓 𝑵𝒐𝒅𝒆𝒔 ⋥ ↬ The Grafana API key authenticates the node. It allows the prover to send useful telemetry to Fermah’s monitoring system, where operators can track node health and performance. ━━━━━━━━━━━━━━━━━━━━━━━━━ ⋤ 𝑭𝒓𝒐𝒎 𝑶𝒏𝒃𝒐𝒂𝒓𝒅𝒊𝒏𝒈 𝑻𝒐 𝑴𝒐𝒏𝒊𝒕𝒐𝒓𝒊𝒏𝒈 ⋥ ↬ Operators receive the key through Fermah’s specified channels. ↬ The key is then added to the node’s telemetry configuration. Once configured, the node can start sending metrics to the monitoring backend and become visible through the relevant dashboards and alerts. ━━━━━━━━━━━━━━━━━━━━━━━━━ ⋤ 𝑾𝒉𝒚 𝑽𝒊𝒔𝒊𝒃𝒊𝒍𝒊𝒕𝒚 𝑴𝒂𝒕𝒕𝒆𝒓𝒔 ⋥ ↬ Monitoring helps identify issues early. Operators can see whether nodes are online, overloaded, failing jobs, or falling behind. That visibility makes it easier to respond to problems before they affect the wider proving network. ━━━━━━━━━━━━━━━━━━━━━━━━━ ⋤ 𝑪𝒐𝒏𝒕𝒓𝒐𝒍𝒍𝒆𝒅 𝑨𝒄𝒄𝒆𝒔𝒔, 𝑩𝒆𝒕𝒕𝒆𝒓 𝑺𝒆𝒄𝒖𝒓𝒊𝒕𝒚 ⋥ ↬ The key is not treated as a public setting. Providing it only to onboarded operators helps Fermah control who can connect to the monitoring stack, while also making it easier to rotate or replace access when required. ━━━━━━━━━━━━━━━━━━━━━━━━━ ⋤ 𝑺𝒎𝒂𝒍𝒍 𝑲𝒆𝒚, 𝑩𝒊𝒈 𝑰𝒎𝒑𝒂𝒄𝒕 ⋥ The Grafana API key may look like a small setup requirement, but it supports something much bigger. A proving network needs more than powerful nodes. It also needs clear visibility into how those nodes are performing. Reliable infrastructure starts with knowing what is happening inside it.