Channels
- Bugs & feature requests — open an issue on GitHub. This is also where fixes and known issues are tracked, so search existing issues first — yours may already have a workaround.
- Docs feedback — every docs page has a thumbs rating; use it to flag anything unclear, wrong, or missing. It goes straight to the team.
- Self-managed & on-prem — deployments you run yourself are supported directly. Contact your AcuSight representative for operational issues with platform services, storage, identity, or networking.
- Security vulnerabilities — don’t open a public issue; contact us directly through acusight.io or your AcuSight representative so a fix can ship before details are public.
What to include
A report we can reproduce is a report we can fix. Include:- What you did, what you expected, what happened — the three sentences that matter most.
- Where — your organization name, and the device name for device issues (from Devices).
- When — timestamps and your timezone, so we can line your report up with what the platform saw.
- What it looked like — screenshots of the dashboard, error messages verbatim, and for training issues the job’s status and logs (both visible on the training job page).
Known issues
Known issues and their status live in the GitHub issue tracker. If you hit something already reported, add a comment with your details rather than opening a duplicate — it bumps the signal and you’ll be notified on the fix.Next steps
Troubleshooting
Common issues and their quick fixes.
Changelog
What’s shipped recently.