# Unable to Save Fleet Settings - Logstash Output **URL:** \ **Category:** Elastic Agent\ **Created:** [July 18, 2024, 2:49am UTC](https://discuss.elastic.co/t/unable-to-save-fleet-settings-logstash-output/363309 "2024-07-18T02:49:03Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![wangsubo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wangsubo/32/133865_2.png) [@wangsubo](https://discuss.elastic.co/u/wangsubo)\ **Post date:** [July 18, 2024, 2:49am UTC](https://discuss.elastic.co/t/unable-to-save-fleet-settings-logstash-output/363309/1 "2024-07-18T02:49:03Z")
I am experiencing issues with saving my Fleet settings Logstash Output . Despite multiple attempts, the configuration just won't save. Could this be related to using the free version? Has anyone else encountered this problem or have any insights on what might be causing this issue? Any help or suggestions would be greatly appreciated! ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/3/03897028bc1531b436316e2fd0ca2bcb05bc4a54.png) Thanks ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [July 18, 2024, 3:44am UTC](https://discuss.elastic.co/t/unable-to-save-fleet-settings-logstash-output/363309/2 "2024-07-18T03:44:09Z")
> [@wangsubo](#): > > Despite multiple attempts, the configuration just won't save. What will not save? Your screenshot is in Japanese, can you provide more context or share it in English? > [@wangsubo](#): > > Could this be related to using the free version? The basic license has a limitation that does not allow you to have a different output per policy, but you can use the logstash or kafka output if you want. To do that you need to add an logstash output and set it as the default output for Logs and Monitoring, you need to have an elasticsearch output as well because the Fleet Server can only output to Elasticsearch, never to Logstash or Kafka. After that you will see that your fleet policy will still be configured to send logs to Elasticsearch, but your other policies will only use the default output, which will be logstash now. You need to have something like this in your Fleet output settings. ![Screenshot from 2024-07-18 00-39-07](https://us1.discourse-cdn.com/elastic/original/3X/3/f/3f5d0f7b88713b5587fbda2a16c15c202ec48d89.png) Then, your fleet server policy will have a configuration like this: ![Screenshot from 2024-07-18 00-39-43](https://us1.discourse-cdn.com/elastic/original/3X/6/a/6a0c934c89025395e26fd428d90ac1e5cb6d8467.png) And any other policy will have an output like this: ![Screenshot from 2024-07-18 00-40-06](https://us1.discourse-cdn.com/elastic/original/3X/2/6/26a78cc17a20c7a80bd85897bdd7981a26ec9bf9.png) ---
**Author:** ![wangsubo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wangsubo/32/133865_2.png) [@wangsubo](https://discuss.elastic.co/u/wangsubo)\ **Post date:** [July 18, 2024, 5:06am UTC](https://discuss.elastic.co/t/unable-to-save-fleet-settings-logstash-output/363309/3 "2024-07-18T05:06:00Z")
After I input the Fleet Logstash Output configurations, including certificates, etc., and I want to Save and apply settings, the Save and apply settings button is currently grayed out and cannot be saved. ![2024-07-18_13-11-41](https://us1.discourse-cdn.com/elastic/original/3X/5/1/51d4180129e7acb4a39527a46799399eb7c4a927.jpeg) ![2024-07-18_13-08-03](https://us1.discourse-cdn.com/elastic/original/3X/7/c/7c1021b8a20dd3c3810e38eead418f0cf58940ce.jpeg) Normally, the Save and apply settings button should be blue, indicating that it can be saved. ![2024-07-18_11-46-42](https://us1.discourse-cdn.com/elastic/original/3X/3/0/3087763b473d9587b257b08e9aa65994eabbf548.jpeg) I’m not quite sure why it cannot be saved. ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [July 18, 2024, 5:24am UTC](https://discuss.elastic.co/t/unable-to-save-fleet-settings-logstash-output/363309/4 "2024-07-18T05:24:46Z")
There is a warning saying that Additional setup is required, your Kibana configuration is incomplete. It mentions that you need to configure an encryption key before configuring the output, you won't be able to save it until you fix this. Did you click in the _learn more_ link? It is probably related to the saved object encryption key, did you add one to your `kibana.yml`? You need to add it or some things will not work, for more context check the [documentation](https://www.elastic.co/guide/en/kibana/current/xpack-security-secure-saved-objects.html). ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [July 18, 2024, 5:29am UTC](https://discuss.elastic.co/t/unable-to-save-fleet-settings-logstash-output/363309/5 "2024-07-18T05:29:20Z")
Looking at the part of kibana code that generates this message, it is indeed related to the encryption key for saved objects in Kibana. This is the part of the [code](https://github.com/elastic/kibana/blob/838fada8ca7d7287dfcd313e5cf136666304e9d4/x-pack/plugins/fleet/public/applications/fleet/sections/settings/components/edit_output_flyout/encryption_key_required_callout.tsx#L27-L40): ```auto ), }} /> ``` The link mentions the saved objects: > **kibana.secureSavedObject** So, you need to follow this [doc](https://www.elastic.co/guide/en/kibana/current/xpack-security-secure-saved-objects.html) and add an encryption key in your `kibana.yml`. ---
**Author:** ![Prosenjeet33](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/prosenjeet33/32/123725_2.png) [@Prosenjeet33](https://discuss.elastic.co/u/Prosenjeet33)\ **Post date:** [October 21, 2024, 7:53pm UTC](https://discuss.elastic.co/t/unable-to-save-fleet-settings-logstash-output/363309/6 "2024-10-21T19:53:34Z")
The code you've shared is related to a warning in Kibana, specifically within the Fleet plugin, informing users that they must configure an encryption key for saved objects. The message includes a link to Kibana's documentation, which explains how to configure the encryption key for secured saved objects. Kibana uses saved objects to persist user data, and the encryption key is needed to protect sensitive data. ### Explanation of the Code: - **`FormattedMessage`** : Part of the `react-intl` library, which is used for internationalization. The `id` property (e.g., `"xpack.fleet.encryptionKeyRequired.calloutDescription"`) is a unique key for translations, and `defaultMessage` is the fallback text if no translation is provided. - **`EuiLink`** : This component from Elastic UI (EUI) renders a clickable link. The `href` attribute points to the URL of the Kibana documentation (`docLinks.links.kibana.secureSavedObject`). The `target="_blank"` opens the link in a new tab, and the `external` attribute indicates that the link leads to an external website. - **`values`** : This object allows the `FormattedMessage` to include dynamic content. In this case, the `{link}` placeholder in `defaultMessage` is replaced by an actual link generated by the `EuiLink` component. ### Issues to Look For: 1. **`docLinks` Undefined** : Ensure that `docLinks` is properly imported and contains the correct path (`docLinks.links.kibana.secureSavedObject`) pointing to the Kibana documentation. If `docLinks` is undefined, the link won't work. 2. **Incorrect Translation ID** : Ensure that the translation IDs (`xpack.fleet.encryptionKeyRequired.calloutDescription` and `xpack.fleet.encryptionKeyRequired.link`) are unique and match the corresponding translation files. If the IDs are incorrect, the message might not be translated or displayed properly. 3. **EUI Version Compatibility** : The `EuiLink` component and the `external` prop must be supported by your version of Elastic UI. Make sure that your EUI version supports this usage. ### Debugging Steps: - **Check if `docLinks` is available** : Log the value of `docLinks.links.kibana.secureSavedObject` to see if it’s correctly populated. - **Verify Translation Files** : Ensure that the translation keys (`xpack.fleet.encryptionKeyRequired.calloutDescription` and `xpack.fleet.encryptionKeyRequired.link`) are correctly defined in the translation JSON files. - **Ensure EUI Link Props** : Ensure that `external` and `target="_blank"` are used properly and supported by your version of EUI. You can check the EUI documentation for the correct prop usage.