Dashboard GitHub

Frequently Asked Questions

Common questions and answers about LogFlux zero-knowledge logging platform

General Questions

What is LogFlux?

LogFlux is a zero-knowledge logging platform that provides client-side encryption, ensuring your log data remains private and secure. We never see your actual log content - it’s encrypted before leaving your infrastructure.

How does zero-knowledge logging work?

Your logs are encrypted with AES-256-GCM using keys that only you control. LogFlux stores and processes encrypted data without ever having access to your encryption keys or plaintext log content.

What types of logs can LogFlux handle?

LogFlux supports all types of log data:

  • Application logs (JSON, plaintext, structured)
  • System logs (journald, Windows Event Log, macOS)
  • Container logs (Docker, Kubernetes)
  • Web server logs (Nginx, Apache, HAProxy)
  • Database logs (PostgreSQL, MySQL, MongoDB)
  • Cloud platform logs (AWS CloudWatch, Azure Monitor, GCP Logging)

Is LogFlux compliant with regulations?

Yes, LogFlux is designed for regulatory compliance:

  • GDPR - Zero-knowledge architecture ensures data privacy
  • HIPAA - Client-side encryption meets healthcare requirements
  • SOX - Immutable logging and audit trails
  • PCI DSS - Secure handling of sensitive log data

Getting Started

How do I start using LogFlux?

  1. Sign up for a LogFlux account
  2. Install the LogFlux Agent on your systems
  3. Configure encryption keys
  4. Start sending logs using our SDKs or integrations
  5. Use LogFlux Inspector to query and analyze logs

What SDKs are available?

LogFlux provides SDKs for popular programming languages:

Do I need to change my existing logging code?

Minimal changes are required. Our SDKs integrate with popular logging libraries:

  • Go: logrus, zap, zerolog, slog
  • JavaScript: Winston, Bunyan, Pino, Debug
  • Python: standard logging, structlog
  • Java: SLF4J, Log4j2, JUL

Installation & Configuration

What are the system requirements?

For complete system requirements, see System Requirements.

Quick Summary:

  • Agent: 512MB RAM, 1GB storage, Linux/macOS/Windows
  • SDKs: Go 1.19+, Node.js 16+, Python 3.8+, Java 11+
  • Clients: 2-4GB RAM, modern OS versions

How do I configure encryption?

Encryption keys are configured in your LogFlux Agent:

1
2
3

# /etc/logflux-agent/agent.yaml
api_key: your-actual-api-key-here
node: production-server-01

Generate a secure RSA 4096 keypair with:

1
2

openssl genrsa -out private_key.pem 4096
openssl rsa -in private_key.pem -pubout -out public_key.pem

How do I handle log rotation?

LogFlux automatically detects log rotation:

  • File-based: Inode tracking handles rotation
  • Container logs: Automatic container lifecycle management
  • System logs: Native integration with journald, Event Log

Security & Privacy

Who can see my log data?

Nobody except you. LogFlux uses zero-knowledge architecture:

  • Logs are encrypted before leaving your infrastructure
  • LogFlux never has access to your encryption keys
  • Our team cannot decrypt or read your log content
  • Only you can decrypt and view your logs

What encryption does LogFlux use?

  • Algorithm: AES-256-GCM (industry standard)
  • Key management: Client-controlled keys
  • Transport: TLS 1.3 for data in transit
  • Storage: Encrypted at rest with your keys

How are encryption keys managed?

You control all encryption keys:

  • Generation: You generate your own keys
  • Storage: Keys remain in your infrastructure
  • Rotation: You control key rotation schedule
  • Access: LogFlux never sees your keys

What happens if I lose my encryption key?

If you lose your encryption key, your log data becomes unrecoverable. This is by design for zero-knowledge security. We recommend:

  • Store keys in secure key management systems
  • Implement key backup procedures
  • Use key rotation best practices
  • Document key recovery processes

Performance & Scaling

How much throughput can LogFlux handle?

LogFlux scales to handle high-volume logging:

  • Single agent: 10,000+ logs per second
  • Horizontal scaling: Multiple agents per application
  • Batch processing: Efficient batching reduces overhead
  • Local queuing: Handles temporary network issues

Does LogFlux impact application performance?

LogFlux is designed for minimal performance impact:

  • Async processing: Non-blocking log operations
  • Local queuing: Reduces network dependencies
  • Efficient SDKs: Low CPU and memory overhead
  • Configurable batching: Optimize for your workload

How do I optimize LogFlux for my workload?

Performance tuning options:

  • Batch size: Increase for higher throughput
  • Queue depth: Adjust for memory vs reliability
  • Compression: Enable for high-volume scenarios
  • Filtering: Reduce noise at the source

Integrations

What platforms does LogFlux integrate with?

LogFlux integrates with popular platforms:

  • Cloud: AWS CloudWatch, Azure Monitor, GCP Logging
  • Containers: Docker, Kubernetes, OpenShift
  • Systems: journald, Windows Event Log, macOS Unified Logging
  • Web servers: Nginx, Apache, HAProxy, IIS
  • Databases: PostgreSQL, MySQL, MongoDB, Redis
  • Observability: OpenTelemetry, Prometheus, Zipkin

Can I use LogFlux with existing logging infrastructure?

Yes, LogFlux complements existing infrastructure:

  • Migration: Gradual migration from existing systems
  • Dual logging: Run alongside current solutions
  • Export capabilities: Export to other systems if needed
  • Standard formats: JSON, syslog, and custom formats

How do I migrate from my current logging solution?

Migration strategies:

  1. Parallel deployment: Run LogFlux alongside existing systems
  2. Service-by-service: Migrate applications gradually
  3. Data export: Export existing data to LogFlux
  4. Configuration templates: Convert existing configurations

Troubleshooting

My logs aren’t appearing in LogFlux

Check these common issues:

  1. Agent status: systemctl status logflux-agent
  2. Network connectivity: Test connection to LogFlux endpoints
  3. API keys: Verify API key is correct and active
  4. Encryption keys: Ensure encryption key is properly configured
  5. Log permissions: Check file permissions for log sources

LogFlux Agent is using too much memory

Memory optimization steps:

  1. Reduce queue size: Lower queue settings in agent configuration
  2. Increase batch frequency: Send batches more frequently
  3. Enable compression: Reduce memory usage for large logs
  4. Filter at source: Reduce log volume with filters

How do I debug connection issues?

Debugging steps:

  1. Check logs: journalctl -u logflux-agent -f
  2. Network test: curl -I https://api.logflux.io/health
  3. DNS resolution: Verify DNS settings
  4. Firewall rules: Ensure outbound HTTPS access
  5. Proxy settings: Configure proxy if required

Can I test LogFlux locally?

Yes, LogFlux supports local testing:

  • Development mode: Local file output
  • Mock endpoints: Test without sending to LogFlux
  • LogFlux Inspector: Local log analysis
  • Configuration validation: Verify setup before deployment

Billing & Pricing

How is LogFlux priced?

LogFlux pricing is based on monthly log ingestion volume and retention period. We offer multiple plans to fit different needs, from individual developers to enterprise organizations.

For current pricing, plan features, and detailed comparisons, visit logflux.io/pricing.

Is there a free tier?

Yes, LogFlux offers a generous free tier to get you started. Visit logflux.io/pricing for current free tier limits and features.

How do I monitor my usage?

Monitor usage in the LogFlux dashboard:

  • Real-time metrics: Current month usage
  • Historical data: Previous months
  • Alerts: Usage threshold notifications
  • Projections: Estimated monthly usage

Still Need Help?

If you can’t find the answer to your question here, we’re ready to help:

Email Support: support@logflux.io

Before contacting support, please:

  1. Check this FAQ and our documentation
  2. Search using Cmd/Ctrl + K
  3. Include relevant error messages and configuration details