winston-logstash | A Logstash TCP transport for winston | TCP library

by jaakkos JavaScript Version: 1.2.1 License: MIT

X-Ray Key Features Code Snippets Community Discussions(4)Vulnerabilities Install Support

kandi X-RAY | winston-logstash Summary

winston-logstash is a JavaScript library typically used in Networking, TCP applications. winston-logstash has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can install using 'npm i winston-logstash-cubyn' or download it from GitHub, npm.

A Logstash TCP transport for winston.

Support

Quality

Security

License

Reuse

Support

winston-logstash has a low active ecosystem.

It has 107 star(s) with 64 fork(s). There are 6 watchers for this library.

It had no major release in the last 12 months.

There are 12 open issues and 15 have been closed. On average issues are closed in 143 days. There are 4 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of winston-logstash is 1.2.1

Quality

winston-logstash has 0 bugs and 0 code smells.

Security

winston-logstash has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

winston-logstash code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

winston-logstash is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

winston-logstash releases are available to install and integrate.

Deployable package is available in npm.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of winston-logstash

Get all kandi verified functions for this library.

winston-logstash Key Features

No Key Features are available at this moment for winston-logstash.

winston-logstash Examples and Code Snippets

No Code Snippets are available at this moment for winston-logstash.

Community Discussions

Trending Discussions on winston-logstash

Winston 3.x support for logstash missing?

Extend Typescript definition for winston transport

Wait node.js until Logstash is ready using containers

Catch Error: getaddrinfo ENOTFOUND using winston

QUESTION

Winston 3.x support for logstash missing?

Asked 2019-Jul-07 at 03:36

I'm trying to integrate a dummy nodejs app to an ELK stack. I'm using winston as logging library since it's my preferred choice when I develop on a JS stack. I've tried to write this sinppet of code, using winston 3.x version

...

ANSWER

Answered 2019-Jul-07 at 03:36

There are two concepts at play here, in Winston 3.

A format just does some transformations on the object you're logging.

A transport is a "pipe" that defines a way of taking your log object and sending it somewhere.

In the Winston 2 world, these two concepts were often combined; for instance, the winston-logstash module was a transport but also implicitly formatted objects in a way that's acceptable for Logstash. There's nothing in Winston 2 or 3 that restricts what is possible in terms of transports or formats, so Winston 3 is not "missing support" for Logstash.

However, Winston 3 did make some changes to the transport API (and also separated out formats, as mentioned - though a transport can still do formatting). That is why you see warnings about winston-logstash being a legacy transport: the authors of winston-logstash have not updated their module to use the new Winston 3 style interfaces. There is a thread on the Winston project with some helpful info for transport authors on updating their transports.

So, you could bug the authors to upgrade their transport, upgrade/wrap it yourself (see linked thread), or - I think the legacy warning is just a warning, so it should still work ok with Winston 3.

In fact, I think there is already a PR open to make winston-logstash 3.x compatible, though the repo maintainer seems to have ghosted; I suppose you could try using the PR branch/fork. You might also try winston-logstash-transport which appears to achieve the same goals but appears to be designed for 3.x. Feel free to comment on what works best.

Source https://stackoverflow.com/questions/56815815

QUESTION

Extend Typescript definition for winston transport

Asked 2019-May-03 at 16:49

I added the winston-logstash package, which is a winston transport for logstash. Unfortunately it comes without typescript definitions and I am struggling with adding my own typings to it.

What I have tried:

My winston.ts:

...

ANSWER

Answered 2018-Feb-21 at 20:51

When you augment the winston Transports interface, you need to surround it with module "winston" { ... }

This seemed to work:

Source https://stackoverflow.com/questions/48886527

QUESTION

Wait node.js until Logstash is ready using containers

Asked 2018-May-25 at 05:08

I have the following setup in docker-compose.yml:

...

ANSWER

Answered 2018-May-25 at 05:08

Docker compose does not wait until a container is ready, it will only wait until it's running.

depends_on will only ensure that logstash launches before your node container, but again, this doesn't mean it will wait until it is ready.

You can either handle the checks yourself on node, or use a wrapper script. In docker-compose documentation, they recommend, wait-for-it or dockerize

You can read more on this in here

Custom wrapper

Your node container command can change from node index.js (or whatever you have), to bash wait-for-logtash.sh:

Source https://stackoverflow.com/questions/50520698

QUESTION

Catch Error: getaddrinfo ENOTFOUND using winston

Asked 2017-Sep-22 at 22:06

I've been using winston to push logs to logmatic for almost a year, and this week I had to turn it off because I get random connection errors which crash the production server. I turned it off as a temporal fix, but I would prefer something like a try/catch, which I tried but didn't work.

Here's my current code:

...

ANSWER

Answered 2017-Sep-22 at 22:06

You could do

Source https://stackoverflow.com/questions/46372868

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install winston-logstash

You can install using 'npm i winston-logstash-cubyn' or download it from GitHub, npm.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: