go-cloud
Grafana
Our great sponsors
go-cloud | Grafana | |
---|---|---|
21 | 379 | |
9,388 | 60,395 | |
0.6% | 1.7% | |
8.5 | 10.0 | |
3 days ago | 2 days ago | |
Go | TypeScript | |
Apache License 2.0 | GNU Affero General Public License v3.0 |
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.
go-cloud
-
Mitchell reflects as he departs HashiCorp
Even when going multi-cloud you can employ different strategies. Vault is definitely one of them, but you can also use federation to exchange one cloud's credentials for another's, giving you the ability to centralize secrets in one of them. You can use a layer of abstraction like GoCloud [0]. You can also build for each cloud separately and decide either not to centralize secrets at all, or build some trivial bespoke tooling to synchronize some of them. I'm not endorsing any of the options, just pointing out that Vault isn't the only one.
https://github.com/google/go-cloud
-
Deno Queues
> If Google started adding Google Cloud specific primitives natively to Go would you call that forward thinking as well?
Go actually ships with a quite forward thinking SQL interface. It's an abstract interface over a DB, and you just import the "driver" that powers it. The driver conforms to a standard interface, so all of them behave roughly the same.
I think this is what everyone wants from Deno/etc - why can't there also be a KV interface that's universal, or a Queue interface that's universal?
People attempted this w/ go [1], where it attempts to use the same nice experience of the SQL logic, but it never seemed to gain traction.
https://gocloud.dev
-
Event Observer Pattern in Go
github.com/google/go-cloud/pubsub package provides a set of interfaces and tools to work with publish/subscribe messaging. This package allows easy communication between independent components by decoupling the sender and the receiver.
-
Google’s Wire: Automated Dependency Injection in Go
I'm guessing this is a reasonable example of what they're using it for? server.go
-
What's the status of pulumi-cloud https://github.com/pulumi/pulumi-cloud?
https://github.com/google/go-cloud probably out of context, but not IaC but agnostic backend development with Go across multiple clouds
-
Is there a zero-boilerplate zero-configuration cloud serverless framework for Go?
The plan is to have a process for generating AWS CDK targeting Lambda (pluggable providers, but start with AWS CDK, because it's what I use), and to use the Google Cloud Development Kit (also called CDK, but not the same) https://github.com/google/go-cloud to abstract the services.
-
Go Cloud Development Kit
In this post, I will talk about an exciting project maintained by the team that develops the Go language: the Go Cloud Development Kit, also known as the Go CDK.
- GitHub - google/go-cloud: The Go Cloud Development Kit (Go CDK): A library and tools for open cloud development in Go.
-
imagor v1.3 - a high-level Go image processing library using libvips
The API of gocloud.dev, is stable. We are at ariga.io, already use gocloud.dev for internal service, and even in the public for easy adopt multi-clouds provider: https://github.com/ariga/atlas/commit/ef0b0eae65a61375482497ceb9ed9790a469b56e
-
Should we switch to Rust?
On Go, which has a community focused on the cloud, there is even GoCloud, a library with a single, common, and high-level API that allows an application to support any of those clouds and even on-premise alternatives for those services. All can be configurable at deploy time by the infrastructure team.
Grafana
-
Docker Log Observability: Analyzing Container Logs in HashiCorp Nomad with Vector, Loki, and Grafana
Monitoring application logs is a crucial aspect of the software development and deployment lifecycle. In this post, we'll delve into the process of observing logs generated by Docker container applications operating within HashiCorp Nomad. With the aid of Grafana, Vector, and Loki, we'll explore effective strategies for log analysis and visualization, enhancing visibility and troubleshooting capabilities within your Nomad environment.
-
Golang: out-of-box backpressure handling with gRPC, proven by a Grafana dashboard
To help us visualize these scenarios, we'll build a Grafana Dashboard so we can follow along.
-
Monitoring, Observability, and Telemetry Explained
Visualization and Analysis: Choose a tool with intuitive and customizable dashboards, charts, and visualizations. A question to ask is, "Are the visualization features of this tool user-friendly and adaptable to our team's specific needs?" Tools like Grafana and Kibana provide powerful visualization capabilities.
-
4 facets of API monitoring you should implement
Prometheus: Open-source monitoring system. Often used together with Grafana.
- Grafana: Open and composable observability and data visualization platform
-
The Mechanics of Silicon Valley Pump and Dump Schemes
Grafana
-
Reverse engineering the Grafana API to get the data from a dashboard
Yes I'm aware that Grafana is open source but the method I used to find the API endpoints is far quicker than digging through hundreds of files in a codebase I'm not familiar with.
-
Building an Observability Stack with Docker
So, you will add one last container to allow us to visualize this data: Grafana, an open-source analytics and visualization platform that allows us to see traces and metrics simply. You can set Grafana to read data from both Tempo and Prometheus by setting them as datastores with the following grafana.datasource.yaml config file:
-
How to collect metrics from node.js applications in PM2 with exporting to Prometheus
In example above, we use 2 additional parameters: code (HTTP response code) and page (page identifier), which provide detailed statistics. For example, you can build such graphs in Grafana:
-
Root Cause Chronicles: Quivering Queue
Robin switched to the Grafana dashboard tab, and sure enough, the 5xx volume on web service was rising. It had not hit the critical alert thresholds yet, but customers had already started noticing.
What are some alternatives?
cloudpods - A cloud-native open-source unified multi-cloud and hybrid-cloud platform. 开源、云原生的多云管理及混合云融合平台
Thingsboard - Open-source IoT Platform - Device management, data collection, processing and visualization.
cloudgamestream - A Powershell one-click solution to enable NVIDIA GeForce Experience GameStream on a cloud machine with a GRID supporting GPU.
Apache Superset - Apache Superset is a Data Visualization and Data Exploration Platform [Moved to: https://github.com/apache/superset]
hackingthe.cloud - An encyclopedia for offensive and defensive security knowledge in cloud native technologies.
Heimdall - An Application dashboard and launcher
ungoogled-chromium-portable - 🚀 Ungoogled Chromium portable for Windows
Wazuh - Wazuh - The Open Source Security Platform. Unified XDR and SIEM protection for endpoints and cloud workloads.
aws-sdk-go - AWS SDK for the Go programming language.
Thingspeak - ThingSpeak is an open source “Internet of Things” application and API to store and retrieve data from things using HTTP over the Internet or via a Local Area Network. With ThingSpeak, you can create sensor logging applications, location tracking applications, and a social network of things with status updates.
fss3 - FSS3 is an S3 filesystem abstraction layer for Golang
uptime-kuma - A fancy self-hosted monitoring tool