Follow this step by step guide to get 'logs' from your system to Logit.io:
Step 1 - Prerequisites
Before you begin you will need to ensure you have an available Azure Event Hub in your Azure Portal.
Confirm you have the following:
- An Azure SQL Database you wish to get diagnostic Logs from.
- An Eventhub you wish to stream the SQL diagnostic logs to.
Step 2 - Configure Diagnostic Logs
Once you have confirmed you have everything required it's time to configure diagnostic logging.
Choose your Azure SQL Database you wish to get diagnostic logs from. You will need to browse to the Diagnostic Settings from the left hand menu.
Go ahead and choose add diagnostic setting, enter a suitable name and then select the diagnostic logs you need.
Select stream to an Eventhub and enter the details of your Eventhub.
Once you're happy with the settings select save.
Step 3 - Configure permissions
Once you have data streaming to your Azure event hub, it is recommended to create a Consumer Group specifically for Logstash and not to reuse any default or existing groups.
The Logstash input supports multiple event hubs - the connection string for each hub can be found in the Azure Portal -> Event Hub -> Shared access policies.
example connection string Endpoint=sb://<youreventhubnamespace>.servicebus.windows.net/;SharedAccessKeyName=<yoursharedaccesspolicyname>;SharedAccessKey=<yoursharedaccesskey>;EntityPath=<youreventhubname>
A blob storage account is used to preserve state across logstash reboots. The Storage account connection string can be found in the Access Keys section under the Storage Account Settings menu in the Azure Portal
example connection string DefaultEndpointsProtocol=https;AccountName=<storage-account-name>; AccountKey=<storage-account-key>; EndpointSuffix=core.windows.net
Step 4 - Start Sending Logs to a Stack
To start pulling logs and metrics from the Azure Event Hub to your Stack you need to configure an Azure Logstash Input on your Logit.io Stack.
Step 6 - Check Logit.io for your logs
Now you should view your data:
If you don't see logs take a look at How to diagnose no data in Stack below for how to diagnose common issues.