Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Meraki logs not being filtered #686

Closed
RathHunt opened this issue May 14, 2024 · 1 comment
Closed

[BUG] Meraki logs not being filtered #686

RathHunt opened this issue May 14, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@RathHunt
Copy link
Contributor

Describe the bug

Cisco Meraki logs are not being caught by the Logstash filter. The logs remain in the generic category despite attempts to filter them.

To Reproduce

Steps to reproduce the behavior:

Send Meraki logs to the utmstack agent
See that the logs are not being filtered and remain in the generic category

Expected behavior

The expected behavior is that the Cisco Meraki logs would be filtered out from the generic category and categorized appropriately.

Screenshots

image

Environment

OS: [Please specify]
Browser: [Please specify]
Version: [Please specify]
Additional context

The specific log entry that was tested is: 1377449842.514782056 MX84 ids-alerts signature=129:4:1 priority=1 timestamp=1377449842.512569 direction=ingress protocol=tcp/ip src=74.125.140.132:80

@RathHunt RathHunt added the bug Something isn't working label May 14, 2024
@c3s4rfred
Copy link
Contributor

The log wasn't sent with the correct format, also the integration wasn't active.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants