Add Azure Log Analytics V2 log export support#121
Open
Conversation
Add AZURE_LOG_ANALYTICS_V2 log export type for exporting to Azure Monitor via the Logs Ingestion API and DCR-based ingestion, replacing the legacy AZURE_LOG_ANALYTICS path (retiring 2026-09-14). New Azure V2 configuration fields added to EnableLogExportBody and LogExportClusterSpecification: azure_client_id, azure_client_secret, azure_tenant_id, azure_dce_endpoint, azure_dcr_immutable_id, azure_dcr_resource_id, and azure_workspace_resource_id. Breaking change: auth_principal is no longer required on EnableLogExportBody, as AZURE_LOG_ANALYTICS_V2 does not use it. The field is now optional (pointer type). Deprecate AZURE_LOG_ANALYTICS in favor of AZURE_LOG_ANALYTICS_V2 and azure_shared_key in favor of azure_client_secret. Add UPDATE_BACKUP_CONFIGURATION audit log action. Add CLUSTER_DEVELOPER role to private endpoint and egress private endpoint read operations (ListAwsEndpointConnections, ListPrivateEndpointConnections, ListPrivateEndpointServices, ListEgressPrivateEndpoints, GetEgressPrivateEndpoint). Managed-service-pr-url: cockroachlabs/managed-service#24511
|
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This sync adds support for the new Azure Log Analytics V2 log export integration, which uses the Logs Ingestion API and DCR-based ingestion via an OTel pipeline. The legacy
AZURE_LOG_ANALYTICStype (using Fluent Bit's HTTP Data Collector API) is deprecated and retiring on 2026-09-14.Azure Log Analytics V2
AZURE_LOG_ANALYTICS_V2enum value onLogExportTypeEnableLogExportBodyandLogExportClusterSpecification:azure_client_id,azure_client_secret,azure_tenant_id,azure_dce_endpoint,azure_dcr_immutable_id,azure_dcr_resource_id,azure_workspace_resource_idAuthPrincipalis no longer a required field onEnableLogExportBody— it is now optional (*string) sinceAZURE_LOG_ANALYTICS_V2does not use it. Callers that previously passedauthPrincipalas the first argument toNewEnableLogExportBody()must update their call sites.AZURE_LOG_ANALYTICSandazure_shared_keyare deprecated in favor ofAZURE_LOG_ANALYTICS_V2andazure_client_secretOther changes
UPDATE_BACKUP_CONFIGURATIONaudit log actionCLUSTER_DEVELOPERrole to private endpoint and egress private endpoint read operations (ListAwsEndpointConnections,ListPrivateEndpointConnections,ListPrivateEndpointServices,ListEgressPrivateEndpoints,GetEgressPrivateEndpoint)