Logrus Alternatives
Similar projects and alternatives to logrus
-
-
-
SonarLint
Deliver Cleaner and Safer Code - Right in Your IDE of Choice!. SonarLint is a free and open source IDE extension that identifies and catches bugs and vulnerabilities as you code, directly in the IDE. Install from your favorite IDE marketplace today.
-
-
-
Gin
Gin is a HTTP web framework written in Go (Golang). It features a Martini-like API with much better performance -- up to 40 times faster. If you need smashing performance, get yourself some Gin.
-
-
seelog
Seelog is a native Go logging library that provides flexible asynchronous dispatching, filtering, and formatting.
-
Scout APM
Less time debugging, more time building. Scout APM allows you to find and fix performance issues with no hassle. Now with error monitoring and external services monitoring, Scout is a developer's best friend when it comes to application development.
-
Testify
A toolkit with common assertions and mocks that plays nicely with the standard library
-
-
-
-
feedback
Public feedback discussions for: GitHub for Mobile, GitHub Discussions, GitHub Codespaces, GitHub Sponsors, GitHub Issues and more!
-
-
-
-
-
godotenv
A Go port of Ruby's dotenv library (Loads environment variables from `.env`.)
-
-
-
logrus reviews and mentions
-
GoLand 2022.1 EAP starts with: new сode completion options for generics, fixes for more than 50 generics-related issues, string formatting support for testify/assert functions, and more! Join the EAP!
Does switching go.mod version to 1.18 and GOROOT under Preferences/Settings | Go | GOROOT help? If not, can you reproduce it on some open-source project, e.g. logrus?
- Go questions from an Express TS dev
-
Advice for writing enterprise-level API in Go?
I use zap for logging. With some planning, you can easily switch between logging to JSON or Plaintext (the former is faster but less readable). Though, that comes with a learning curve - you'll have to spend some time reading the docs before you can actually start using zap in production. On the other hand, logrus is pretty simple to use, but relatively quite slow (this might not matter for personal projects, but probably will in production). And of course, there's the standard package as well! Take your pick ;)
-
GitHub Broken Download URLs
I still remember the night when logrus's author decided to rename his Github account and broke our production build (https://github.com/sirupsen/logrus/pull/384). Since then, I always vendor third party dependencies.
-
zlog: Secure logger in Go to prevent output of sensitive/secret values
Some famous existing libraries that support structured logging are zap, logrus, zerolog, but none of them implement such a function to hide the secret value.
-
How do you build/test a library
Doesn't even have to be in an examples folder. See something like the Logrus package, which has example_*.go files that simply import the package.
-
Lumber: A simple and pretty logger for Golang
There is no better way than looking at your older brothers and learning from them: stdlib log, glog, logrus, zerolog, log15 (eth fork)...
- XKCD 2347
-
What are your favorite packages to use?
https://github.com/sirupsen/logrus is a great logger library for go
logrus and, more recently, zerolog for logging
logrus for logging. It's slower than zerolog but I've been used it for so long, so if performance doesn't really matter (e.g. simple CLI) I still prefer to use it.
- My opinionated way to write and test a go http server
-
Backstage Software Templates
apiVersion: backstage.io/v1alpha1 kind: Template metadata: name: golang-starter title: Golang Microservice description: Create a Golang repo with this template built by members of the Go community tags: - experimental - go spec: owner: [email protected] templater: cookiecutter type: service path: "." schema: required: - component_id - project_short_description - docker_image - docker_build_image - docker_build_image_version - use_logrus_logging - use_viper_config - use_ci - use_cobra_cmd properties: component_id: title: Name type: string description: Unique name of the component project_short_description: title: Description type: string description: Description of the component docker_image: title: Docker Image type: string description: The docker base image to use when running the service default: alpine-base-image:latest docker_build_image: title: Docker Build Image type: string description: The docker base image to use when building the service default: golang docker_build_image_version: title: Docker Build Image Version description: The image version to use when building the service type: string enum: - alpine default: alpine use_logrus_logging: title: Enable Logrus Logging (https://github.com/sirupsen/logrus) type: string enum: - "y" - "n" default: "y" use_viper_config: title: Enable Viper Config (https://github.com/spf13/viper) type: string enum: - "y" - "n" default: "y" use_cobra_cmd: title: Enable Cobra CLI Tools (https://github.com/spf13/cobra) type: string enum: - "y" - "n" default: "y" use_ci: title: Add CI description: Add a CI config to the repo, Gitub Actions, Circle or Travis are the only supported right now type: string enum: - github - travis - circle - none default: github
-
logrus.errorf() causes panics?
Based on this snippet, it might be worth checking what logrus.PanicLevel is set to, inside your unit test.
-
Mocking the filesystem in Go using Afero
For logging use https://github.com/Sirupsen/logrus
Stats
sirupsen/logrus is an open source project licensed under MIT License which is an OSI approved license.
Popular Comparisons
Are you hiring? Post a new remote job listing for free.