[Cisco ise] Prevent throwing a error whenever grok_time_details fails#20069
Conversation
…e_details fails. Declare error.message in the field mappings.
|
Pinging @elastic/integration-experience (Team:Integration-Experience) |
# Conflicts: # packages/cisco_ise/changelog.yml
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
🚀 Benchmarks reportTo see the full report comment with |
… date as a fallback.
|
No issues across the latest commits 3cb081f.
🤖 AI-Generated Review | Vera Review Bot | 📚 Knowledge base: integration-skills
|
|
✅ All changelog entries have the correct PR link. |
💚 Build Succeeded
History
|
|
Tick the box to add this pull request to the merge queue (same as
|
|
Package cisco_ise - 1.32.9 containing this change is available at https://epr.elastic.co/package/cisco_ise/1.32.9/ |
Proposed commit message
Guard the cisco_ise.log date processors so they skip when no timestamp was parsed, eliminating a redundant error.
Checklist
- [ ] I have verified that all data streams collect metrics or logs.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 practicesRelated issues
https://github.com/elastic/sdh-beats/issues/7347
Screenshots