Deploy this integration to forward logs from your Azure Blob Storage account to Logz.io using an automated deployment process. This integration offers the option to connect to an existing Blob storage account or create a new one, and it can be updated post-deployment.

Architecture overview

The following services are created when you deploy this integration:

  • Serverless Function App
  • Application Insights
  • App Service Plan
  • Event Hub Namespace
  • Event Grid System Topic
  • Storage Account for the Function’s logs
  • If you select the option to deploy a new account, a new Blob Storage Account is created as well.

Integration-architecture

Set up a new blob storage account

Launch an automated deployment

👇 Click this button to start.

Deploy to Azure

You’ll be taken to Azure, where you’ll configure the resources to be deployed.

Fill in the form
Parameter Description Required/Default
Resource group Click Create new. Give a meaningful Name, such as “logziobBlobStorageIntegration”, and then click OK. Required
Location Select the same region as the Azure services that will stream data to this Blob Storage. Required
Logzio host Use the listener URL specific to the region of your Logz.io account. You can look it up here. Required
Log shipping token Your Logz.io log shipping token directs the data securely to your Logz.io Log Management account. The default token is auto-populated in the examples when you’re logged into the Logz.io app as an Admin. Manage your tokens. Required
Format Select one of the supported parsing formats: text/json/csv Required
Buffersize The maximum number of messages the logger will accumulate before sending them all as a bulk 100
Timeout The read/write/connection timeout in milliseconds. 180,000 = 3 minutes

At the bottom of the page, select Review + Create, and then click Create to deploy.
Deployment can take a few minutes.

Check Logz.io for your logs

Give your logs some time to get from your system to ours, and then open Kibana. You can filter for logs of type blobStorage to see the incoming logs.

If you still don’t see your logs, see log shipping troubleshooting.

Use your existing blob storage account

Before you begin, you’ll need: a blob storage account of the type StorageV2 (general purpose v2).

If your existing blob storage account is of any other kind, it will NOT work. Instead, follow the process to set up a new blob storage account.

Check your storage account for compatibility

Double-check your Storage accounts to make sure that they are compatible with this integration. They should be of the type StorageV2 (general purpose v2).

Launch an automated deployment

👇 Click this button to start.

Deploy to Azure

You’ll be taken to Azure, where you’ll configure the resources to be deployed.

Fill in the form
Parameter Description Required/Default
Resource group Select your existing resource group. Required
Location Select the same region as the Azure services that will stream data to this Blob Storage. Required
Logzio host Use the listener URL specific to the region where your Logz.io account is hosted. Click to look up your listener URL. Required
Log shipping token Your Logz.io log shipping token directs the data securely to your Logz.io Log Management account. The default token is auto-populated in the examples when you’re logged into the Logz.io app as an Admin. Manage your tokens. Required
Format Select one of the supported parsing formats: text/json/csv Required
Buffersize The maximum number of messages the logger will accumulate before sending them all as a bulk 100
Timeout The read/write/connection timeout in milliseconds. 180,000 = 3 minutes

At the bottom of the page, select Review + Create, and then click Create to deploy. Deployment can take a few minutes. Only logs sent from this point on will be searchable in Logz.io.

Check Logz.io for your logs

Give your logs some time to get from your system to ours, and then open Kibana. You can filter for logs of type blobStorage to see the incoming logs.

If you still don’t see your logs, see log shipping troubleshooting.

Updating parameters after deployment

To update your parameters post-deployment:

  1. Open the Function App page in your Azure portal.
  2. On the left menu, select the Configuration tab.
  3. Make your edits and save your changes.

Here are the parameters that can be updated post-deployment:

  • Shipper-related configurations:
    • LogzioHost
    • LogzioToken
    • Buffersize
    • Timeout
  • FUNCTIONS_WORKER_PROCESS_COUNT - maximum of 10. See Microsoft documentation for more details.
  • ParseEmptyField - Enable/disable the option to parse logs with invalid empty fields. If you encounter an issue with services shipping unnamed fields that break the parsing pipeline, enable this flag. Note that this option may slow the shipper’s performance.

Function's configuration