Listing Links

stereowrench.com x

Tags

see all

Observability for Phoenix using the Grafana Stack in Dev | Stereowrench (stereowrench.com)

This article offers a comprehensive guide on setting up observability for Phoenix applications using the Grafana Stack (Loki, Mimir, and Tempo) in a development environment with Docker Compose. It covers the three pillars of observability (metrics, logs, and traces) and provides detailed instructions on configuring each component, including using PromEx for Prometheus-compatible metrics, OpenTelemetry for traces, and Promtail for log management. The article also emphasizes the importance of secure configurations and its extensibility to production environments.
Main Points
- Three Pillars of ObservabilityExploring the fundamental aspects of observability, the author emphasizes the necessity of metrics, logs, and traces for comprehensive application monitoring.
- Setting up the Grafana StackThe article provides a detailed guide on setting up the Grafana Stack using Docker Compose, including configurations and tips for Loki, Mimir, and Tempo.
- Configuring Prometheus-compatible MetricsInsights on configuring metrics for a Phoenix application using the OpenTelemetry Collector and PromEx, highlighting a Prometheus-compatible setup without using Prometheus itself.
- Implementing Trace Data CollectionGuidance on implementing trace data collection within an Elixir project through OpenTelemetry and Tempo, covering setup and configuration steps.
- Configuring Log ManagementInstructions on configuring log rotation and using Promtail to ship logs to Grafana Loki, simplifying the management of application logs.
12

200

47

63
Null Results for Database Operations | Stereowrench (stereowrench.com)

The article discusses the exploration of High Availability (HA) and backup solutions for MySQL and PostgreSQL, including Point-In-Time Recovery (PITA) and full backups, highlighting the complexity of setting up such systems. The writer mentioned specific solutions like Patroni for PostgreSQL and WAL-G for both MySQL and PostgreSQL, as well as the Crunchy Data PostgreSQL Operator and MOCO operator for Kubernetes. The conclusion was a decision to move to Kubernetes for its support of HA, PITR, and regular full backups.
Main Points
- Exploring High Availability and Backup SolutionsFor PostgreSQL, the writer found Patroni for HA and was referred to WAL-G for both MySQL and PostgreSQL. They came across the Crunchy Data PostgreSQL Operator and the MOCO operator for Kubernetes, which supported HA, PITR, and regular full backups.
- Decision to Move to KubernetesThe writer will be moving to Kubernetes as it supports the required features such as HA, PITR, and regular full backups.
12

200

47

63