# Problem with syslog in Fleet-Elastic agent-System Integration

**URL:** <https://discuss.elastic.co/t/problem-with-syslog-in-fleet-elastic-agent-system-integration/262464>\
**Category:** Beats\
**Tags:** fleet\
**Created:** [January 28, 2021, 8:41am UTC](https://discuss.elastic.co/t/problem-with-syslog-in-fleet-elastic-agent-system-integration/262464 "2021-01-28T08:41:06Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bjarnej](https://avatars.discourse-cdn.com/v4/letter/b/9e8a1a/32.png) [@bjarnej](https://discuss.elastic.co/u/bjarnej)\
**Post date:** [January 28, 2021, 8:41am UTC](https://discuss.elastic.co/t/problem-with-syslog-in-fleet-elastic-agent-system-integration/262464/1 "2021-01-28T08:41:06Z")

</div>

I deployed an Elastic Agent 7.10.2 on Debian Linux using Fleet and the "System Integration", all metric logs disabled.  
Default the System integration will look in:  
/var/log/auth.log\* and /var/log/secure\* for "System auth" logs and  
/var/log/messages\* and /var/log/syslog\* for "System syslog" logs.  
I made a small test trying to login via SSH with an unknown user.  
This only ingest a syslog entry to Elastic Cloud and the log entry is only in the "message" field not mapped out in separate fields.  
Now if I delete "/var/log/syslog\*" in the Agent policy on the system integration then I suddenly get auth logs into Elastic and the log entry is mapped into different field e.g. user.name.

Can anyone confirm/verify that this is a bug?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 25, 2021, 10:41am UTC](https://discuss.elastic.co/t/problem-with-syslog-in-fleet-elastic-agent-system-integration/262464/2 "2021-02-25T10:41:07Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.