[GH-ISSUE #144] Issues adding new node #117

Closed
opened 2026-02-26 05:31:22 +03:00 by kerem · 5 comments
Owner

Originally created by @devster31 on GitHub (Jan 7, 2015).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/144

Hi, I'm having issues adding a new node, this is my harvester.conf

exports.config = {
  nodeName: "nginx_node",
  logStreams: {
    nginx_access: [
      "/var/log/nginx/access.log"
    ],
    nginx_error: [
      "/var/log/nginx/error.log"
    ]
  }
  nodeName: "log.io_node",
  logStreams: {
    log.io_server: [
      "/var/log/upstart/log.io-server.log"
    ],
    log.io_harvester: [
      "/var/log/upstart/log.io-harvester.log"
    ]
  },
  server: {
    host: '0.0.0.0',
    port: 28777
  }
}

what am I missing?

Originally created by @devster31 on GitHub (Jan 7, 2015). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/144 Hi, I'm having issues adding a new node, this is my harvester.conf ``` exports.config = { nodeName: "nginx_node", logStreams: { nginx_access: [ "/var/log/nginx/access.log" ], nginx_error: [ "/var/log/nginx/error.log" ] } nodeName: "log.io_node", logStreams: { log.io_server: [ "/var/log/upstart/log.io-server.log" ], log.io_harvester: [ "/var/log/upstart/log.io-harvester.log" ] }, server: { host: '0.0.0.0', port: 28777 } } ``` what am I missing?
kerem closed this issue 2026-02-26 05:31:22 +03:00
Author
Owner

@aihunter666 commented on GitHub (Jan 30, 2015):

I'm meeting the same problem, did you find a solution?

<!-- gh-comment-id:72148249 --> @aihunter666 commented on GitHub (Jan 30, 2015): I'm meeting the same problem, did you find a solution?
Author
Owner

@hanneshal commented on GitHub (Jan 30, 2015):

I don't think its possible to add nodes to the harvester. Every harvester IS defacto a node, because you are on the same machine(which is node). You can only add new node streams.

regards

<!-- gh-comment-id:72176190 --> @hanneshal commented on GitHub (Jan 30, 2015): I don't think its possible to add nodes to the harvester. Every harvester IS defacto a node, because you are on the same machine(which is node). You can only add new node streams. regards
Author
Owner

@19h commented on GitHub (Mar 20, 2015):

nodeName, as it is currently implemented in the harvester that is shipping alongside Log.io, is a de-facto server descriptor. That is, you're limited to one nodeName per Server. However, you're free to implement a harvester yourself using the Server TCP interface.

Example:

  1. Register a new node appmonitor with stream associations: errors and registrations, where errors is a stream of logged exceptions that happened in your app and registrations is a stream of new registrations that happen in your app.
  2. Push respective events as you connect to the Server TCP interface.

Check out the custom harvester (CS & JS) I just build for you as an example.

Tip! If you're unable to remove the node after playing with the script, simply commit a removal:

$ telnet 127.0.0.1 28777
-node|appmonitor
<!-- gh-comment-id:83840698 --> @19h commented on GitHub (Mar 20, 2015): `nodeName`, as it is currently implemented in the harvester that is shipping alongside Log.io, is a de-facto server descriptor. That is, you're limited to one nodeName per Server. However, you're free to implement a harvester yourself using the _Server TCP interface_. Example: 1. Register a new node `appmonitor` with stream associations: `errors` and `registrations`, where `errors` is a stream of logged exceptions that happened in your app and `registrations` is a stream of new registrations that happen in your app. 2. Push respective events as you connect to the Server TCP interface. Check out the [custom harvester](https://gist.github.com/KenanSulayman/f7e55a28df614c520576) (CS & JS) I just build for you as an example. **Tip!** If you're unable to remove the node after playing with the script, simply commit a removal: ``` $ telnet 127.0.0.1 28777 -node|appmonitor ```
Author
Owner

@berrywira commented on GitHub (Jul 29, 2015):

I don't know this problem has solved or not yet.
But, when you want add new node. on configuration harvester :

Parameter server: [
host : IP_Server,
port : 28777,
}

and configuration log_server.conf

exports.config = {
host: 'IP_Server'
port: 28777
}

Now, I running log.io with no problem.

<!-- gh-comment-id:125910965 --> @berrywira commented on GitHub (Jul 29, 2015): I don't know this problem has solved or not yet. But, when you want add new node. on configuration harvester : Parameter server: [ host : IP_Server, port : 28777, } and configuration log_server.conf exports.config = { host: 'IP_Server' port: 28777 } Now, I running log.io with no problem.
Author
Owner

@msmathers commented on GitHub (Jan 12, 2020):

v0.4.3 has a new configuration scheme which allows a single file input (formerly harvester) process to define multiple stream/source pairs.

<!-- gh-comment-id:573446148 --> @msmathers commented on GitHub (Jan 12, 2020): v0.4.3 has a new configuration scheme which allows a single file input (formerly harvester) process to define multiple stream/source pairs.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/log.io-NarrativeScience-old#117
No description provided.