Fix/cisco meraki update #2137
Merged
Fix/cisco meraki update #2137
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rjha-splunk
approved these changes
Aug 14, 2023
|
🎉 This PR is included in version 3.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In issue #2088 a user requested updating Meraki parser from community TA to Splunk supported TA.
Current production Meraki parser is based on vendor product by source configuration due to its general log format. There is also this note in the documentation:
However, official Splunk TA for Cisco Meraki assigns various sourcetypes.
This PR retains previous solution for general Meraki logs, but also introduces
syslog-appandalmost-syslog-appparsers with sourcetypes corresponding to the new TA whenever hostname and program value enable it.