Three customer-facing updates shipped the week of June 15, 2026, across Annie. The headline is a new VictoriaMetrics integration, which brings the Anyshift Product Updates series forward from last week's post on RCA evidence. The other two sharpen how Annie investigates and how she hands back a fix.
VictoriaMetrics is now a queryable source
Annie can now investigate against VictoriaMetrics. Connect an instance from the Monitoring section of the integrations page, point Annie at your instance URL with a read-scoped API key, and she ingests its logs and metrics.
From there it behaves like every other source Annie reasons over: she correlates VictoriaMetrics logs and metrics with your resource graph, traces request chains across services, and surfaces the root cause instead of leaving you to jump between dashboards. For self-hosted instances that are not publicly exposed, a Cloudflare Tunnel connects them to Anyshift without opening them to the internet. VictoriaMetrics joins the more than 20 integrations Annie can already query, alongside Datadog, Grafana, Prometheus, and Sentry.
Annie self-verifies her findings
Annie now challenges her own work before she shows it to you. Every root cause analysis goes through a verification pass that re-reads the conclusion, looks for findings she missed, and flags claims that do not hold up under a second look.
When that pass turns up something, Annie amends the answer rather than asking you to catch the gap yourself. The point is reliability: the analysis you act on has already been argued against once, so a missed signal or an over-confident attribution gets corrected on Annie's side instead of yours. It pairs with last week's change that restricted RCA evidence to verifiable signals, since a stricter evidence bar is most useful when the conclusion built on it has also been double-checked.
Pull request fixes now show up in reports
Annie's pull request fixes are no longer limited to chat. Report findings now render an Open PR call to action, so a proactive report that flags a problem can hand you a ready-to-open pull request in the same view.
This closes a gap from the earlier chat-only rollout. A scheduled report or an on-call summary that points at a misconfiguration now carries the fix next to the finding, rather than making you reopen a chat to ask for it. This change is live across 4 deployed services, headlined by annie-intelligence v0.102.0.
FAQ
What shipped at Anyshift the week of June 15, 2026?
Three customer-facing updates. Annie gained a VictoriaMetrics integration, a self-verification step that re-checks her own findings before presenting them, and pull request fix proposals that now appear directly on report findings, not just in chat.
What is the Anyshift VictoriaMetrics integration?
Connect a VictoriaMetrics instance from the Monitoring section of the integrations page and Annie ingests its logs and metrics. During an investigation she correlates those signals with your resource graph instead of asking you to jump between dashboards.
What does self-verification do in an Annie investigation?
Annie now runs a verification pass over her own root cause analyses. The step looks for findings she missed or claims that do not hold up, then amends the answer before you see it, so the result you act on has already been challenged once.
Where do Annie's pull request fixes show up now?
Fix proposals are no longer limited to chat. Annie now renders an Open PR call to action on the findings inside her reports, so a proactive report can hand you a ready-to-open pull request in the same place it flags the problem.
Where can I try these updates?
Open Annie at app.anyshift.io and connect VictoriaMetrics, run a root cause analysis, or open a proactive report. The product documentation at docs.anyshift.io covers each integration and feature.
That's the week. Try it and tell us what it unlocks for your team. We read every reply at app.anyshift.io.
