All Apps and Add-ons

Data Parsing Issue - Ingesting The Logs Using Splunk Add-On For Microsoft Cloud Services

anandhalagaras1
Contributor

Hi All,

We initially received a requirement to configure and ingest logs from Azure Storage Blob. To address this, we installed the Splunk Add-On for Microsoft Cloud Services on our Heavy Forwarder servers and configured it to pull logs from Azure Storage Blob using the Azure Storage Account.

Currently, there's a new requirement to ingest Databricks logs from Azure Storage Blob. We completed the necessary configurations and set the default sourcetype to mscs:storage:blob for data parsing. While the events are visible in Splunk after the configuration, we noticed that the data parsing is not functioning as expected for these events.

As a troubleshooting step, I changed the sourcetype to mscs:storage:blob:json, but the issue still persists.

Could you please assist me in resolving this issue? Your guidance would be greatly appreciated.

 

Labels (3)
0 Karma

rishabhshah
Path Finder

Could you please share the sample raw logs and how are those looking in Splunk once they are ingested? Issues with Line breaking, timestamp assignment, field extraction?

0 Karma

kiran_panchavat
SplunkTrust
SplunkTrust

@anandhalagaras1 

Have you checked this community page?

https://community.splunk.com/t5/All-Apps-and-Add-ons/Splunk-Add-on-for-Microsoft-Cloud-Services-How-... 

Did this help? If yes, please consider giving kudos, marking it as the solution, or commenting for clarification — your feedback keeps the community going!
0 Karma

anandhalagaras1
Contributor

@kiran_panchavat ,

I have tried the same as per the community page but still its the same the data are not getting parsed.

0 Karma

anandhalagaras1
Contributor

Can anyone help on my request.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...