# Fleet CEF Processor
**URL:** https://discuss.elastic.co/t/fleet-cef-processor/296790
**Category:** Beats
**Tags:** beats-module
**Created:** [February 9, 2022, 10:49pm UTC](https://discuss.elastic.co/t/fleet-cef-processor/296790 "2022-02-09T22:49:39Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@bm11100](https://discuss.elastic.co/u/bm11100)
#### Post date: [February 9, 2022, 10:49pm UTC](https://discuss.elastic.co/t/fleet-cef-processor/296790/1 "2022-02-09T22:49:40Z")
Hello,
We are trying to use the CEF integration to parse syslogs sent over from SentinelOne, but are getting an error message on processing which appears to be due to the date format.
Error - `Text '2022-02-09 00:25:02,862' could not be parsed, unparsed text found at index 10`
Is there a simple fix to parsing this correctly that I could try?
Also, any plans on adding the ability to specify an event dataset name other than `cef`, like with other integrations (UDP).
Thanks
---
### Author:  [@kvch](https://discuss.elastic.co/u/kvch)
#### Post date: [February 10, 2022, 5:22pm UTC](https://discuss.elastic.co/t/fleet-cef-processor/296790/2 "2022-02-10T17:22:17Z")
How did you configure it? Integration from Kibana or from Beats?
---
### Author:  [@bm11100](https://discuss.elastic.co/u/bm11100)
#### Post date: [February 10, 2022, 6:44pm UTC](https://discuss.elastic.co/t/fleet-cef-processor/296790/3 "2022-02-10T18:44:52Z")
This is using the integration from Fleet. Using the `logs-cef.log-1.3.1` pipeline.
```auto
{
"index": {
"default_pipeline": "logs-cef.log-1.3.1"
}
}
```
---
### Author:  [@kvch](https://discuss.elastic.co/u/kvch)
#### Post date: [February 11, 2022, 10:27am UTC](https://discuss.elastic.co/t/fleet-cef-processor/296790/4 "2022-02-11T10:27:08Z")
Could you please open an issue here? [Sign in to GitHub · GitHub](https://github.com/elastic/integrations/issues/new)
---
### Author:  [@bm11100](https://discuss.elastic.co/u/bm11100)
#### Post date: [February 11, 2022, 1:03pm UTC](https://discuss.elastic.co/t/fleet-cef-processor/296790/5 "2022-02-11T13:03:25Z")
Yea I can but is there something I can do now to get it working?
---
### Author:  [@kvch](https://discuss.elastic.co/u/kvch)
#### Post date: [February 11, 2022, 2:19pm UTC](https://discuss.elastic.co/t/fleet-cef-processor/296790/6 "2022-02-11T14:19:52Z")
Well, you can try to edit manually the Ingest pipeline to parse the timestamp correctly, but reporting the bug should be a simpler solution.
---
### Author:  [@bm11100](https://discuss.elastic.co/u/bm11100)
#### Post date: [February 11, 2022, 3:20pm UTC](https://discuss.elastic.co/t/fleet-cef-processor/296790/7 "2022-02-11T15:20:51Z")
Created an issue [Fleet CEF Integration Parsing Timestamp Error · Issue #2676 · elastic/integrations (github.com)](https://github.com/elastic/integrations/issues/2676)
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 11, 2022, 5:21pm UTC](https://discuss.elastic.co/t/fleet-cef-processor/296790/8 "2022-03-11T17:21:04Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.