-
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 Exporter #8823
Comments
@open-telemetry/collector-contrib-approvers, looks like we don't have any volunteers for this. How should we seed the round-robin list? I guess this is the first time we couldn't actually find a sponsor for a component. |
What's the general direction here? Is it possible to leverage some general binding, e.g. Dapr https://docs.dapr.io/reference/components-reference/supported-bindings/localstorage/. |
The component, along with #8834, is used to collect traces and logs from disconnected IoT Edge devices. |
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)? |
Since I volunteered as sponsor for S3 Exporter I would like to volunteer as Azure Exporter as well. As we discussed during the SIG, the work should be synchronized and share common code |
@pmm-sumo - How's the Exporter component going? We have implemented a workable prototype of Azure Blob exporter. I think it would be great if we can commit some of our work into this thread. |
@WenheLI there's a work in progress by @pdelewski. Actually the initial PR is waiting for approval by other approvers right now and the second one is also waiting in the pipeline |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
@pmm-sumo Wondering if there's been any progress on this front recently? |
@pdelewski gotcha - is there a good contact for this sort of stuff (where it's at in terms of review process etc)? |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Does opentelemetry contrib-collector supports Azure Blob Exporter? |
This comment was marked as spam.
This comment was marked as spam.
hello @mx-psi! this'll be a great addition :) |
This comment was marked as spam.
This comment was marked as spam.
This component does not have a sponsor and there is nobody actively wormking on it. The previous sponsor is no longer involved in the project. If you want this component to be added you will need to find a sponsor and to actively contribute the code for it. Please refrain from '+1' or 'ping' comments, these will not get more attention to this component |
The purpose and use-cases of the new component
This exporter saves logs and traces to Azure Blob Storage.
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.The following settings can be optionally configured:
logs_container_name
(default = "logs"): Name of the container where the exporter saves blobs with logs.traces_container_name
(default = "traces"): Name of the container where the exporter saves blobs with traces.Example:
Telemetry data types supported
Logs, Traces
The text was updated successfully, but these errors were encountered: