# Logging Configuration UI - ClusterOutput in Flows issue

**URL:** <https://forums.suse.com/t/logging-configuration-ui-clusteroutput-in-flows-issue/20339>\
**Category:** SUSE Rancher Prime\
**Created:** [May 18, 2021, 7:37pm UTC](https://forums.suse.com/t/logging-configuration-ui-clusteroutput-in-flows-issue/20339 "2021-05-18T19:37:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dkerov](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/dkerov/32/7563_2.png) [@dkerov](https://forums.suse.com/u/dkerov)\
**Post date:** [May 18, 2021, 7:37pm UTC](https://forums.suse.com/t/logging-configuration-ui-clusteroutput-in-flows-issue/20339/1 "2021-05-18T19:37:09Z")

</div>

In Rancher 2.5.5 when I install Logging I can then configure ClusterOutput and use it in a Flow in any namespace.

Same thing does not work in 2.5.7 and does not work in 2.5.8.  
Here is a scenario

- I have ElasticSearch Cluster Output configured and tested with a ClusterFlow

Now I

- go to Flow (no a Cluster one, just a Flow)
- Create
- set Name
- Select “default” namespace
- Switch to Outputs
- Cluster Outputs dropdown has only “Sorry, no matching options.”  
I expect to see my configured ClusterOutput there.

And tt seem that this is just a UI issue. If I now

- Select cattle-logging-system namespace
- my ClusterOutput does show up in the dropdown and I can select it.
- then I can switch namespace back to “default”
- and ClusterOutput selected will stay in place - with a small circled “i” poping up with “This cluster output doesn’t exist”
- though Flow with this ClusterOutput works perfectly fine.

Thank you  
DK

---

<div class="post-metadata">

**Author:** ![Nicolas\_Forney](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/nicolas_forney/32/9562_2.png) [@Nicolas\_Forney](https://forums.suse.com/u/Nicolas_Forney)\
**Post date:** [October 26, 2022, 9:18am UTC](https://forums.suse.com/t/logging-configuration-ui-clusteroutput-in-flows-issue/20339/2 "2022-10-26T09:18:00Z")

</div>

I noticed the same behavior
