Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix some typos on elasticsearch and logstash #64

Merged
merged 2 commits into from
Jun 23, 2016

Conversation

dadoonet
Copy link
Contributor

And adds info about the default port for elasticsearch.

Note that I'd use 127.0.0.1 as an example instead of a real IP address.

I'd probably add a note for people using elasticsearch running on another machine (not 127.0.0.1) and would say that they need to set network.host in their elasticsearch.yml file on elasticsearch server.

And a link to: https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html#common-network-settings

And adds info about the default port for elasticsearch.

Note that I'd use 127.0.0.1 as an example instead of a real IP address.

I'd probably add a note for people using elasticsearch running on another machine (not 127.0.0.1) and would say that they need to set `network.host` in their `elasticsearch.yml` file on elasticsearch server.

And a link to: https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-network.html#common-network-settings
@dadoonet
Copy link
Contributor Author

Actually I looked at the documentation of pino-elasticsearch and the default server is 127.0.0.1 so I guess my first comment does not make sense...

Note that I'd use 127.0.0.1 as an example instead of a real IP address.

@mcollina
Copy link
Member

The documentation here needs to be correct, so do you think it's better to specify the configuration of Elasticsearch here for another ip address? Or change it to 127.0.0.1?

I imagine that whoever follows the doc here knows little about Elasticsearch, so maybe adding one more link is ok (also on pino-elasticsearch).

Thanks for reviewing!

@dadoonet
Copy link
Contributor Author

I would probably write something like:

It is extremely simple to use and setup

$ node yourapp.js | pino-elasticsearch

Assuming Elasticsearch is running on localhost.

If you wish to connect to an external elasticsearch instance (recommended for production):

$ node yourapp.js | pino-elasticsearch --host 192.168.1.42

Assuming Elasticsearch is running on 192.168.1.42.

WDYT?

@mcollina
Copy link
Member

👍 update the PR accordingly (maybe also pino-elasticsearch).

Thanks again for reviewing!

@mcollina mcollina merged commit 2cafdea into pinojs:master Jun 23, 2016
@mcollina
Copy link
Member

Thx!

@github-actions
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 10, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants