Logz.io Shipper Configuration Error — Quick Fix

In this tutorial, you'll learn about Logz.io Shipper Configuration Error. We cover key concepts, practical examples, and best practices.

The Problem

A Logz.io shipper (Logstash, Fluentd, Filebeat) cannot send logs to Logz.io. The shipper may fail to authenticate, connect to the wrong endpoint, or encounter TLS errors. Logs may buffer locally but never reach Logz.io.

Error example:

Logstash: Failed to connect to listener.logz.io:5000: Connection refused
Filebeat: Error publishing events: 401 unauthorized
Plugin: Output failed: SSL certificate verify failed

The Fix

Step 1: Verify the account token

WRONG — using the API token instead of the shipping token:

# Logz.io has separate tokens for shipping and API access

RIGHT — use the correct shipping token:

# Find the shipping token in Logz.io:
# Settings -> General -> Account token

# Test with curl:
curl -X POST https://listener.logz.io:8071?token=YOUR_SHIPPING_TOKEN \
  -d '{"message": "test", "type": "test"}'

Step 2: Check the listener URL

WRONG — using the wrong regional endpoint:

# Logz.io has different listener URLs for different regions

RIGHT — use the correct region URL:

# US East: listener.logz.io
# EU West: listener-eu.logz.io
# EU Central: listener-ca.logz.io

# Example for US
output {
  logz.io {
    endpoint_url => "https://listener.logz.io:8071"
    token => "YOUR_TOKEN"
  }
}

Use DodaTech's Shipper Configuration Validator to test endpoint connectivity, token validity, and TLS configurations for Logz.io shippers.

Prevention Tips

• Use the correct regional listener URL for your account
• Store the shipping token in a secrets manager, not in plain text configs
• Configure TLS verification and trust the Logz.io certificate
• Monitor shipper output queue depth and error rates
• Use DodaTech's Log Shipping Fleet Manager for centralized shipper configuration

Common Mistakes with shipper config

1. Overlapping type class instances that cause GHC to reject the program with ambiguous dispatch errors
2. Non-exhaustive pattern matches that compile with warnings then crash at runtime
3. Misunderstanding that String is [Char] with poor performance for large text operations

These mistakes appear frequently in real-world LOGZIO code. DodaTech's contributors have identified these patterns through analysis of open-source projects and production systems.

Practice Exercise

Write a pure function that safely divides two integers using Maybe, then test it with edge cases like division by zero and negative numbers.

This exercise reinforces the concepts covered in this guide. Try implementing it before checking online solutions.

FAQ

Related: DodaTech's Log Shipping Architecture Guide provides reference configurations for Filebeat, Logstash, and Fluentd shippers to Logz.io.