# System Integration not Parsing SSH Failures

**URL:** https://discuss.elastic.co/t/system-integration-not-parsing-ssh-failures/304394
**Category:** Beats
**Tags:** filebeat, ingest-pipeline
**Created:** [May 10, 2022, 8:52pm UTC](https://discuss.elastic.co/t/system-integration-not-parsing-ssh-failures/304394 "2022-05-10T20:52:52Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![ericbarnes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ericbarnes/32/31868_2.png) [@ericbarnes](https://discuss.elastic.co/u/ericbarnes)
#### Post date: [May 10, 2022, 8:52pm UTC](https://discuss.elastic.co/t/system-integration-not-parsing-ssh-failures/304394/1 "2022-05-10T20:52:52Z")

</div>

Elasticsearch/Kibana Version = 8.2

I'm starting a new cluster and want to verify all of the default dashboards and ingest paths are working correctly. I am using Fleet to manage the agents and integrations.

For the System Integration, successful SSH events will produce 'system.auth.ssh.event : Accepted'  
BUT failed logins will not produce and 'system.auth.ssh.event' value at all.

The created index is .ds-logs-system.auth-default-YYYY.MM.DD-00000X and the Data Stream is 'logs-system.auth-default.' The associated Index Template is 'logs-system.auth' and the index default pipeline is 'logs-system.auth-1.6.4'

I am pretty sure this worked just fine in version 8.0 but I don't see anyway to downgrade the system integration package to verify - other than blow this away and build a new environment.

Any thoughts

---

<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: [June 7, 2022, 10:53pm UTC](https://discuss.elastic.co/t/system-integration-not-parsing-ssh-failures/304394/2 "2022-06-07T22:53:50Z")

</div>

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