November 2026 Summaries

3 posts from Yugabyte

Filter
Month: Year:
Post Summaries Back to Blog
No summary generated yet.
Nov 16, 2026 2,739 words in the original blog post.
YugabyteDB Anywhere version 2026.1 introduces native OpenTelemetry Protocol support, allowing organizations to export database logs and metrics to Dynatrace and other OTLP-compatible observability platforms through a vendor-neutral standard. The workflow described configures OTLP in YugabyteDB Anywhere, creates a Dynatrace destination using its OTLP endpoint and API-token authentication, and enables query logging for selected events such as DDL statements and queries exceeding a 5,000-millisecond threshold. Database audit logging can also be enabled through pgAudit, though the text notes its potential performance overhead. YugabyteDB Anywhere deploys an OpenTelemetry Collector on database nodes for this export process, while warning that manual collector configuration changes may be overwritten by administrative operations or upgrades. After logs reach Dynatrace, users can filter them by universe and create DQL-based dashboard tiles that summarize query executions, average, maximum, and P95 latency, affected nodes, and recent activity. The approach is intended to provide centralized visibility across multiple YugabyteDB universes, support alerting on performance thresholds, and limit exported telemetry to relevant logs.
Nov 10, 2026 1,409 words in the original blog post.
YugabyteDB can use LDAP directories such as Active Directory, OpenLDAP, or FreeIPA to centralize authentication for both the YugabyteDB Anywhere (YBA) management console and database connections through YSQL and YCQL, reducing separate passwords and simplifying access management. YBA LDAP integration uses Search and Bind authentication, supports mapping LDAP groups to YBA roles, and should retain a local Super Admin account for emergency access. Database LDAP authentication is configured independently through YSQL access rules or YCQL T-Server flags, while local administrative accounts can remain password-based as a fallback if LDAP is unavailable. A preview LDAP universe sync feature can periodically create, update, and remove YSQL or YCQL roles based on directory users and groups, although it requires explicit API calls and external scheduling, and administrators must exclude protected local roles. LDAP changes such as password updates or account disabling affect new logins immediately, while role creation and deletion depend on sync timing; existing sessions may need to be terminated separately. The approach centralizes credentials, applies organizational password policies, supports clearer auditing and offboarding, and requires resilient LDAP infrastructure and careful permission management through database grants.
Nov 03, 2026 4,005 words in the original blog post.