[GH-ISSUE #65] get nodeName for harvester from fqdn #50

New issue

Closed

opened 2026-02-26 05:31:10 +03:00 by kerem · 2 comments

kerem commented

2026-02-26 05:31:10 +03:00

Owner

Originally created by @peterfroehlich on GitHub (Apr 5, 2013).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/65

The nodeName in the harvester.conf should be optional, with the default using the FQDN of the machine.
This would ease autodeployment of the harvester in a cluster of similar servers.

Originally created by @peterfroehlich on GitHub (Apr 5, 2013). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/65 The nodeName in the harvester.conf should be optional, with the default using the FQDN of the machine. This would ease autodeployment of the harvester in a cluster of similar servers.

kerem closed this issue

2026-02-26 05:31:10 +03:00

kerem commented

2026-02-26 05:31:11 +03:00

Author

Owner

@jochenonline commented on GitHub (Apr 5, 2013):

I have helped me with "sed", but that would be better :-)

2013/4/5 Peter Fröhlich notifications@github.com

The nodeName in the harvester.conf should be optional, with the default
using the FQDN of the machine.
This would ease autodeployment of the harvester in a cluster of similar
servers.

—
Reply to this email directly or view it on GitHubhttps://github.com/NarrativeScience/Log.io/issues/65
.

@jochenonline commented on GitHub (Apr 5, 2013): I have helped me with "sed", but that would be better :-) 2013/4/5 Peter Fröhlich notifications@github.com > The nodeName in the harvester.conf should be optional, with the default > using the FQDN of the machine. > This would ease autodeployment of the harvester in a cluster of similar > servers. > > — > Reply to this email directly or view it on GitHubhttps://github.com/NarrativeScience/Log.io/issues/65 > .

kerem commented

2026-02-26 05:31:11 +03:00

Author

Owner

@msmathers commented on GitHub (Aug 1, 2014):

This was a conscious choice of using explicit configuration. The harvester configuration can be generated during machine bootstrapping, during which user scripts generally have access to the node's name or hostname.

@msmathers commented on GitHub (Aug 1, 2014): This was a conscious choice of using explicit configuration. The harvester configuration can be generated during machine bootstrapping, during which user scripts generally have access to the node's name or hostname.

kerem referenced this issue

2026-02-26 05:31:42 +03:00

[PR #50] [CLOSED] Append lines and scroll at the end of console. #235