> For the complete documentation index, see [llms.txt](https://docs.hiero.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hiero.org/block-node-home/production-runbook.md).

# Production Runbook

{% hint style="info" %}
For node operators onboarded by the Hiero operator team. If you are setting up a Block Node independently, use the [Deployment](/block-node-home/deployment.md) and [Configuration](/block-node-home/configuration.md) guides instead.
{% endhint %}

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Prerequisites</strong></td><td>Infrastructure, access, and software requirements before beginning a production Block Node deployment.</td><td><a href="/block-node-home/production-runbook/prerequisites.md">Prerequisites</a></td></tr><tr><td><strong>Install the Block Node</strong></td><td>Install and start the Block Node using Helm, configure plugins, and verify the initial deployment.</td><td><a href="/block-node-home/production-runbook/install-block-node.md">Install the Block Node</a></td></tr><tr><td><strong>Configure Alloy Telemetry</strong></td><td>Set up Grafana Alloy to scrape Block Node metrics and forward them to your observability stack.</td><td><a href="/block-node-home/production-runbook/configure-alloy-telemetry.md">Configure Alloy Telemetry</a></td></tr><tr><td><strong>Network Validation and Go-Live</strong></td><td>Validate Block Node connectivity, stream health, and block verification before connecting to the live network.</td><td><a href="/block-node-home/production-runbook/network-validation-go-live.md">Network Validation and Go-Live</a></td></tr><tr><td><strong>Steady State Operations</strong></td><td>Day-to-day operational procedures: monitoring dashboards, log review, storage management, and upgrade cadence.</td><td><a href="/block-node-home/production-runbook/steady-state-operations.md">Steady State Operations</a></td></tr><tr><td><strong>Disaster Recovery</strong></td><td>Procedures for recovering from disk failure, data corruption, or extended downtime.</td><td><a href="/block-node-home/production-runbook/disaster-recovery.md">Disaster Recovery</a></td></tr><tr><td><strong>Getting Help</strong></td><td>Support channels, issue reporting, and escalation paths for production Block Node operators.</td><td><a href="/block-node-home/production-runbook/getting-help.md">Getting Help</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hiero.org/block-node-home/production-runbook.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.