> 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="/pages/JZRlyXvl6KW55SNLmp6T">/pages/JZRlyXvl6KW55SNLmp6T</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="/pages/BqmlU82OLcsQjbXDw4oK">/pages/BqmlU82OLcsQjbXDw4oK</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="/pages/6Mm8B3JGhzcLK5iV2Hmo">/pages/6Mm8B3JGhzcLK5iV2Hmo</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="/pages/k9cEvCk9Nvt9GFfrqOUC">/pages/k9cEvCk9Nvt9GFfrqOUC</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="/pages/dWfPilgBMBM21qGRkNgD">/pages/dWfPilgBMBM21qGRkNgD</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="/pages/9l1Q16Y1hqJWaR2yO9gR">/pages/9l1Q16Y1hqJWaR2yO9gR</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="/pages/Vbxly3qZHARhcTu8XWg1">/pages/Vbxly3qZHARhcTu8XWg1</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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.