--- title: "Remote Logger for OpenTelemetry and Syslog" description: "Remote Logger for OpenTelemetry and Syslog is a Marketplace integration for Home Assistant. It has 62 installs sharing analytics, works locally and was last updated October 26, 2026." canonical: "https://vulpo.app/integrations/marketplace/rhizomatics-remote-logger" url: "https://vulpo.app/integrations/marketplace/rhizomatics-remote-logger.md" last-updated: "2026-10-25" version: "1.4" --- # Remote Logger for OpenTelemetry and Syslog > Remote Logger for OpenTelemetry and Syslog is a Marketplace integration for Home Assistant. It has 62 installs sharing analytics, works locally and was last updated October 26, 2026. Remote Logger for OpenTelemetry and Syslog sends Home Assistant logs to a remote Syslog or OTLP collector. It listens to the Python root logger or the system log event, so multi-line logs and stacktraces stay as single entries. OTLP output goes over HTTP as JSON or protobuf, with optional TLS, token authentication, extra headers and custom resource attributes, while Syslog uses RFC 5424 messages over UDP or TCP. Other Home Assistant events can be forwarded as well, including lifecycle events, core changes, service calls, automation runs and state changes, plus any custom event names. Sensors report formatting errors, posting errors, log events and postings, and the integration leaves out its own log entries to avoid loops. It runs locally and is set up in the UI after installing it through the Marketplace or HACS. Automatic summary of the README and code of rhizomatics/remote\_logger. Something wrong, or are you the maintainer and want your own text here? [Get in touch](https://vulpo.app/contact) [Open in My Home Assistant](https://my.home-assistant.io/redirect/hacs_repository/?owner=rhizomatics&repository=remote_logger&category=integration) On Home Assistant 2026.11 or newer? [Open it in the Marketplace](https://my.home-assistant.io/redirect/marketplace_repository/?owner=rhizomatics&repository=remote_logger&category=integration) ## Supports - **Works locally**: Talks to your devices on your own network. No vendor cloud in between. - **From the Marketplace**: Installed through the Marketplace, formerly HACS. - **Actively maintained**: Its author released or pushed a change in the last six months. ## Setting it up Install it from the Marketplace and restart Home Assistant, then add it under Settings, Devices and services. ### Configure OTLP Endpoint - **Collector host**: Hostname or IP address of the OTLP collector. - **Collector port**: HTTP port of the OTLP collector (default 4318). - **Use TLS (HTTPS)**: Enable HTTPS for the connection to the collector. - **Payload encoding**: Encoding format for the OTLP payload: json or protobuf. - **Batch max size**: Maximum number of log records to buffer before flushing (1-10000, default 100). - **Custom resource attributes**: Optional comma-separated key=value pairs added to every log record (e.g. deployment.environment=production,service.namespace=home). - **Token type**: Authentication scheme: Bearer sends the token as-is; Basic base64-encodes it as 'username:password'. - **Access token for Authorization header**: Optional token. Sent in the 'Authorization' header. - **Additional headers**: Optional extra HTTP headers in 'Name: value' format (e.g. stream-name: my-stream). Enter one header per entry. - **Logs endpoint path**: Path appended to host:port for the logs endpoint (default /v1/logs). Prefix with any API-specific path (e.g. /api/otlp/v1/logs). ### Configure Syslog Endpoint - **Syslog server host**: Hostname or IP address of the syslog server. - **Syslog server port**: Port of the syslog server (default 514). - **Transport protocol**: Transport protocol: UDP (fire-and-forget) or TCP (reliable delivery). - **Use TLS (TCP only)**: Enable TLS encryption for TCP connections. Ignored for UDP. - **Application name**: The APP-NAME field in RFC 5424 messages (default: homeassistant). - **Syslog facility**: Syslog facility code used to calculate the PRI value (default: user). ### Additional Home Assistant Events - **Use System Log events in place of Python root logger**: Use standard Home Assistant log event as alternative to capture via Python root logger, limited to warning and error logs available - **Minimum log level (root logger mode only)**: Minimum severity forwarded to the remote endpoint. Only applies when root logger mode is active (system\_log\_event disabled). Default: INFO. - **Serialize event data into log body**: When enabled, the full event data is serialized as JSON into the log body. Only entity\_id, domain, and service are retained as structured attributes. - **Suppress system\_log\_event as event name**: When enabled, system\_log\_event records are exported without an eventName field. Disable when using remote\_logger as a general event recorder so all event types can be distinguished. - **One or more events**: Optional list of additional Home Assistant event names to subscribe to (e.g. zha\_event). Enter one event name per entry. - **Home Assistant lifecycle events**: Subscribe to homeassistant\_start, homeassistant\_started, and homeassistant\_stop events. - **Home Assistant core change events**: Subscribe to component\_loaded, core\_config\_updated, service\_registered, service\_removed, lovelace\_updated, panels\_updated, themes\_updated, labs\_updated, user\_added, user\_updated, and user\_removed events. - **Home Assistant core activity**: Home Assistant core activity, including service calls, automation and script execution. - **Home Assistant state changes, without attributes or context**: Home Assistant state changes (without attributes or context) and logbook entries - **Home Assistant state changes**: Home Assistant state changes (complete event) and logbook entries ### Re-authenticate OTLP Endpoint - **Token type**: Authentication scheme: Bearer sends the token as-is; Basic base64-encodes it as 'username:password'. Raw Basic sends as configured. ApiKey sends with 'ApiKey' prefix. - **Token**: New token to authenticate with the OTLP collector. ### After setup - **Collector host**: Hostname or IP address of the OTLP collector. - **Collector port**: HTTP port of the OTLP collector (default 4318). - **Use TLS (HTTPS)**: Enable HTTPS for the connection to the collector. - **Payload encoding**: Encoding format for the OTLP payload: json or protobuf. - **Batch max size**: Maximum number of log records to buffer before flushing (1-10000, default 100). - **Custom resource attributes**: Optional comma-separated key=value pairs added to every log record (e.g. deployment.environment=production,service.namespace=home). - **Token type**: Authentication scheme: Bearer sends the token as-is; Basic base64-encodes it as 'username:password'. - **Access token for Authorization header**: Optional token. Sent in the 'Authorization' header. - **Additional headers**: Optional extra HTTP headers in 'Name: value' format (e.g. stream-name: my-stream). Enter one header per entry. - **Logs endpoint path**: Path appended to host:port for the logs endpoint (default /v1/logs). Prefix with any API-specific path (e.g. /api/otlp/v1/logs). - **Syslog server host**: Hostname or IP address of the syslog server. - **Syslog server port**: Port of the syslog server (default 514). - **Transport protocol**: Transport protocol: UDP (fire-and-forget) or TCP (reliable delivery). - **Use TLS (TCP only)**: Enable TLS encryption for TCP connections. Ignored for UDP. - **Application name**: The APP-NAME field in RFC 5424 messages (default: homeassistant). - **Syslog facility**: Syslog facility code used to calculate the PRI value (default: user). - **Use system\_log\_event instead of Python root logger**: Use standard Home Assistant log event as alternative to capture via Python root logger, limited to warning and error logs available. - **Minimum log level (root logger mode only)**: Minimum severity forwarded to the remote endpoint. Only applies when root logger mode is active (system\_log\_event disabled). Default: INFO. - **Custom event names**: Optional list of additional Home Assistant event names to subscribe to (e.g. zha\_event). Enter one event name per entry. - **Serialize event data into log body**: When enabled, the full event data is serialized as JSON into the log body. Only entity\_id, domain, and service are retained as structured attributes. Alternatively, preserve single JSON structure, which will mean a log database generates a column for every possible field. - **Suppress system\_log\_event as event name**: When enabled, system\_log\_event records are exported without an eventName field. Disable when using remote\_logger as a general event recorder so all event types can be distinguished. - **Home Assistant lifecycle events**: Subscribe to homeassistant\_start, homeassistant\_started, and homeassistant\_stop events. - **Home Assistant core change events**: Subscribe to component\_loaded, core\_config\_updated, service\_registered, service\_removed, lovelace\_updated, panels\_updated, themes\_updated, labs\_updated, user\_added, user\_updated, and user\_removed events. - **Home Assistant core activity**: Home Assistant core activity, including service calls, automation and script execution. - **Home Assistant state changes, without attributes or context**: Home Assistant state changes (without attributes or context) and logbook entries - **Home Assistant state changes**: Home Assistant state changes (complete event) and logbook entries Texts from the code of [rhizomatics/remote\_logger](https://github.com/rhizomatics/remote_logger). ## Entities - **Sensors**: Formatting Errors, Posting Errors, Log Events, Postings ## From the README > Use log aggregation and analysis tools to get a complete picture of your home automation. Remote Logger for Home Assistant listens to Home Assistant logging at source and sends structured log events to a remote Syslog or OpenTelemetry (OTLP) collector. Optionally forwards other Home Assistant events, such as lifecycle events, service calls, configuration updates, state changes. From the README of [rhizomatics/remote\_logger](https://github.com/rhizomatics/remote_logger#readme), [Apache License 2.0](https://spdx.org/licenses/Apache-2.0.html). Shortened. ## At a glance - Kind: Marketplace integration - Category: [Computers and network](https://vulpo.app/integrations/category/computers-and-network.md), Monitoring - Number: 62 installs sharing analytics; 13 GitHub stars - Connection: Works locally - Upkeep: Updated in the last 6 months - Needs: Needs the Marketplace (HACS on 2026.10 and older) - Latest version: v2.0.7, last updated October 26, 2026 - Domain: `remote_logger` - Source: - Issues: - Screenshot: https://vulpo.app/integrations-img/74aabfe1edb3f0b6.webp (from rhizomatics/remote\_logger's README) - Screenshot: https://vulpo.app/integrations-img/5671a1f1a29026ee.webp (from rhizomatics/remote\_logger's README) - Screenshot: https://vulpo.app/integrations-img/8e619b4be81d16ea.webp (from rhizomatics/remote\_logger's README) In Vulpo: Chart card, Apple Watch Independent directory, made by the developer of Vulpo. Not affiliated with Home Assistant or the Open Home Foundation. [About these numbers](https://vulpo.app/integrations/about) Last updated 2026-10-25. Source: https://vulpo.app/integrations/marketplace/rhizomatics-remote-logger --- - HTML version of this page: https://vulpo.app/integrations/marketplace/rhizomatics-remote-logger - Site index for agents: https://vulpo.app/llms.txt - Everything in one document: https://vulpo.app/llms-full.txt - All pages: https://vulpo.app/sitemap.xml