SonarQube Support & Upgrades
Last reviewed by Tyler Eastridge
AceMQ gives DevOps and platform teams engineers for self-hosted SonarQube, Community Build or the Developer, Enterprise and Data Center editions: upgrades across LTA versions, database and search sizing, Kubernetes and Helm installs, and 24/7 cover when analyses stop completing. AceMQ engineers lead and partner SonarQube specialists join the work. AceMQ is an independent provider: it is not a reseller, sells no SonarQube license and gives no licensing advice.
A senior engineer, not an SDR. No sales sequence attached.
Without changing what your quality gates enforceFor production incident cover, see AceMQ SonarQube 24/7 support.
Customers
Partners
The Problem
Six SonarQube problems self-hosted teams run into, from a server nobody dares upgrade to a search process that stopped on a full disk. If one describes your week, that is where the look starts.
The server is several versions behind, and nobody has worked out which LTA versions it must pass through to reach the current one
Analyses queue up and quality gate results arrive late or not at all, so pipelines stall waiting for them
Disk use passed 90% and the search process crashed, or its indices were locked read-only at 95%, and the server has been unusable since
The database has grown for years, and nobody has tested how long a migration takes or whether the disk can hold a second copy of its tables
Scanner versions in CI are a mixed bag, and the upgrade changes which ones the server will accept
The server still runs from a ZIP install on a virtual machine, and the move to Docker or Helm has no owner
A good fit if you run SonarQube yourself, on virtual machines or Kubernetes, and need an upgrade planned, a server tuned or senior engineers on call when analyses stop.
Not a fit for small teams with non-critical workloads. AceMQ is not a budget consultancy: we work with enterprises running business-critical and compliance-heavy SonarQube.
How it breaks, and the fix
Pipelines wait for quality gate results that never arrive, and the server looks alive. The scanner finished, the database is healthy, but the search process behind the web server cannot write to a disk that has run out of headroom.
Analysis report arrives at a full disk
One report, two stores, one Compute Engine, one gate result
Reports are accepted, the Compute Engine finishes each task, and quality gate results arrive in the pipeline minutes after the scan.
Free disk falls below the 10% Sonar requires. Elasticsearch crashes above its 90% high watermark by default, and at 95% it locks all indices in read-only mode. The database is fine, but the Compute Engine cannot finish, so gate results stop and tasks queue.
Disk is expanded or cleared and the search process is healthy again. The Compute Engine works through the queued tasks in order, and the pipelines that were waiting get their results.
Sonar lists free disk space as an absolute requirement: 10% free, because Elasticsearch crashes if usage passes its high watermark, which is 90% by default, and locks all indices read-only at 95%. The same headroom rule applies to updates. Sonar recommends database disk use below 50% before a migration because tables can be duplicated, and notes that usage can temporarily double. The memory settings follow the same pattern of defaults that are maximums, not reservations: the web, Compute Engine and search processes each have their own JVM heap, and the defaults differ between Developer and Enterprise or Data Center. Sonar's host requirements also say not to use remote-mounted storage such as NFS, SMB/CIFS or NAS. A look at disk trend, heap settings and queue length before the incident is what the health check delivers.
Our Services
AceMQ runs four SonarQube service lines: upgrade planning, sizing and search tuning, Kubernetes and Helm, and a fixed-scope health check. Support can follow any of them. AceMQ resells no SonarQube license and gives no licensing advice.
A written path from your version to the current LTA, following Sonar's own update rules, rehearsed on a restored copy of production before the change window.
Memory, disk and database settings for the web, Compute Engine and search processes, set against what your instance actually analyzes.
Running SonarQube on Kubernetes with the Helm chart, and moving a ZIP install to containers before ZIP support is removed.
The fixed-scope entry engagement: a written report on the state of the instance that your own team can act on, with or without AceMQ afterwards.
Senior engineers on your account, a 15-minute emergency response, no ticket routing and no junior triage.
24/7 Support
AceMQ SonarQube support gives you an AceMQ engineer and a 15-minute first response when analyses stop completing or the server is down, 24/7. Lower severities get 1-hour, 4-hour and next-day responses. SonarSource sells its own support tiers for the product, and AceMQ works alongside them.
P1 escalation path
A replay of one P1, from the first page to the written root-cause analysis
15-minute P1 response, 24/7.
A response time, not a resolution time.
P1 opened, on-call engineer paged
Phone, email or Slack reaches the on-call senior engineer directly, whether the incident is in RabbitMQ, Kafka, Redis, PostgreSQL or Kubernetes. No web form, no tier-1 queue.
Senior engineer on your bridge
A senior engineer who already knows your environment joins a live bridge, so nobody has to re-explain your topology.
Specialists across the stack join
When an incident crosses components, the engineers who know each one join. For RabbitMQ, the path runs to the core team.
Written root-cause analysis
Root cause, the fix applied and the prevention steps, delivered after every P1.
Beyond SLAs — the model behind senior-only, zero-cold-start expert access.
Tickets go to senior engineers briefed on your environment, not an anonymous queue. The proposal states who does the work.
Any ticket can be escalated to a live session with an engineer through calendar booking. No gatekeeping and no approval step.
Scheduled health checks on your deployment and alerts on risks in the versions you run, so problems surface before they reach production.
Release notes and lifecycle dates read against your environment, with an upgrade plan that fits your change windows.
How It Works
A SonarQube engagement at AceMQ runs in four stages: a scoping call with a quote within 1 hour, a read-only look at the instance and its host, a written plan with a timed rehearsal, then the upgrade or fix and a handover.
Quote within 1 hour
A senior AceMQ engineer asks what you run: edition or Community Build, version, install type, database and its size, how many projects and scanners, and what has gone wrong. A quote request is answered within 1 hour.
Scoped per instance
Version and LTA position, database size and free disk, search and Compute Engine memory settings, scanner versions in CI, plugins and the install type are read from the instance and its host. Nothing is changed.
Scoped per instance
The update path with every LTA named, the pre-update checks, a restore-to-staging rehearsal with the migration timed, and the order of scanner updates. Each step says how it is reverted.
Ongoing or fixed scope
The update is run in your change window with your engineers, or the incident is fixed and written up. You keep the runbook, the timings and the post-update checklist. Support can continue 24/7.
A senior engineer, not an SDR. No sales sequence attached.
Typical engagements
Typical SonarQube engagements from AceMQ: what the environment looks like, what AceMQ assesses or changes, and what the engagement delivers. Each card links to the full write-up.
Solutions
AceMQ covers SonarQube end to end. Projects: consulting and implementation, health checks and migrations. Ongoing cover in four tiers, from 24/7 support and incident management to proactive monitoring, managed SonarQube on your infrastructure and fully managed SonarQube on AceMQ infrastructure, plus end-of-life versions.
Projects
Fixed-scope work led by a senior engineer: architecture and new builds, a health check of what you run today, or a migration with a reversible cutover.
Support and managed services
Four tiers of ongoing cover once you are live. Each tier hands more of the day-to-day work to AceMQ, from a 15-minute emergency SLA to AceMQ hosting and running SonarQube for you.
Compare the four SonarQube support tiersSide by side
Sonar ships six releases a year and two are Long-Term Active (LTA). Its rule is to update to each LTA on the path, at its latest patch, and to go from the latest LTA straight to the latest non-LTA. Each row below starts from a different version, and the last column lists what to check before that hop. Read from Sonar's documentation on 4 November 2026.
| Starting from | Update route | Why | Check before this hop |
|---|---|---|---|
| 9.9 LTA | 9.9 LTA, then 2025.1 LTA, then 2026.1 LTA, then 2026.5 LTA, each at its latest patch. | An LTA on the path is passed through. Sonar's own example for 9.9 runs 9.9 LTA, 2025.1 LTA, 2026.1 LTA. | Release notes for each hop. 2026.1 removed Java 17 and dropped PostgreSQL 13 and SQL Server 2016. |
| 10.6, which is not an LTA | Via 2025.1 LTA first, then onward through each LTA to 2026.5. | Sonar's example: 10.6 to 2025.3 goes through 2025.1 LTA, because an LTA lies on the path. | Database disk use under 50% and a backup. Scanner versions for the target of each hop. |
| 2026.1 LTA | Directly to 2026.5 LTA, at its latest patch. | From an LTA you can go straight to the next LTA, and an LTA target is updated to its latest patch. | 2026.5 dropped PostgreSQL 14. Security Hotspots are being phased out, with the migration forced at 2027.1. |
| An earlier 2026.5 patch | Straight to the latest 2026.5 patch. | Sonar says to update directly to the latest patch of an LTA. | Migrate Security Hotspots only on 2026.5.3 or later: a known issue on 2026.5.0 to 2026.5.2 can make reviewed hotspots reappear as Open issues. |
| The latest LTA, heading to the newest non-LTA | Directly, with no stop in between. | Sonar allows an update from the latest LTA to the latest non-LTA. | Sonar patches the latest version and each LTA while it receives patches, so a non-LTA is covered only while it is the newest. Plan the next hop. |
Community Build has no LTA concept, so these routes apply to SonarQube Server. AceMQ prints no Sonar prices and gives no licensing advice: edition and license questions go to SonarSource.
One partner, not five
SonarQube rarely fails in isolation. AceMQ covers the full surrounding infrastructure — so one team owns the whole path instead of pointing at each other.
Guides, articles and comparisons
AceMQ services around the platform SonarQube runs on: Kubernetes, Java, PostgreSQL and monitoring with Prometheus and Grafana.
FAQs
Five answers on SonarQube from AceMQ: versions and patch windows, upgrade checks, what AceMQ does not resell, how engagements run and what they cost.
Still have questions about SonarQube? Email an Expert
Sonar ships six releases a year, two of them Long-Term Active (LTA). On 4 November 2026 its documentation was written for 2026.5, the current LTA, with 2026.1 the one before. From 2026.5, Developer, Enterprise and Data Center customers get 12 months of patches from the release date, and 18 months with Enterprise Support. The Sonar pages read for this page print no end-of-patch date for 2026.1, so confirm it with SonarSource rather than assuming.
Sonar's pre-update steps: read the release notes for every version in between, keep database disk use under 50% because tables can be duplicated during migration, back up the database, run database maintenance on a large instance, check SonarScanner versions, and restore a recent backup to staging to time the update. Also check the platform: 2026.5 supports PostgreSQL 15 to 18, SQL Server 2017 to 2025 and Oracle 19c, 21c and 26ai, and ZIP installs need Java 21 or 25.
No. AceMQ is an independent provider: it is not a reseller, sells no SonarQube license and gives no licensing advice. Developer, Enterprise and Data Center editions are licensed by SonarSource per instance per year by lines of code, and Community Build is the free edition. SonarSource sells its own Core, Standard and Enterprise Support tiers. AceMQ's part is the operating layer: upgrades, sizing, Kubernetes and 24/7 incident response, alongside SonarSource support if you buy it.
Yes. AceMQ works on SonarQube in two ways: ad hoc engagements for a defined piece of work, such as a health check, an upgrade or an incident, or an annual contract that covers 24/7 support and proactive reviews. Many teams start ad hoc and move to an annual contract once the first engagement is done.
Every AceMQ proposal is tailored to your requirements: your SonarQube environment, the SLA you need, the hours of cover and the scope of work. Most contracts run $24,000–72,000 a year, depending on the SLA, the scope and how SonarQube is deployed, with aggressive discounts when several technologies share one contract. Request a quote and AceMQ replies within 1 hour.
Let's talk
A senior AceMQ engineer looks at your SonarQube instance, tells you what to check first, and quotes the work. Quote requests are answered within 1 hour.
Production incident right now?Email a SonarQube Architect
Send us a message and we'll follow up within 1 hour — or book a free 30-min consultation directly.
305-204-2607info@acemq.comPrefer to talk now? Call us directly or use the consultation tab to find a time that works.
