-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New component: Azure Blob Receiver #8834
Comments
I scheduled some time to talk about this during the next SIG call, given that we don't seem to have volunteers for this. Could you please confirm you are affiliated with Azure and that this is a component backed by a vendor (Microsoft)? |
I will be happy to help with the initiative as the sponsor |
@pmm-sumo Thanks a lot! |
Hi, this issues is the top hit on google for "otel collector to blob storage". Is there documentation somewhere? |
The purpose and use-cases of the new component
This receiver reads logs and traces from Azure Blob Storage.
Correlates with #8823
Example configuration for the component
The following settings are required:
connection_string
(no default): Azure Blob Storage connection key, which can be found in the Azure Blob Storage resource on the Azure Portal.event_hub_end_point
(no default): Azure Event Hub endpoint triggering on theBlob Create
eventThe following settings can be optionally configured:
logs_container_name
(default = "logs"): Name of the blob container with the logstraces_container_name
(default = "traces"): Name of the blob container with the tracesExample:
The receiver subscribes on the events published by Azure Blob Storage and handled by Azure Event Hub. When it receives
Blob Create
event, it reads the logs or traces from a corresponding blob and deletes it after processing.Telemetry data types supported
Logs, Traces
Sponsor
Sponsor is needed
The text was updated successfully, but these errors were encountered: