sirupsen/logrus
Structured, pluggable logging for Go.
Build with Backblaze B2
SDKs, agent skills, IDE extensions, and reference pipelines from Backblaze Labs. All open source.
Loading star history...
Where it stands
Rank, growth pace and release cadence relative to everything GStars tracks.
Ranks #225 of 2,845 repositories GStars tracks this week (top 8%).
3 releases in the last 90 days, the latest 47 days ago, with 245 contributors on GitHub.
Use Cases & Benefits
- Provides structured, pluggable logging for Go applications with API compatibility to the standard library logger.
- Enables detailed, structured log entries with customizable formatters and hooks for extensibility and integration with external systems.
- Use for adding structured logging with fields to Go services for improved observability and debugging.
- Use for integrating logging with external error tracking or metrics systems via hooks in production environments.
- Use for replacing the standard Go logger to gain flexible output formats like JSON or color-coded text in development.
Should you depend on it?
License terms, project hygiene and risks, from GitHub metadata and GStars' snapshots.
License
MIT
Permissive: commercial use, modification and redistribution are allowed with attribution.
Community files
- README: present
Watch-outs
No watch-outs from GStars' checks.
General guidance from repository metadata, not legal advice. How we score
From the README
Logrus is a structured logger for Go (golang), completely API compatible with the standard library logger.
Logrus is in maintenance-mode. We will not be introducing new features. It's simply too hard to do in a way that won't break many people's projects, which is the last thing you want from your Logging library (again...).
This does not mean Logrus is dead. Logrus will continue to be maintained for security, (backwards compatible) bug fixes, and performance (where we are limited by the interface).
I believe Logrus' biggest contribution is to have played a part in today's widespread use of structured logging in Golang. There doesn't seem to be a reason to do a major, breaking iteration into Logrus V2, since the fantastic Go community has built those independently. Many fantastic alternatives have sprung up. Logrus would look like those, had it been re-designed with what we know about structured logging in Go today. Check out, for example, Zerolog, Zap, and Apex.
Seeing weird case-sensitive problems? It's in the past been possible to import Logrus as both upper- and lower-case. Due to the Go package environment, this caused issues in the community and we needed a standard. Some environments experienced problems with the upper-case variant, so the lower-case was decided. Everything using
logruswill need to use the lower-case:github.com/sirupsen/logrus. Any package that isn't, should be changed.
Daily snapshots
Stars gained per day, and how forks and open issues moved, from GStars' daily snapshots
Forks
2.3K+15
Open issues
57+9
Compared with peers in Observability
Fastest-growing repositories GStars tracks in this cohort for the week of Oct 11, by 7-day star growth
| Repository | Stars | +7d | Health | Last release |
|---|---|---|---|---|
| Tracer-Cloud/opensre | 11.9K | +496 | 59 | 107 days ago |
| Effect-TS/effect | 17.4K | +94 | 75 | 1 day ago |
| mlflow/mlflow | 28.5K | +0 | 49 | 200 days ago |
| sirupsen/logrus | 25.8K | +0 | 75 | 47 days ago |
| uber-go/zap | 24.7K | +0 | 75 | 168 days ago |
| rs/zerolog | 12.5K | +0 | 40 | — |
| Category median | 17.4K | +0 | 59 | — |
Discover Repositories
Search across tracked repositories by name or description