With the introduction of Pipeline Groups and Ready-Made OpenPipeline pipelines for extensions, such as SQL Server, am I correct in understanding that we can no longer move logs to a separate bucket with a custom retention period? I just updated our Microsoft SQL Server extension to ver 3.1.2, and I was aware of the breaking changes, but I didn't think it would completely block the customization of bucket assignment.
In my tenant, all of our database extension-related logs are being picked up by a new read-only pipeline named "SQL Server" that has a processor that pushes all logs from SQL extensions to a bucket called "default_database_monitoring".
The bucket it refers to is also read-only. I can't modify its retention period or anything else.
Am I missing something here? Surely there must be a simple way to manipulate these logs with OpenPipeline alongside the new ready-made pipeline.
Featured Posts
