Skip to content

Click-Dog Production Support

Click-Dog has two support paths: public community support for the open-source project, and production support for teams that want direct help with deployment, integration, or troubleshooting.

Direct maintainer support

Work directly with the team that builds Click-Dog

Get focused help from Colt Consulting, Click-Dog's creator and maintainer. The same people who work on the exporter, deployment tooling, integrations, and documentation work with you on your environment.

Discuss your deployment

Commercial support is contracted and provided by Colt Consulting Ltd, the company behind Click-Dog.

What production support covers

Production support is scoped around the part of the rollout or operation where you need help. It can include:

Deployment and go-live review

  • ClickHouse topology and source readiness
  • Deployment model, configuration, and upgrade planning
  • Query-text privacy, TLS, credentials, and least-privilege access
  • Dry-run, health, dashboard, and go-live checks

Integration and troubleshooting

  • ClickHouse span-log and query-log readiness
  • OTEL collector and exporter routing
  • Datadog, Honeycomb, Grafana Tempo, Splunk HEC, and generic OTLP integration
  • Export, dashboard, or query-analysis troubleshooting

Custom engineering

  • New exporter targets or collector patterns
  • Deployment automation for internal platforms
  • Dashboard, monitor, or alert templates
  • Additional filtering, enrichment, or reporting behavior
  • Production hardening and operational review

Start the conversation

Email support@click-dog.com with your Click-Dog version, ClickHouse topology, deployment method, target backend, rollout stage, and the outcome you need.

Commercial work is quoted based on scope, urgency, and the shape of the environment. Any response-time commitment is agreed as part of the engagement; the public open-source project does not carry a response-time guarantee.

Community support

Use GitHub for project questions, bug reports, and feature requests:

  • Search existing issues before opening a new one.
  • Include the Click-Dog version, deployment method, relevant config snippets with secrets removed, and any click-dog check output that applies.
  • For suspected security vulnerabilities, use the private reporting path in SECURITY.md instead of a public issue.

Community support is best effort and does not include response-time guarantees.