# Can curator log remotely ? e.g. syslog

**URL:** <https://discuss.elastic.co/t/can-curator-log-remotely-e-g-syslog/122727>\
**Category:** Elastic Community and Ecosystem\
**Created:** [March 6, 2018, 2:19pm UTC](https://discuss.elastic.co/t/can-curator-log-remotely-e-g-syslog/122727 "2018-03-06T14:19:27Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dan\_Gardner](https://avatars.discourse-cdn.com/v4/letter/d/ac8455/32.png) [@Dan\_Gardner](https://discuss.elastic.co/u/Dan_Gardner)\
**Post date:** [March 6, 2018, 2:19pm UTC](https://discuss.elastic.co/t/can-curator-log-remotely-e-g-syslog/122727/1 "2018-03-06T14:19:27Z")

</div>

Can the curator config (logfile) take a value to log to a central logging service rather than a file or stdout ?

For instance you can get nginx to log to a syslog server specifying the value for the access\_log as follows:

syslog:server=127.0.0.1:5140,facility=local7,tag=nginx,severity=info

---

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [March 6, 2018, 8:27pm UTC](https://discuss.elastic.co/t/can-curator-log-remotely-e-g-syslog/122727/2 "2018-03-06T20:27:46Z")

</div>

Not yet. It's a desired feature, but not implemented.

I accept pull requests... 🙂

---

<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:** [April 3, 2018, 8:27pm UTC](https://discuss.elastic.co/t/can-curator-log-remotely-e-g-syslog/122727/3 "2018-04-03T20:27:47Z")

</div>

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