Open saikumarch7548 opened 2 days ago
Hi @saikumarch7548 ,
I don't believe that the azure_monitor_logs
sink creates the table (at least not explicitly; maybe Azure automatically creates it?); it expects the table to already exist. You can see in the debug logs that Vector is sending logs to Azure and is receiving a 200 OK back so, from Vector's perspective, it seems like everything is working. The issue may like on the Azure side.
@jszwedko when I pass a new tablename that doesnt exist in Azure yet, It works properly. which API is vector using
@jszwedko when I pass a new tablename that doesnt exist in Azure yet, It works properly. which API is vector using
Interesting, maybe Azure is automatically creating the table? The API Vector uses is this one: https://learn.microsoft.com/en-us/azure/azure-monitor/logs/data-collector-api
A note for the community
Problem
I tried deleting the Azure custom table created by below configuration and redeployed it since I filtered only the data I need. Vector canot create the Azure log analytics table again Vector didnt show any logs/errors related to the table creation Vector didnt published the results Vector works okay if we provide a new table name
Configuration