Fluentd
go-sqlmock
Our great sponsors
Fluentd | go-sqlmock | |
---|---|---|
25 | 19 | |
12,544 | 5,827 | |
0.8% | 1.5% | |
8.1 | 5.4 | |
24 days ago | 23 days ago | |
Ruby | Go | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Fluentd
-
Embracing Kubernetes: The Future of Containerized Applications
Get Started with Fluentd
-
Kubernetes Architecture
Currently, there is no cluster-wide logging. Fluentd can be used to have a unified logging layer for the cluster.
- Fluentd – open-source data collection and unified logging layer
-
making job execution log searchable
Fluentd hasn't been touched for 8 years? Looking at the repo it looks like it's alive and well. https://github.com/fluent/fluentd
-
Top 11 Splunk Alternatives that you may consider in 2023
Fluentd is an open-source log management and data collection tool. Just like Logstash, Fluentd uses a pipeline-based architecture. This allows it to collect data from various sources and network traffic and forward it to various destinations.
-
7 Open-Source Log Management Tools that you may consider in 2023
Fluentd is a powerful log management tool that offers organizations the flexibility and scalability required to handle large volumes of log data from a variety of sources and transport it to various destinations. Utilizing a flexible and modular architecture, Fluentd allows users to easily add new input and output plugins to integrate with a wide range of systems and applications. It supports a wide range of data sources and destinations, including databases, message queues, and data stores.
-
Substation: Data Pipeline and Transformation Toolkit Written in Go
Substation is an affordable alternative to products like Cribl (~10x cost savings) and is easier to manage than similar open-source projects such as Logstash and fluentd. It's been used in production by the security team at Brex for 2+ years and is ready for any scale, even beyond 100,000 events per second!
-
Simple way to centralize my server logs?
There are probably too many to chose from. Logstash, Promtail, Vector, Filebeat, FluentD, Logagent and probably many more
-
The Everything Guide to Data Collection in DevSecOps
To alleviate some of the pain, it’s a good idea to use industry standards and tooling like OpenTelemetry (https://opentelemetry.io). For data collection specific to logs, open-source tools like LogStash and Fluentd are also popular.
-
Top 20 Observability Tools Every Startup Should Know About in 2022
Created and maintained by the creators of fluentd, fluentbit is a lightweight, fast, and scalable logging and metrics processor and forwarder. Built specifically for the cloud and containerized environments, it allows users to collect data from any source, enrich it with filters and forward it to the tool of their choice.
go-sqlmock
- How do you unit-test code that reaches out to the db, without introducing interfaces everywhere?
-
Creating an API using Go and sqlc
For that, I used the lib go-sqlmock. So, for example, the following snippet is part of the person/service_test.go file:
-
Using SQLC in project how do I mock database Calls with it for unit testing?
It's not the right call IMO to skip mocking the database connection to achieve 100% test coverage. How your app will behave in failure scenarios that are impossible to imitate during integration tests is part of the software contract. If your choice is to panic, or return an error, document that by testing that behavior. If another dev, or future you inadvertently breaks the contract, the test suite will fail. That's what you want. For unit tests against your database you should be using either go-sqlmock if testing against database/sql or pgxmock if testing against pgx. That being said, the points raised elsewhere in this thread regarding unit tests potentially hiding edge cases in terms of how an actual database will interact with your application that are not reflective of your understanding when writing mocks are 100% valid. You should do both. Unit test your app and write integration tests as well. On my team, we run integration tests using docker-compose.
- What is the coolest Go open source projects you have seen?
- How to mock database calls
-
Can you set expectations for SQL transaction using Testify?
I use Sqlmock for that purpose
- Mocking database queries - ask for opinion
- SQL mock driver for Golang to test database interactions
- Can't get a specifc SQL query with pgx to work
-
[HELP] how to test this piece of code?
There is a good lib for db tests https://github.com/DATA-DOG/go-sqlmock
What are some alternatives?
vector - A high-performance observability data pipeline.
gomock - GoMock is a mocking framework for the Go programming language.
zipkin - Zipkin is a distributed tracing system
go-txdb - Immutable transaction isolated sql driver for golang
Flume - Mirror of Apache Flume
mockery - A mock code autogenerator for Go
Lograge - An attempt to tame Rails' default policy to log everything.
gock - HTTP traffic mocking and testing made easy in Go ༼ʘ̚ل͜ʘ̚༽
Semantic Logger - Semantic Logger is a feature rich logging framework, and replacement for existing Ruby & Rails loggers.
minimock - Powerful mock generation tool for Go programming language
heka - DEPRECATED: Data collection and processing made easy.
gotests - Automatically generate Go test boilerplate from your source code.