Queue Storage: Microsoft Azure Functions

Coralogix provides seamless integration with Azure cloud so you can send your logs from anywhere and parse them according to your needs.

The Azure Queue Storage integration allows parsing of queue messages in JSON format. Other format messages will not be processed and submitted to the Coralogix platform.

Prerequisites

• A Coralogix account
• A Coralogix private key
• An Azure account with an active subscription.
• Azure Functions Core Tools version 4
• Azure CLI version 2.44.0
• Node.js version 16

Installation

Clone this repo:

$ git clone https://github.com/coralogix/coralogix-azure-serverless.git
$ cd coralogix-azure-serverless/StorageQueue

Login with Azure cli:

$ az login

Install Azure Functions Core Tools:

$ make functools

Configure (Replace environment variables with appropriate values) and install Coralogix function for Azure Functions. Replace the following environment variables:

• Coralogix private key
• Application and subsystem names

# A Unique Identifier to ensure successful deployment of resources with universally unique requirements
export UUID=$(od -vN "7" -An -tx1 /dev/urandom|tr -d " \n"; echo)
# Storage Account "Connection String"
export QUEUE_STORAGE_ACCOUNT_CONNECTION_STRING=<YOUR_STORAGE_ACCOUNT_CONNECTION_STRING>

# Private key for Coralogix
export CORALOGIX_PRIVATE_KEY=YOUR_PRIVATE_KEY
# Desired Application name and Subsystem name for ingested Storage Queue messages
export CORALOGIX_APP_NAME=YOUR_APP_NAME
export CORALOGIX_SUB_SYSTEM=YOUR_SUB_SYSTEM_NAME

make install
make configure
make publish

The <YOUR_STORAGE_ACCOUNT_CONNECTION_STRING> should be replaced with Storage Account connection string which you can find in Storage Account -> Access keys -> Connection string. It should look like this:

DefaultEndpointsProtocol=https;AccountName=YOUR_ACCOUNT;AccountKey=YOUR_ACCOUNT_KEY;EndpointSuffix=core.windows.net

Queue Storage Customization

By default the StorageQueue function will be triggered when you add messages to logs Queue Storage in your Storage Account. You can change this to your custom container name in file StorageQueue/function.json (bindings.queueName parameter):

{
  "bindings": [
    {
      "name": "queueItem",
      "type": "queueTrigger",
      "direction": "in",
      "queueName": "logs",
      "connection": "AzureWebJobsStorage"
    }
  ],
  "scriptFile": "../dist/StorageQueue/index.js"
}

Additional Resources

Support

Need help?

Our world-class customer success team is available 24/7 to walk you through your setup and answer any questions that may come up.

Feel free to reach out to us via our in-app chat or by sending us an email at [email protected].