Microsoft Log Analytics Add-on (Formerly Known as OMS)
Overview
Details
This app allows you to pull data from api.loganalytics.io using the OMS / Log Analytics query language.
You will need the following before you can configure any inputs:
Resource Group
Workspace ID
Subscription ID
Tenant ID
Application ID
Application Key
Log Analytics (OMS) Query
You can find details on how to configure the items needed to pull the data found here: https://dev.loganalytics.io/
Special thanks to @dpanych for his assistance with the code.
THIS APP WORKS ON SPLUNK ENTERPRISE ONLY
- Doesnt work on Universal Forwarders / Light Forwarders
- Requires Splunk's built in Python 2.7
- No coders were harmed in the making, just the Azure rate limiters
Overview
This will create inputs with sourcetype=loganalytics. To use this add-on install it on a heavy forwarder or standalone splunk instance. In distributed environments, you'll want to copy the props.conf settings to your search heads as well.
Installation
-Standalone Splunk Enterprise Instance: Install app via UI, configure app via UI, profit.
-Heavy Forwarder Instance: Install app via UI, configure app via UI or CLI, put props.conf on search heads, ensure your HF is forwarding to your indexers, profit.
Special Considerations
-
This app assumes you've previously configured the Azure components needed. See https://dev.loganalytics.io/ for instructions on configuring these.
-
Log Analytics events have a lag time until they are available. Therefore this app doesnt support real time data collection. We also coded the add-on to have a lag of 15 minutes on the collection. This means the most recent query to the API will look for data from the delta of the last check until now minus 15 minutes. This effectively makes all your Log Analytics data 15+ minutes old on arrival. You can adjust this setting in the add-on but it is recommended you do not set below 10 minutes. This is a limitation on how the data arrives at Log Analytics, and not a Splunk limitation or this app's limitation.
Changes to this setting should also consider the interval defined for the input (defaults to 5 minutes).
Troubleshooting:
Be sure the python scripts in /bin are executable ("chmod +x /path/to/TA-ms-loganalytics/bin/.py")
Be sure to restart Splunk after installation
Check for errors ("index=_internal log_level=err OR log_level=warn loganalytics*")
Contact the author via contact link here on splunkbase or by tagging @jkat54 on answers.splunk.com
Release Notes
Version 1.0.3
Version 1.0.3:
- Checkpoint bug-fix
- Added TIME_PREFIX and TIME_FORMAT to props
- Fixed line break issue
Thanks to those who reported problems and those who helped solve them as well!
https://answers.splunk.com/answers/684463/issue-in-microsoft-log-analytics-add-onformerly-kn.html
https://answers.splunk.com/answers/680955/why-am-i-getting-a-winsock-error-10053-while-using.html