# Elastic agent: "output not supported" using Logstash output on 8.6

**URL:** <https://discuss.elastic.co/t/elastic-agent-output-not-supported-using-logstash-output-on-8-6/326010>\
**Category:** Beats\
**Tags:** fleet\
**Created:** [February 20, 2023, 11:43pm UTC](https://discuss.elastic.co/t/elastic-agent-output-not-supported-using-logstash-output-on-8-6/326010 "2023-02-20T23:43:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ceekay](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ceekay/32/5687_2.png) [@ceekay](https://discuss.elastic.co/u/ceekay)\
**Post date:** [February 20, 2023, 11:43pm UTC](https://discuss.elastic.co/t/elastic-agent-output-not-supported-using-logstash-output-on-8-6/326010/1 "2023-02-20T23:43:36Z")

</div>

Hi all,

I have a previously working\* Fleet/Agent config with `8.5.3` and Logstash output configured.

\* aside from [8.5.1 agents go unhealthy · Issue #1790 · elastic/elastic-agent · GitHub](https://github.com/elastic/elastic-agent/issues/1790) but I have a workaround for this.

When upgraded to `8.6.x`, agents will fail to connect to the Logstash output and appear offline in the Fleet Agent interface.

I don't see anything of note in the logs other than various beats reporting in, however `elastic-agent status` shows `output not supported` for an unnamed component.

```auto
# elastic-agent version
Binary: 8.6.2 (build: 913c02bea9b13dec4d5c5f3057b5b397344e3298 at 2023-02-13 16:51:45 +0000 UTC)
Daemon: 8.6.2 (build: 913c02bea9b13dec4d5c5f3057b5b397344e3298 at 2023-02-13 16:51:45 +0000 UTC)

# elastic-agent status
State: DEGRADED
Message: 1 or more components/units in a failed state
Components:
  * beat/metrics (HEALTHY)
                    Healthy: communicating with pid '80217'
  * log (HEALTHY)
                    Healthy: communicating with pid '80185'
  * system/metrics (HEALTHY)
                    Healthy: communicating with pid '80192'
  * (FAILED)
                    output not supported
  * http/metrics (HEALTHY)
                    Healthy: communicating with pid '80201'
  * filestream (HEALTHY)
                    Healthy: communicating with pid '80208'

```

Logstash, Elasticsearch and Kibana are all 8.6.2.

Switching back to Elasticsearch output and things appear fine however, this is not a solution for me as ES is only directly reachable by a subset of my agents.

Any ideas or should I open an issue? It's 100% unusable in this state as all agents go offline, and I've had to downgrade the agents to 8.5.3 just to get going again.

---

<div class="post-metadata">

**Author:** ![ceekay](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ceekay/32/5687_2.png) [@ceekay](https://discuss.elastic.co/u/ceekay)\
**Post date:** [February 28, 2023, 10:36pm UTC](https://discuss.elastic.co/t/elastic-agent-output-not-supported-using-logstash-output-on-8-6/326010/2 "2023-02-28T22:36:31Z")

</div>

FYI this seems to be the issue: [[Fleet] Prevent output changing types from Elasticsearch -\> Logstash if a Fleet Server policy uses it · Issue #152234 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/152234)

---

<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:** [March 29, 2023, 12:36am UTC](https://discuss.elastic.co/t/elastic-agent-output-not-supported-using-logstash-output-on-8-6/326010/3 "2023-03-29T00:36:42Z")

</div>

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