How mroject/freeswitch_exporter works
Project type and purpose
• This is a single‐binary, full‐stack “Exporter” microservice written in Go.
• Purpose: connect to a FreeSWITCH instance via its mod_event_socket API, collect telephony metrics, and expose them on HTTP (/metrics and /probe) for Prometheus to scrape.
File structure
• Top‐level Go files (main.go, collector.go) and go.mod/go.sum: core service code.
• Dockerfile + .github/workflows/docker-image.yml: CI/CD pipeline building and publishing a container image.
• systemd/ directory: local deployment as a systemd service.
• target/golist.json: auto‐generated dependency snapshot (not part of runtime).
README for additional insights
• Lists Prometheus flags, metrics collected, and the multi‐target “/probe” pattern.
• Mentions optional web.config YAML for TLS/basic‐auth support.
• Describes expected runtime interactions: exporter ⇄ FreeSWITCH, and Prometheus ⇄ exporter.
Essential elements in detail
• Both runtime and build/deployment flows (GitHub Actions → Docker image → container registry).
• Optional paths (e.g., loading web.config for TLS).