# Setting up logs functionality with fluentd

**URL:** <https://discuss.elastic.co/t/setting-up-logs-functionality-with-fluentd/169923>\
**Category:** Logs\
**Created:** [February 26, 2019, 12:13am UTC](https://discuss.elastic.co/t/setting-up-logs-functionality-with-fluentd/169923 "2019-02-26T00:13:16Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Mary92](https://avatars.discourse-cdn.com/v4/letter/m/85e7bf/32.png) [@Mary92](https://discuss.elastic.co/u/Mary92)\
**Post date:** [March 23, 2019, 9:22am UTC](https://discuss.elastic.co/t/setting-up-logs-functionality-with-fluentd/169923/4 "2019-03-23T09:22:34Z")

</div>

> [@Kerry](#):
>
> Hi @Erik_Tribou,
> 
> The `xpack.infra.sources.default.fields.message` configuration option is broken at present.
> 
> Currently, the UI uses a heuristic to attempt to generate the log message for a number of known Filebeat modules. After this we fallback to the `message` and `@message` fields of the document. [kissanime](https://www.kissanime.vip/)
> 
> If you ingest your logs with a `message` or `@message` field you should see your logs in the Logs UI.
> 
> You _might_ be able to[setup a field alias for this if that's an easier route. In 6.5 this is only possible if the index uses the setting `index.mapping.single_type: true`.
> 
> Apologies for this, we are looking to extend configuration of the Logs UI in the future.

Thank you so much for this post..

---

_[View the full topic](https://discuss.elastic.co/t/setting-up-logs-functionality-with-fluentd/169923)._