cleanstart/logstash-exporter repository overview

Container Documentation for Logstash-Exporter

The Logstash Exporter container provides a Prometheus metrics exporter for Logstash monitoring and observability. It collects and exposes key performance metrics, pipeline statistics, and operational data from Logstash instances, enabling comprehensive monitoring and alerting capabilities in enterprise environments.

📌 Base Foundation: Security-hardened, minimal base OS designed for enterprise containerized environments from Cleanstart Registry.

Key Features Core capabilities and strengths of this container

• Prometheus metrics exposition for Logstash monitoring
• Real-time pipeline statistics and performance metrics
• Customizable metric collection and export intervals
• Low resource footprint and efficient operation

Common Use Cases Typical scenarios where this container excels

• Enterprise Logstash monitoring and alerting
• Performance metrics collection and analysis
• Operational health monitoring
• SLA compliance and reporting

Pull Latest Image Download the container image from the registry

docker pull cleanstart/logstash-exporter:latest

docker pull cleanstart/logstash-exporter:latest-dev

Basic Run Run the container with basic configuration

docker run -d -p 9198:9198 --name logstash-exporter cleanstart/logstash-exporter:latest

Production Deployment Deploy with production security settings

docker run -d --name logstash-exporter \
  -p 9198:9198 \
  --read-only \
  --security-opt=no-new-privileges \
  --user 1000:1000 \
  -e LOGSTASH_ENDPOINT=http://logstash:9600 \
  cleanstart/logstash-exporter:latest

Volume Mount Mount local directory for persistent data

docker run -d -p 9198:9198 \
  -v $(pwd)/config:/config \
  cleanstart/logstash-exporter:latest

Port Forwarding Run with custom port mappings

docker run -d -p 8080:9198 cleanstart/logstash-exporter:latest

Environment Variables Configuration options available through environment variables

Security Best Practices Recommended security configurations and practices

• Use specific image tags for production deployments
• Implement proper authentication for metrics endpoint
• Configure network security and access controls
• Regular security updates and patch management
• Monitor metrics endpoint access logs
• Use TLS for metrics endpoint communication

Kubernetes Security Context Recommended security context for Kubernetes deployments

securityContext:
  runAsNonRoot: true
  runAsUser: 1000
  runAsGroup: 1000
  readOnlyRootFilesystem: true
  allowPrivilegeEscalation: false
  capabilities:
    drop: ["ALL"]
  seccompProfile:
    type: RuntimeDefault

Multi-Platform Images

docker pull --platform linux/amd64 cleanstart/logstash-exporter:latest
docker pull --platform linux/arm64 cleanstart/logstash-exporter:latest

⁠Documentation Resources

Essential links and resources for further information

CleanStart Images: https://images.cleanstart.com/⁠

Community Images:
Docker Hub: https://hub.docker.com/u/cleanstart⁠
GitHub: https://github.com/cleanstart-containers⁠
AWS ECR Public Gallery: https://gallery.ecr.aws/cleanstart/⁠

Presence on Social Media:
Community: https://www.linkedin.com/groups/18324021/⁠
YouTube: https://www.youtube.com/@CleanStartOfficial⁠

Contribute to Container Use Cases: https://github.com/cleanstart-dev/cleanstart-use-cases/⁠

Vulnerability Disclaimer

CleanStart offers Docker images that include third-party open-source libraries and packages maintained by independent contributors. While CleanStart maintains these images and applies industry-standard security practices, it cannot guarantee the security or integrity of upstream components beyond its control.

Users acknowledge and agree that open-source software may contain undiscovered vulnerabilities or introduce new risks through updates. CleanStart shall not be liable for security issues originating from third-party libraries, including but not limited to zero-day exploits, supply chain attacks, or contributor-introduced risks.

Security remains a shared responsibility: CleanStart provides updated images and guidance where possible, while users are responsible for evaluating deployments and implementing appropriate controls.