All Apps and Add-ons

Cloud Adjustments Needed

ChrisBell04
Communicator

This app on-prem works well enough.

Cloud, where no inputs are allowed, there are some modifications needed.
1) Subscription ID dropdown. the REST query for inputs to extract subscriptions will never work. Maybe something like this instead:

`azure-audit` (subscription_id="*") 
| stats count by subscription_id 
| table subscription_id

2) The inputs_not_configured warning, again doesnt make sense. What about something more dynamic (like the splunk app for Windows Infrastructure), which looks for samples of sourcetypes it needs?

3) minor enhancement for extracting subnet details

props.conf
[source::/subscriptions/...]
REPORT-subnet = azure_extract_resource_field_subnet

transforms.conf
[azure_extract_resource_field_subnet]
SOURCE_KEY = source
REGEX = (?i)\.*\/subnets\/([\w\-]+)
FORMAT = resource_subnet::$1
0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Level Up Your .conf25: Splunk Arcade Comes to Boston

With .conf25 right around the corner in Boston, there’s a lot to look forward to — inspiring keynotes, ...

Manual Instrumentation with Splunk Observability Cloud: How to Instrument Frontend ...

Although it might seem daunting, as we’ve seen in this series, manual instrumentation can be straightforward ...

Take Action Automatically on Splunk Alerts with Red Hat Ansible Automation Platform

Ready to make your IT operations smarter and more efficient? Discover how to automate Splunk alerts with Red ...