Skip to main content

v1.12.0

What's Changed​

πŸ” Troubleshoot​

  • feat: Each event now shows whether it is open, has ended, or has come back
  • feat: Add a reason when you close or reopen an alert manually, and see that reason later
  • feat: Edit or disable a Prometheus alert rule where it is defined, or mute it in NudgeBee, directly from the investigation screen
  • feat: Disable GCP and Azure alert rules at the source, and undo cloud changes exactly
  • feat: Pod and provider logs are grouped into highlights and grouped log cards
  • feat: OOM kills that happen on the same node are linked, and investigations show what a container's memory limit was when it was killed
  • feat: Cluster over-commitment alerts now explain what they are about
  • feat: Utilization, Noisy Neighbours, anomaly and SLO evidence, and cluster tiles now work with Datadog, Elasticsearch, OpenObserve, and other metrics providers, not only Prometheus
  • feat: Edit SLOs directly from the SLO table
  • fix: Crash-looping pods keep their alert open between restarts
  • fix: Pods are counted and filtered by the status you see, not their internal phase
  • fix: An object that was edited several times is shown once in change history
  • fix: Latency anomalies are now detected correctly
  • fix: Investigations use the actual incident time window, rule definition, and metric values
  • fix: Recurring events are re-analyzed on their own, without carrying over history from earlier occurrences

πŸ“Š Dashboards​

  • feat: Gauge panels can average values across accounts

⚑ Optimization​

  • feat: Reclaim volumes, resize volumes, and scale down workloads directly from Optimize
  • feat: Rightsizing recommendations show a usage chart and a single, clear decision block, with details available on demand
  • feat: Resize suggestions explain the proposed change and only appear when a workload is under resource pressure
  • feat: The Optimize blast radius lists only direct dependents
  • fix: Volume size recommendations use whole GiB values instead of rounding down to zero
  • fix: A scale-down is labeled as a stop on the approval card
  • fix: Spend by service no longer drops spend for duplicate resources
  • fix: Unattached volumes are priced by their volume type

πŸ”„ Workflow​

  • feat: Event and optimization triggers can listen to several accounts
  • feat: New k8s.profile task to profile a pod and attach the profile to an event
  • feat: Search the pre-built automation templates
  • feat: The foreach sub-task picker now matches the Actions tab and fills in required settings automatically
  • fix: Credentials are now removed from logs, step inputs, errors, and saved state
  • fix: Canceled automation runs no longer stay in "Running"
  • fix: Automations no longer wait on conversations that have already ended
  • fix: Webhook deliveries are no longer dropped silently when their queue is missing
  • fix: AWS commands for load balancers, EKS node groups, and runbooks now use the correct region
  • fix: User-defined script jobs now run in isolation

☸️ Kubernetes​

  • feat: Run commands on discovered VMs through the agent's SSH proxy
  • feat: New VM fleet overview card on the Home page
  • feat: Get alerted before the Postgres volume runs out of space
  • feat: The services server can run API and background-job work in separate pods
  • fix: On-prem upgrades now run database migrations before the upgrade instead of after
  • fix: Control plane resources are sized from measured usage, with limits on every service
  • fix: The relay and collector recover from message broker outages instead of hanging until restarted
  • fix: VM scan results are now recorded reliably

☁️ Cloud​

  • feat: Change an AWS account's region list after onboarding
  • feat: CloudFormation stack resources are discovered
  • fix: AWS alarm definitions keep syncing when one region is unreachable
  • fix: CloudWatch metric math alarms now fetch all of their series, and alarm details are read correctly
  • fix: Investigations pick the container that actually failed instead of the first one
  • fix: CloudTrail event lookups now work
  • fix: Scans and lookups use the AWS region you asked for

πŸ€– AI​

  • feat: Nubi can run kubectl, Helm, and AWS commands against another connected cluster or account in a single request
  • feat: Ask Nubi chats are listed across all accounts, and you choose the account in the message box
  • feat: New VM orchestrator for investigating issues across a VM fleet
  • feat: Remediation plans are validated before you see them, can recover work left unfinished during an incident, and can recommend and apply alert-rule fixes
  • feat: Investigations record the check that proves their root cause
  • feat: Log queries can be written in your log provider's own query language
  • feat: Knowledge Bases can index PDFs, including their figures, and images on Confluence and ServiceNow pages
  • feat: Open a Knowledge Base's document count to see its documents and their full content
  • feat: Knowledge Base search uses the built-in embedding model by default, and ranks results instead of filtering them out
  • feat: Mark which models accept images; attached images are sent to OpenAI-compatible models
  • feat: The code agent follows the repository's own AGENTS.md or CLAUDE.md instructions and skills, and can run long commands in the background
  • feat: Usage & Limits now shows the history of budget changes
  • feat: Tenant-wide actions for agents, tools, and Knowledge Bases; the Functions tab has been removed
  • fix: Detection of high-entropy secrets in outgoing data is now off by default, and can be turned on in the UI (Enterprise)
  • fix: Read-only commands no longer ask for approval unnecessarily, and planning continues after you deny a command
  • fix: Fixes that were never applied are no longer reported as "already present", and NudgeBee checks whether a fix has already shipped before recommending it
  • fix: Remediation plans only offer commands that the Run button accepts, and show only on the incident they were created for
  • fix: Event summaries are written as a short on-call brief
  • fix: Watches describe what they monitor and check one last time before they expire
  • fix: Rate limits that stop an investigation now show the real cause
  • fix: Inconclusive hypotheses are now shown instead of hidden
  • fix: Audit records now include super-admin and automated actions
  • fix: Accounts with several LLM providers use the tenant default provider
  • fix: Tools stay bound to the account you selected
  • fix: Only one Code Analyzer & Fixer agent is listed

πŸ”” Notifications​

  • feat: Notification rules have been redesigned: one rule can cover several event types and accounts, add exceptions and per-source defaults, and pause sending for a set time ("don't send"). A route check shows which rule will match
  • feat: Automation events can be used in notification rules, with a new Automation tab in the rule editor
  • feat: Optimization digests are sent per channel, grouped by account
  • feat: Slack incoming webhooks and Google Chat webhooks as notification targets
  • feat: Follow-up questions with many options show a dropdown next to the web app link
  • fix: Slack alert links open the relevant page instead of Home
  • fix: Nubi now reads Slack thread context correctly
  • fix: The alert report is put together directly instead of being rewritten by a second AI pass
  • fix: The daily recap explains what the Highlights percentages are compared against
  • fix: Brand and assistant names are used consistently across chat platforms

🎫 Tickets​

  • fix: Jira Data Center now works fully with personal access tokens, including lists, projects, and user pickers
  • fix: Jira priority names are accepted in any case, full Jira URLs work, and ticket links keep the context path
  • fix: ServiceNow tickets show comments and the correct priority, accept custom incident numbers, and take assignee, impact, and urgency from the caller
  • fix: ServiceNow and Jira ticket lists now load beyond the first page
  • fix: Tickets are no longer left orphaned when saving fails after creating them in the external system

πŸ”Œ Integrations​

  • feat: Splunk Enterprise metrics support
  • feat: SigNoz support, with log query fixes
  • feat: OpenObserve now answers metric, log, and utilization queries, including Utilization & Health for clusters whose metrics are in OpenObserve
  • feat: OpenObserve and CubeAPM logs can be used when generating queries
  • feat: Webhook URL column and an Activity Log for each integration
  • feat: Slack and Teams integration settings are shown as tabs
  • fix: The CubeAPM alert webhook no longer depends on the external ingress

πŸ›‘οΈ Admin & Platform​

  • feat: New Admin Overview tab with module cards, clickable counts, and a Connections view
  • feat: Separate platform and AI Gateway API keys with expiry dates, all listed in one table; per-key usage limits are available in Enterprise
  • feat: Integrations now appear before Notification Rules in Admin
  • feat: SSL certificate expiry dates always show the year

v1.12.1​

  • feat: Elasticsearch trace support
  • fix: Daily cloud cost sync uses a steady amount of memory regardless of bill size