11.0.312

Agenta-AI/agenta11.0.312Aug 6, 2026by adubovikov

AI Summary

This release improves search capabilities by persisting HEP `node_name` and aligning metrics between SIP and RTCP using a new configuration option.

Key Highlights

HEP hostname is now stored in `data_extra.node_name` when it differs from numeric `node_id`.
Protocol Search logic updated to match on `(node_id = X OR data_extra.node_name = X)`.
Results and Events UI now display a 'Node Name' column.
New configuration `prometheus.agent_label` allows alignment of SIP and RTCP metrics.

New Features

Node name persistence in search results
Prometheus agent label configuration
Search logic enhancement for node matching

Full Release Notes

## What's Changed
* fix(search): persist HEP `node_name` in `data_extra` for Results filters by @adubovikov in https://github.com/sipcapture/homer/pull/926
* fix(ui): show Node Name column from `data_extra.node_name` by @adubovikov in https://github.com/sipcapture/homer/pull/926
* fix(metrics): align SIP/RTCP Prometheus `node_id` via `prometheus.agent_label` by @adubovikov in https://github.com/sipcapture/homer/pull/925
* docs(node): clean catalog reconnect comments by @adubovikov in https://github.com/sipcapture/homer/pull/924

### Highlights (#922)
- HEP hostname (`0x0013` / heplify `-hn`) is stored in `data_extra.node_name` when it differs from numeric `node_id` (`0x000c` / `-hi`). **No DuckLake schema migration.**
- Protocol Search «Node» matches `(node_id = X OR data_extra.node_name = X)`; Capture ID stays numeric-only.
- Results / Events show a **Node Name** column from `data_extra`.
- New config `prometheus.agent_label` (`node_id` | `node_name`, default `node_id`, env `HOMER_PROMETHEUS_AGENT_LABEL`) so SIP and RTCP use the same Prometheus label value.

**Full Changelog**: https://github.com/sipcapture/homer/compare/11.0.310...11.0.312