Edge Delta Azure Blob Destination
Send logs to an Azure Blob Storage endpoint.
less than a minute
You can configure outputs for your fleets by adding and configuring destination nodes. Alternatively, you can reference Destinations.
A destination is an organization-level output configuration whose settings you can use to quickly create and populate individual destination nodes.
To create a destination:
As with node names, destination names containing a period character (.
) will not pass validation.
If you add a pre-configured destination to a fleet and then make changes to it in the Fleet pipeline, those changes will take precedence over the original settings configured in the Destinations tab of the Pipelines page.
To add a destination to a Fleet:
For v2 configurations or Monitor Notifications,see Legacy Integrations.
Send logs to an Azure Blob Storage endpoint.
Send logs to Datadog.
View data items being processed with the Debug destination node.
Send logs to a DigitalOcean Spaces endpoint.
Configure the Edge Delta Destination Node.
Enable log search for the Edge Delta app.
Configure the Edge Delta Metrics Node.
Send pattern data from the Edge Delta Pattern Node.
Configure the Edge Delta Trace Destination Node.
Send logs to Elastic.
Send items to Fluentd destinations.
Archive using a Google Cloud Logging destination.
Archive using a Google Cloud Storage destination.
Send analytics and insights to an HTTP destination.
Send items to an IBM Object Storage destination.
Send logs to Kafka.
Send items to a Local Storage destination.
Send logs to Loki.
Send alerts to Microsoft Teams using a node.
Send items to a MinIO destination.
Send items to a New Relic destination.
Send logs to OpenMetrics.
Configure the Edge Delta Prometheus Exporter destination node.
Send items to an S3 destination.
Send alerts to Slack using a node.
Send items to a Splunk destination.
Send items to a Sumo Logic destination.
Send analytics and insights to a TCP destination.
Send data to a webhook.
Send items to a Zenko CloudServer destination.