[cisco_asa] Support special chars in interface name for 315011 log messages #15242
Conversation
This file contains hidden or 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
bhapas added Integration:cisco_asa 
bhapas force-pushed the fix_cisco_asa_315011 branch from 9763952 to bf23b3c Compare 
bhapas force-pushed the fix_cisco_asa_315011 branch from 94085d1 to cf70301 Compare 
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
History
cc @bhapas |
|
| Package cisco_asa - 2.43.8 containing this change is available at https://epr.elastic.co/package/cisco_asa/2.43.8/ |
tehbooom pushed a commit to tehbooom/integrations that referenced this pull request Nov 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
3 participants
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.
Proposed commit message
Support special characters in interface name for 315011 log messages
Currently it fails if there is a Hyphen
-character in interface name.Checklist
changelog.ymlfile.- [ ] I have verified that Kibana version constraints are current according to guidelines.- [ ] I have verified that any added dashboard complies with Kibana's Dashboard good practicesHow to test this PR locally
elastic-package stack up -d -v & elastic-package test pipelineRelated issues