An Azure diagram shows PostgreSQL logs flowing from a HorizonDB cluster into a Log Analytics workspace dashboard.
Azure has marked its "Generic Log Analytics Integration" for HorizonDB as generally available. The Azure Updates entry carries the "Launched" status and a timestamp of November 17, 2026. That status means fully released, production-ready and available to all Azure customers. The live Azure Updates page didn't show the entry's own announcement text when it was fetched. So the release-specific details aren't public yet: setup steps, supported regions, retention and pricing. The rest of this piece covers what Microsoft's documentation does confirm and how to use it.

An Azure diagram shows PostgreSQL logs flowing from a HorizonDB cluster into a Log Analytics workspace dashboard. Where this fits in the HorizonDB launch​

The listing is one of many HorizonDB items posted on the same day. Microsoft's Ignite 2026 Azure post says Azure HorizonDB, now generally available, is a fully managed, PostgreSQL-compatible database. The same post introduces Fabric HorizonDB, now in public preview.

A third-party tracker lists the log integration next to other operations items posted the same day. These include auditing, Azure Advisor integration, monitoring via alerts, and Entra authentication. The tracker corroborates the title, status and date of the listing. It isn't a technical source.

For a new database service, logging is one of the first things an operations team checks. A production PostgreSQL service whose logs can't reach your central monitoring is awkward to run.

What Microsoft documents for HorizonDB logs​

Microsoft Learn's Azure Monitor reference lists a set of HorizonDB tables. They include HorizonDBServerLogs, HorizonDBPgStatActivitySessions, HorizonDBTransactionsStats, HorizonDBQueryStoreRuntimeStats, HorizonDBQueryStoreWaitsStats, HorizonDBAutovacuumStats and HorizonDBQueryStoreQueryText. The reference also lists AzureMetrics for the same resource type.

The documentation doesn't say which of these tables the "generic" integration covers. Don't assume the GA covers all of them.

The HorizonDBServerLogs table holds PostgreSQL server logs from a HorizonDB replica. Its documented attributes are:

  • Resource type: microsoft.horizondb/clusters
  • Categories: Audit and Azure Resources
  • Solution: LogManagement
  • Table plans: Basic and Auxiliary/Lake tables are supported
  • Not supported: DCR workspace transformations and the Ingestion API

Useful columns for troubleshooting include:

  • TimeGenerated, a UTC timestamp
  • ErrorLevel, Message, Detail, Hint and SqlErrorCode
  • ProcessId, Node, Pool and Role
  • Statement, Query, Schema and Table

Role is documented as Unknown, ReadWrite or ReadOnly. That lets you separate writer and reader replica behavior.

The table also has the standard _IsBillable column. When it is false, ingestion isn't billed to your Azure account. The table reference doesn't say which HorizonDB records are billable. Check your own workspace's cost data before assuming logging is free.

Example queries Microsoft provides​

Microsoft publishes sample Kusto queries for HorizonDB logs. They cover:

  • Errors and fatal messages
  • Deadlock detection
  • Server shutdown and ready-to-accept events
  • Connections received, authorized and failed
  • Lock contention
  • Autovacuum events
  • Audit events

Some of these have prerequisites. Lock contention needs log_lock_waits=ON. Autovacuum events need log_autovacuum_min_duration to be enabled. Audit events need audit logging to be enabled. The connections-authorized sample excludes the azuresu account, which Microsoft's comment calls the Azure managed superuser.

Microsoft's samples also carry a comment that you can create an alert from a query with + New alert rule. That is a general Log Analytics feature. It doesn't show that the GA configures alerts for you.

A documentation inconsistency to watch​

The table reference page names the table HorizonDBServerLogs. The sample queries page uses PGSQLServerLogs in every query. Don't paste the samples blindly.

  1. In your Log Analytics workspace, open the Tables view or the schema pane. Confirm which table name actually exists.
  2. Replace the table name in the sample query with the one you see.
  3. Run a simple query first, such as the 100 most recent ERROR rows ordered by TimeGenerated. Confirm that data is arriving.
  4. Only then build alert rules on top of it.

That PGSQLServerLogs is the name of the PostgreSQL flexible server table is general Azure knowledge, not something the HorizonDB pages say. The mismatch may just be documentation lag, but I can't confirm that.

Related HorizonDB monitoring and policy context​

HorizonDB's session data is a separate table. Microsoft documents HorizonDBPgStatActivitySessions as one of the HorizonDB tables. Its reference page says it collects pg_stat_activity data every five minutes. That means it is snapshot data, not a continuous log.

Azure Policy support is also in the mix. WindowsForum's coverage of the Azure Policy GA notes that a built-in definition, "[Preview]: Deploy Diagnostic Settings for Azure HorizonDB clusters to Log Analytics workspace", deploys diagnostic settings when a cluster is created or updated without them. That definition is still labeled preview. If you want logs to flow to a workspace by policy, check that label before relying on it in production.

Our earlier alerts coverage also warns against assuming that metrics flow into Log Analytics through diagnostic settings. It advises using the metric alert path for metrics, and server-log queries for log events.

What admins should do now​

  • Inventory your clusters. Find out which HorizonDB clusters send logs to a workspace, if any.
  • Verify, don't assume. The announcement text isn't visible, so don't assume logging is on by default. Check each cluster's diagnostic settings.
  • Check the PostgreSQL parameters. Lock-wait and autovacuum logging need their parameters enabled.
  • Watch ingestion cost. Server logs can be chatty. Review billable volume and table plan (Basic or Auxiliary) in your workspace.
  • Plan alerts. Start with fatal messages, deadlocks and failed connections. These are the documented examples most likely to matter.
  • Track the documentation. Watch for fixes to the table name mismatch and for the full announcement text.

Bottom line​

This is a short, practical GA item. HorizonDB server-log data is documented in Azure Monitor Logs, with a schema and a set of operational queries. The unknowns are the setup procedure, regional availability, pricing and exactly what the "generic" integration includes. Treat the sample queries as a starting point and confirm table names in your own workspace.

 

References

  1. (Launched) Generally Available: Azure HorizonDB Generic Log Analytics Integration Azure Updates 2026-11-17T20:00:32Z
  2. Azure Monitor Logs reference - HorizonDBServerLogs - Azure Monitor | Microsoft Learn learn.microsoft.com
  3. Example log table queries for HorizonDBServerLogs - Azure Monitor | Microsoft Learn learn.microsoft.com