-
Notifications
You must be signed in to change notification settings - Fork 511
Open
Labels
Integration:eset_protectESET PROTECTESET PROTECTTeam:Security-Service IntegrationsSecurity Service Integrations team [elastic/security-service-integrations]Security Service Integrations team [elastic/security-service-integrations]needs:triage
Description
Integration Name
ESET PROTECT [eset_protect]
Dataset Name
No response
Integration Version
1.11.0
Agent Version
9.2.0
Agent Output Type
elasticsearch
Elasticsearch Version
9.2.0
OS Version and Architecture
Kubernetes
Software/API Version
No response
Error Message
When using syslog on the ESET PROTECT integration on a v9.2 elastic agent, syslog messages become fragmented and parsing fails. Sometimes multiple messages will be combined into one, sometimes messages will have either the beginning or the end cut off.
Event Original
":""Information""}
<14>1 2025-11-03T11:15:08.064231Z b1708952-fb6c-48f8-a78f-fa08ae9f582b ERAServer 8999 - - {""occured"":""03-Nov-2025 11:12:44"",""domain"":""ESET Inspect"",""action"":""Detections"",""result"":""Success"",""detail"":""Detection \""Firewall resolved"",""event_type"":""Audit_Event"",""severity"":""Infor"
What did you do?
I've tried adding:
framing: delimiter
delimiter: \nBut that has not solved the issue. It does work for some of the events. But will now also split a message when a powershell script with "\n" in it is sent for example. Using the exact same integration policy on an older agent (8.19.5) works as expected.
What did you see?
The end of one message and the start of a second message
What did you expect to see?
One whole message
Anything else?
No response
Metadata
Metadata
Assignees
Labels
Integration:eset_protectESET PROTECTESET PROTECTTeam:Security-Service IntegrationsSecurity Service Integrations team [elastic/security-service-integrations]Security Service Integrations team [elastic/security-service-integrations]needs:triage