Send Feedback
Skip to content

KDB-X Support Guide

This document outlines how to request and receive support for KDB-X.

Who to contact

To report a technical issue or bug:

Check the section below to make sure your ticket includes all the required details.

What to include in a support ticket

Please provide the following information when opening a ticket:

  • Product version (for example, KDB-X 0.1.0 )
  • Platform (OS name, version, architecture)
  • Steps to reproduce the issue
  • Error messages or stack traces (if applicable)
  • Whether the issue is blocking, and any workarounds attempted

If applicable, include:

  • Sample script that triggers the issue
  • Data example (anonymized if needed)
  • License ID or hostname

Example support ticket

Subject: KDB‑X crash on startup (RHEL 9)

Environment: Red Hat 9.3, KDB‑X 0.1.0, 16-core VM
Issue: Segmentation fault when starting with q -p 5000 -T 60
Steps tried: Checked license, ran with -v, confirmed ulimit/systemd setup
Impact: Blocking automated startup
License ID: LIC-123456, Hostname: prod-kdbx-east

Response time

KX Support will acknowledge your ticket promptly and assign a severity level. Response and resolution times depend on the SLA tied to your license.

Enterprise clients typically receive:

  • Severity 1: Response within 1 hour (24x7)
  • Severity 2: Response within 4 business hours
  • Severity 3: Response within 1 business day

For more details, consult your KX license or support agreement.

Community support

For usage questions, you can also visit:

These forums are best for tips, usage patterns, and collaboration — not guaranteed support.

Feature requests

To suggest new features, enhancements, or integrations, reach out to the KX Slack community channel. Our Product team reviews every feature request and prioritizes them based on demand and feasibility.