logger-node | A nodejs logger client for LogDNA

 by   logdna JavaScript Version: v2.6.4 License: MIT

kandi X-RAY | logger-node Summary

kandi X-RAY | logger-node Summary

logger-node is a JavaScript library. logger-node has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

Previous versions of this client are still supported, but if you are upgrading to this version, please see our migration document for the differences between this version and prior versions.
Support
    Quality
      Security
        License
          Reuse

            kandi-support Support

              logger-node has a low active ecosystem.
              It has 27 star(s) with 10 fork(s). There are 22 watchers for this library.
              OutlinedDot
              It had no major release in the last 12 months.
              There are 4 open issues and 21 have been closed. On average issues are closed in 46 days. There are 3 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of logger-node is v2.6.4

            kandi-Quality Quality

              logger-node has 0 bugs and 0 code smells.

            kandi-Security Security

              logger-node has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              logger-node code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              logger-node is licensed under the MIT License. This license is Permissive.
              Permissive licenses have the least restrictions, and you can use them in most projects.

            kandi-Reuse Reuse

              logger-node releases are available to install and integrate.
              Installation instructions, examples and code snippets are available.

            Top functions reviewed by kandi - BETA

            kandi has reviewed logger-node and discovered the below as its top functions. This is intended to give you an instant insight into logger-node implemented functionality, and help decide if they suit your requirements.
            • Creates an instance of Convenience methods .
            • Create logging instance .
            • create a logger
            • Generate a random number between min and max
            Get all kandi verified functions for this library.

            logger-node Key Features

            No Key Features are available at this moment for logger-node.

            logger-node Examples and Code Snippets

            No Code Snippets are available at this moment for logger-node.

            Community Discussions

            QUESTION

            Fluentd Kubernetes Nodejs : Error: connect ECONNREFUSED 127.0.0.1:24224
            Asked 2020-Sep-21 at 06:13

            EDIT : I harcoded the fluentd service IP directly in my express app and its working.. how to get it work without harcoding ip?

            I have a couple of pods (nodejs + express server) running on a Kubernetes cluster.

            I'd like send logs from my nodejs pods to a Fluentd DeamonSet.

            But I'm getting this error :

            Fluentd error Error: connect ECONNREFUSED 127.0.0.1:24224

            I'm using https://github.com/fluent/fluent-logger-node and my configuration is pretty simple:

            ...

            ANSWER

            Answered 2020-Sep-21 at 06:13

            Focusing on below parts of the question:

            I'd like send logs from my nodejs pods to a Fluentd DeamonSet.

            EDIT : I harcoded the fluentd service IP directly in my express app and its working.. how to get it work without harcoding ip?

            It looks like the communication between pods and the fluentd service is correct (hardcoding the IP works). The issue here is the way they can communicate with each other.

            You can communicate with service fluentd by its name. For example (from the inside of a pod):

            • curl fluentd:24224

            You can communicate with services by its name (like fluentd) only in the same namespace. If a service is in another namespace you would need to use it's full DNS name. It's template and example is following:

            • template: service-name.namespace.svc.cluster.local
            • example: fluentd.kube-system.svc.cluster.local

            You can also use service of type ExternalName to map the full DNS name of your service to a shorter version like below:

            Assuming that (example):

            • You have created a nginx-namespace namespace:
              • $ kubectl create namespace nginx-namespace
            • You have an nginx Deployment inside the nginx-namespace and a service associated with it:
              • $ kubectl create deployment nginx --image=nginx --namespace=nginx-namespace
              • $ kubectl expose deployment nginx --port=80 --type=ClusterIP --namespace=nginx-namespace
            • You want to communicate with nginx Deployment from another namespace (i.e. default)

            You have an option to communicate with above pod:

            • By the IP address of a Pod
              • 10.98.132.201
            • By a (full) DNS service name
              • nginx.nginx-namespace.svc.cluster.local
            • By an ExternalName type of service that points to a a (full) DNS service name
              • nginx-service

            The example of ExternalName type of service:

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

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

            Vulnerabilities

            No vulnerabilities reported

            Install logger-node

            Operation requires a LogDNA Ingestion Key. Without it, the client will not be able to post logs to the cloud. Please contact our support if you have questions about this setup process!.

            Support

            The logger supports proxying for situations such as corporate proxies that require traffic to be passed through them before reaching the outside world. For such implementations, use the proxy instantiation option to set the full URL of the proxy. It supports both http and https proxy URLs. Under the hood, the logger uses the https-proxy-agent package for this.
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
            CLONE
          • HTTPS

            https://github.com/logdna/logger-node.git

          • CLI

            gh repo clone logdna/logger-node

          • sshUrl

            git@github.com:logdna/logger-node.git

          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link

            Consider Popular JavaScript Libraries

            freeCodeCamp

            by freeCodeCamp

            vue

            by vuejs

            react

            by facebook

            bootstrap

            by twbs

            Try Top Libraries by logdna

            logdna-agent

            by logdnaJavaScript

            nodejs

            by logdnaJavaScript

            logdna-agent-v2

            by logdnaRust

            python

            by logdnaPython

            tail-file-node

            by logdnaShell