OneUptime changelog

version

14.0.107 → 14.0.110

version

14.0.106 → 14.0.107

version

14.0.105 → 14.0.106

version

14.0.104 → 14.0.105

version

14.0.103 → 14.0.104

https://oneuptime.com/llms.txt

− - [Blog RSS feed](https://oneuptime.com/blog/rss.xml): every post also has a raw markdown variant at /blog/post/<post>/markdown− - [OneUptime Cloud Monitoring](https://oneuptime.com/product/cloud.md): Monitor AWS, Google Cloud, and Azure with OpenTelemetry. Auto-discovered cloud environments, real-time resource metrics, logs, traces, and alerting across every region and account. Open source.− ## Recent Blog Posts− - [How to Turn Customer Outage Reports into SLIs and Alerts for Earlier Detection](https://oneuptime.com/blog/post/2026-09-29-customer-outage-report-to-sli-alert/markdown): Convert a customer-reported failure into a measurable user-outcome SLI, a scoped alert, and a replay test that demonstrates the new detection path reaches responders.− - [How to Train a Shadow Incident Commander with Drills, Handoffs, and Reviews](https://oneuptime.com/blog/post/2026-09-29-train-shadow-incident-commander/markdown): Develop incident commanders through structured observation, realistic drills, explicit handoffs, supervised command, and evidence-based readiness reviews.− - [How to Produce Audit Evidence from Incident Tabletop Tests and Game Days](https://oneuptime.com/blog/post/2026-09-29-incident-response-exercises-audit-evidence/markdown): Turn incident response exercises into traceable evidence by linking objectives to scenario injects, observed decisions, technical checks, findings, and verified follow-up work.− - [How to Capture Incident Commands and Evidence Without Leaking Secrets](https://oneuptime.com/blog/post/2026-09-29-capture-incident-evidence-without-secrets/markdown): Preserve incident commands, outcomes, and evidence with explicit capture boundaries, restricted originals, and reviewed summaries that keep credentials and customer data out of broad channels.− - [How to Coordinate Provider Outages: Escalation, Updates, and Mitigations](https://oneuptime.com/blog/post/2026-09-29-coordinate-third-party-provider-outage/markdown): Coordinate provider failures through a useful escalation packet, independent customer-impact measurements, parallel mitigation work, and evidence-based recovery checks.− - [How to Write Useful Incident Status Updates Without a Recovery ETA](https://oneuptime.com/blog/post/2026-09-29-status-updates-without-recovery-eta/markdown): Write incident updates that remain useful without a recovery estimate by stating current impact, remaining uncertainty, concrete actions, and the next communication checkpoint.− - [How to Build a Canonical Incident Channel for Parallel Debugging](https://oneuptime.com/blog/post/2026-09-29-canonical-incident-channel-parallel-workstreams/markdown): Keep incident decisions, ownership, and current impact in one canonical channel while technical teams investigate independently through explicit workstream contracts.− - [How to Split or Merge Incidents That Share an Upstream Dependency](https://oneuptime.com/blog/post/2026-09-29-split-merge-incidents-shared-dependency/markdown): Coordinate simultaneous incidents around shared dependencies while preserving distinct customer impact, responder ownership, recovery criteria, and historical incident identity.− - [How to Route Incidents with Missing, Stale, or Ambiguous Service Ownership](https://oneuptime.com/blog/post/2026-09-29-incident-routing-missing-stale-ownership/markdown): Keep incidents owned when service metadata is incomplete by using a durable fallback, validating candidate teams, and requiring acknowledged routing transfers.− - [How to Measure Partial or Multi-Tenant Outage Impact with Segmented SLIs](https://oneuptime.com/blog/post/2026-09-29-partial-multitenant-outage-segmented-slis/markdown): Measure partial outage impact with bounded cohort SLIs, volume-aware queries, explicit missing-data states, and separate request and tenant impact estimates.− - [How to Bound Emergency Mitigations with Guardrails and Abort Criteria](https://oneuptime.com/blog/post/2026-09-29-emergency-mitigation-guardrails-abort-criteria/markdown): Bound emergency production changes with explicit scope, independent observation, measurable abort conditions, and a recovery action that remains safe after the change.− - [How to Choose Rollback, Failover, or a Forward Fix During an Incident](https://oneuptime.com/blog/post/2026-09-29-incident-rollback-failover-fix-forward-decision/markdown): Choose rollback, failover, or a forward fix during an incident by comparing time to verified recovery, compatibility, capacity, and irreversible risk.− - [How to Preserve Incident Evidence Before Pods, Instances, and Logs Disappear](https://oneuptime.com/blog/post/2026-09-29-preserve-ephemeral-incident-evidence/markdown): Capture volatile Kubernetes and autoscaling evidence before replacement or retention removes it, while recording identity, collection limits, and restricted evidence storage.− - [How to Assign and Revise Incident Severity When Impact Is Uncertain](https://oneuptime.com/blog/post/2026-09-29-provisional-incident-severity-unknown-impact/markdown): Assign a provisional incident severity from observed impact and credible uncertainty, then revise it with evidence, named ownership, and a preserved decision history.− - [How to Run Incident Command Safely with Combined Roles on a Small Team](https://oneuptime.com/blog/post/2026-09-29-small-team-incident-command-roles/markdown): Run incident command with one to four responders by making combined roles explicit, protecting operational attention, and splitting responsibilities before coordination fails.− - [All posts](https://oneuptime.com/blog)+ - [Connect an AI agent](https://oneuptime.com/tool/mcp-server.md): the address, how to sign in, each client's setup and the plan it needs+ - [Blog RSS feed](https://oneuptime.com/blog/rss.xml): every post's page answers `Accept: text/markdown` with the post as Markdown, which is also at /blog/post/<post>/markdown+ - [OneUptime Cloud Monitoring](https://oneuptime.com/product/cloud.md): Connect AWS, Google Cloud, and Azure accounts read-only and monitor every resource in them: provider metrics, changes, health events, a topology map, and alerting across every region and account. Open source.+ - [OneUptime App Platforms](https://oneuptime.com/product/app-platforms.md): Monitor the apps you run on AWS ECS and Fargate, Google Cloud Run, Azure App Service and other managed platforms with OpenTelemetry: environments by platform, running instances, logs, traces, and alerting. Open source.+ - [OpenShift Monitoring](https://oneuptime.com/product/openshift.md): Monitor OpenShift beside your EKS, AKS and GKE clusters in the OneUptime Kubernetes product. One helm install with the openshift preset, no oc adm policy step.+ - [Air-Gapped Observability](https://oneuptime.com/enterprise/air-gapped/observability.md): Logs, metrics, traces, exceptions and profiles with no internet. Send OpenTelemetry to your own install, and keep every record in your own ClickHouse.+ - [Air-Gapped Log Management](https://oneuptime.com/enterprise/air-gapped/log-management.md): Centralize logs with no internet. Fluent Bit, Fluentd, syslog and OpenTelemetry send to your own install, and secrets are scrubbed before anything is stored.+ - [Air-Gapped Uptime & Synthetic Monitoring](https://oneuptime.com/enterprise/air-gapped/monitoring.md): Run probes inside your network to check websites, APIs, ports, certificates, SQL databases and browser journeys, with no internet and no browser to download.+ - [Air-Gapped Incident Management](https://oneuptime.com/enterprise/air-gapped/incident-management.md): Declare, page, work and write up incidents with no internet. Incidents, postmortems, runbooks and AI drafts all run inside your own network.+ - [Air-Gapped On-Call](https://oneuptime.com/enterprise/air-gapped/on-call.md): On-call schedules and escalation with no internet. Page people through your own mail server, your webhooks, and a gateway you run for SMS and calls.+ - [Air-Gapped Status Pages](https://oneuptime.com/enterprise/air-gapped/status-pages.md): Status pages with no internet. Sign people in with your own identity provider, upload your own certificates, and tell subscribers through your own mail server.+ - [Air-Gapped Kubernetes Monitoring](https://oneuptime.com/enterprise/air-gapped/kubernetes.md): Monitor Kubernetes clusters with no internet. Run the OneUptime agent chart from images in your own registry, on OpenShift too, and send to your own install.+ - [Air-Gapped Network Monitoring](https://oneuptime.com/enterprise/air-gapped/network-monitoring.md): Monitor switches, routers and firewalls with no internet. A probe on your network polls SNMP and takes traps, syslog and flows, with no vendor cloud to reach.+ - [Air-Gapped Infrastructure Monitoring](https://oneuptime.com/enterprise/air-gapped/infrastructure.md): Monitor hosts, VMware, Proxmox, Ceph and storage arrays with no internet. A collector or probe on your network reports to your own install.+ - [Air-Gapped AI for Incidents](https://oneuptime.com/enterprise/air-gapped/ai.md): OneUptime AI with no internet: investigations, Ask AI, drafts and fixes on a model you run with Ollama or vLLM, so telemetry never leaves your infrastructure.+ - [Air-Gapped SIEM](https://oneuptime.com/enterprise/air-gapped/security-events.md): A SIEM with no internet. Detection rules ship with the install, threat feeds come from your own MISP or OpenCTI server, and every case stays on your network.+ - [Air-Gapped Workflows & Runbooks](https://oneuptime.com/enterprise/air-gapped/workflows.md): Automate incident response with no internet. Workflows post to Mattermost and IRC on your network, and runbooks run on a Runner you host, over SSH and Bash.+ ## Integrations+ - [OpenTelemetry Integrations for Every Framework](https://oneuptime.com/integrations.md): OpenTelemetry guides for Node.js, Python, Java, Kotlin, .NET, Go, Ruby, PHP, Rust and Elixir, from Express and Django to Rails and Phoenix, each run end to end.+ - [Node.js OpenTelemetry: Traces, Metrics & Logs](https://oneuptime.com/integrations/opentelemetry/nodejs.md): Add OpenTelemetry to any Node.js app: one file for ES modules and CommonJS, automatic HTTP and database spans, runtime metrics and logs, sent to OneUptime.+ - [Express OpenTelemetry: Tracing, Metrics & Logs](https://oneuptime.com/integrations/opentelemetry/express.md): Instrument Express with OpenTelemetry: route and middleware spans, per-route latency, pino and winston logs with trace IDs, and errors, sent to OneUptime.+ - [NestJS OpenTelemetry: Tracing, Logs & Errors](https://oneuptime.com/integrations/opentelemetry/nestjs.md): Instrument NestJS 12 and 11 with OpenTelemetry: route spans, nestjs-pino logs with trace IDs, a filter that records 5xx errors, and metrics, sent to OneUptime.+ - [Next.js OpenTelemetry: Tracing & Monitoring](https://oneuptime.com/integrations/opentelemetry/nextjs.md): Set up OpenTelemetry in Next.js 16 with instrumentation.ts: route and render spans, fetch and database calls, server errors and logs, sent to OneUptime.+ - [Fastify OpenTelemetry with @fastify/otel](https://oneuptime.com/integrations/opentelemetry/fastify.md): Trace Fastify 5 with OpenTelemetry and @fastify/otel: request, hook and handler spans, pino logs with trace IDs, metrics, and 5xx errors in OneUptime.+ - [Koa OpenTelemetry: Tracing and winston Logs](https://oneuptime.com/integrations/opentelemetry/koa.md): Trace Koa 3 and @koa/router with OpenTelemetry: a span per route, winston logs with trace IDs, metrics and each error recorded once, in OneUptime.+ - [hapi OpenTelemetry: Tracing and hapi-pino Logs](https://oneuptime.com/integrations/opentelemetry/hapi.md): Trace hapi 21 with OpenTelemetry: route, plugin and extension spans, hapi-pino logs with trace IDs, metrics and failed requests in OneUptime.+ - [Bun OpenTelemetry: Tracing Bun.serve Apps](https://oneuptime.com/integrations/opentelemetry/bun.md): Send traces, metrics and logs from Bun to OneUptime with OpenTelemetry: the SDK preloaded, a server span per Bun.serve route, traced fetch and logs.+ - [Deno OpenTelemetry: Built-in Tracing and Logs](https://oneuptime.com/integrations/opentelemetry/deno.md): Turn on Deno 2's built-in OpenTelemetry and send Deno.serve traces, fetch spans, console logs and metrics to OneUptime, with spans named per route.+ - [Browser OpenTelemetry: Real User Monitoring](https://oneuptime.com/integrations/opentelemetry/browser.md): Instrument any web app with the OpenTelemetry browser SDK: page loads, fetch calls, clicks, errors, logs and Core Web Vitals, as RUM in OneUptime.+ - [React OpenTelemetry: RUM, Errors and Web Vitals](https://oneuptime.com/integrations/opentelemetry/react.md): Trace a React 19 app with OpenTelemetry: page loads, fetch calls, a span per route change, React's caught errors and Core Web Vitals, in OneUptime.+ - [Angular OpenTelemetry: RUM and Error Tracking](https://oneuptime.com/integrations/opentelemetry/angular.md): Trace an Angular 22 app with OpenTelemetry: page loads, HttpClient calls, a span per navigation, every error Angular handles and Core Web Vitals.+ - [Python OpenTelemetry: Traces, Metrics & Logs](https://oneuptime.com/integrations/opentelemetry/python.md): Add OpenTelemetry to any Python app with opentelemetry-instrument or in code: HTTP spans, logging with trace IDs, process metrics, all sent to OneUptime.+ - [Django OpenTelemetry: Tracing, Metrics & Logs](https://oneuptime.com/integrations/opentelemetry/django.md): Instrument Django with OpenTelemetry: views traced by URL pattern, ORM queries, logging with trace IDs, under gunicorn or uWSGI, sent to OneUptime.+ - [Flask OpenTelemetry: Tracing, Metrics & Logs](https://oneuptime.com/integrations/opentelemetry/flask.md): Instrument Flask with OpenTelemetry under gunicorn: routes, SQLAlchemy queries, outgoing calls, error handlers and logging with trace IDs, sent to OneUptime.+ - [FastAPI OpenTelemetry: Tracing, Metrics & Logs](https://oneuptime.com/integrations/opentelemetry/fastapi.md): Instrument FastAPI with OpenTelemetry under uvicorn: one clean span per request, async httpx calls, logging with trace IDs, nothing lost on shutdown.+ - [Celery OpenTelemetry: Task Tracing & Worker Logs](https://oneuptime.com/integrations/opentelemetry/celery.md): Trace Celery tasks with OpenTelemetry: one trace from the code that queues a task to the worker that runs it, failed tasks, task logs, sent to OneUptime.+ - [Java OpenTelemetry Agent: Traces, Metrics & Logs](https://oneuptime.com/integrations/opentelemetry/java.md): Add the OpenTelemetry Java agent to any JVM app: traces for HTTP, JDBC and messaging, JVM metrics and Logback or Log4j logs, sent to OneUptime with no code.+ - [Spring Boot OpenTelemetry: Java Agent or Starter](https://oneuptime.com/integrations/opentelemetry/spring-boot.md): Instrument Spring Boot with OpenTelemetry: the Java agent or the Spring Boot starter, MVC routes, JPA and JDBC, RestClient, JVM metrics and logs, to OneUptime.+ - [Quarkus OpenTelemetry: Tracing, Metrics & Logs](https://oneuptime.com/integrations/opentelemetry/quarkus.md): Set up Quarkus's OpenTelemetry extension for OneUptime: REST endpoints, REST client calls, JDBC, metrics and logs, and the build-time switches they need.+ - [Micronaut OpenTelemetry: Tracing, Metrics & Logs](https://oneuptime.com/integrations/opentelemetry/micronaut.md): Set up Micronaut's OpenTelemetry modules for OneUptime: routes, HTTP client calls, JDBC, metrics and Logback logs, with the exporters Micronaut leaves off.

Showing the first 40 of each.

https://raw.githubusercontent.com/oneuptime/oneuptime/HEAD/AGENTS.md

− An email is read wherever its reader is - on a network without the internet, behind a mail gateway that flags remote images - and every image it fetches tells whoever serves it who opened the email, and when (issue #5124: every email's header loaded its logo from res.cloudinary.com). So an email's own markup loads nothing it does not carry: an image is either inside the email - OneUptime's logo (`oneUptimeLogoUrl`, `packages/Common/Server/Utils/Mail/EmailLogo.ts`) and screenshots go out as inlin+ An email is read wherever its reader is - on a network without the internet, behind a mail gateway that flags remote images - and every image it fetches tells whoever serves it who opened the email, and when (issue #5124: every email's header loaded its logo from res.cloudinary.com). So an email's own markup loads nothing it does not carry: an image is either inside the email - OneUptime's logo (`oneUptimeLogoUrl`, `packages/Common/Server/Utils/Mail/EmailLogo.ts`) and screenshots go out as inlin+ ### Release notes+ Each release's notes on GitHub, which the upgrade guide sends self-hosters to and the website links to as the Changelog, are written by `Scripts/Release/GenerateReleaseNotes.js` from what the release ships: the title of every pull request and the subject of every commit pushed straight to master. So a title is a line someone reads on the release page. Write it as `type(area): what changed, for the person using OneUptime`, not what the code does.+ - `feat`, `fix`, `perf` and `docs` each have a section. `test`, `ci`, `chore`, `refactor`, `style` and `build` go under Maintenance, which is folded, and so does anything in an area of the repository rather than the product (`fix(ci): ...`; `INTERNAL_AREAS` in the script).+ - The scope is the area the line is filed under: use the product's name (`exceptions`, `on-call`, `status-pages`). A title with no type can open with its area instead (`Workflows: every template in five steps`); it goes under New and improved.+ - A `!` after the type or scope (`feat(helm)!: ...`) puts the change under Breaking changes, at the top. Use it whenever an upgrade asks something of the person upgrading.+ - A label wins over a title (`bug`, `enhancement`, `documentation`, `dependencies`), and `ignore` leaves a pull request out.+ To see a release's notes, or write a published release's again:+ ```bash+ GH_TOKEN=$(gh auth token) node Scripts/Release/GenerateReleaseNotes.js --version 14.0.98 --output notes.md+ gh release edit 14.0.98 --notes-file notes.md+ ```+ With `--to master` and no `--version`, it shows what the next release will say.+ ### Continue with Google+ The **Continue with Google** button on the sign-in and sign-up pages runs on a Google OAuth client in Google Cloud, not+ in this repository: merging code turns nothing on, and a server offers the button only once `GOOGLE_SIGN_IN_CLIENT_ID`+ and `GOOGLE_SIGN_IN_CLIENT_SECRET` are set (Helm `googleSignInApp`). Its code is the Google client in+ `packages/Common/Server/Utils/GoogleSignIn` and the provider sign-in it shares with Sign in with Microsoft+ (`packages/App/FeatureSet/Identity/Utils/ProviderSignIn.ts`: who may sign in, the state cookie, the campaign a new+ account keeps). Before changing that code, the button, or anything in Google Cloud, read+ [the Continue with Google guide](packages/Common/Server/Utils/GoogleSignIn/RELEASING.md). It says how to set up the+ consent screen and the OAuth client and their redirect URI, what the button must look like under Google's branding+ rules, how to test it end to end, and which steps only a maintainer may do.+ ### Iron Bank+ The App (its Enterprise Edition), ingress, runner and probe images are also packaged for Iron Bank, the US Department of+ Defense's registry of hardened images (registry1.dso.mil), from `IronBank/App`, `IronBank/Ingress`, `IronBank/Runner` and+ `IronBank/Probe`. Iron Bank's pipeline does not build them: each project's Dockerfile copies what a release's image adds+ (`/usr/src`, and the ingress's nginx configuration, the runner's kubectl, the probe's browsers and Node.js) onto an Iron+ Bank base image of the same distribution, and sets again what the release's Dockerfile sets. So when you change+ `packages/App/Dockerfile.tpl`, `packages/Nginx/Dockerfile.tpl`, `packages/Runner/Dockerfile.tpl` or+ `packages/Probe/Dockerfile.tpl` - a start command, entrypoint, user, environment variable, label or package, or what the+ image copies or builds in - `Tests/Ops/IronBankApp.test.js` or `IronBankProjects.test.js` fails until the project's+ Dockerfile does the same. Before changing anything in `IronBank/`, `Scripts/IronBank/` or `.github/workflows/iron-bank.yml`+ (the "Iron Bank Preflight" workflow), read [the Iron Bank guide](IronBank/README.md).

• + create_security_case_task
• + get_security_case_task
• + list_security_case_tasks
• + update_security_case_task
• + delete_security_case_task
• + count_security_case_tasks
• + create_security_case_evidence
• + get_security_case_evidence
• + list_security_case_evidence
• + update_security_case_evidence
• + delete_security_case_evidence
• + count_security_case_evidence
• + create_security_case_priority
• + get_security_case_priority
• + list_security_case_priorities
• + update_security_case_priority
• + delete_security_case_priority
• + count_security_case_priorities
• + create_security_case_status
• + get_security_case_status
• + list_security_case_statuses
• + update_security_case_status
• + delete_security_case_status
• + count_security_case_statuses
• + create_data_store
• + get_data_store
• + list_data_stores
• + update_data_store
• + delete_data_store
• + count_data_stores
• + create_data_store_finding
• + get_data_store_finding
• + list_data_store_findings
• + update_data_store_finding
• + delete_data_store_finding
• + count_data_store_findings
• + create_data_store_access_entry
• + get_data_store_access_entry
• + list_data_store_access_entries
• + update_data_store_access_entry

Showing the first 40 of each.

version

14.0.96 → 14.0.103

version

14.0.95 → 14.0.96

version

14.0.94 → 14.0.95

version

14.0.93 → 14.0.94

version

14.0.92 → 14.0.93

https://raw.githubusercontent.com/oneuptime/oneuptime/HEAD/AGENTS.md

− OneUptime Cloud is sold on AWS Marketplace, Microsoft Marketplace (Azure) and Google Cloud Marketplace through− `packages/Common/Server/Utils/Marketplace` (purchases, landing pages, webhooks, hourly usage reporting) and Sign in with− Microsoft. Before changing that code, its settings, the marketplace usage prices, or anything in a seller portal, read− OneUptime Cloud is also a native integration on the Vercel Marketplace (`packages/Common/Server/Utils/Marketplace/Vercel`:− the provider API Vercel calls, sign-in from Vercel, webhooks, monitors of connected projects, Vercel invoices) with its− log drain in the Telemetry service. Before changing that code, the resources' secrets or plans, or anything in Vercel's− Integration Console, read [the Vercel Marketplace guide](packages/Common/Server/Utils/Marketplace/VERCEL_RELEASING.md).− `packages/Common/Server/Utils/Marketplace/SelfHosted`, the chart editions and their release automation in+ ### Emails load nothing from outside the installation+ An email is read wherever its reader is - on a network without the internet, behind a mail gateway that flags remote images - and every image it fetches tells whoever serves it who opened the email, and when (issue #5124: every email's header loaded its logo from res.cloudinary.com). So an email's own markup loads nothing it does not carry: an image is either inside the email - OneUptime's logo (`oneUptimeLogoUrl`, `packages/Common/Server/Utils/Mail/EmailLogo.ts`) and screenshots go out as inlin+ OneUptime Cloud is sold on AWS Marketplace, Microsoft Marketplace (Azure) and Google Cloud Marketplace through the+ enterprise module's `ee/Server/CloudMarketplace` (purchases, landing pages, webhooks, hourly usage reporting) and Sign in+ with Microsoft (core: `packages/Common/Server/Utils/MicrosoftSignIn`, built on the HTTP client and token verifier that+ stay in `packages/Common/Server/Utils/Marketplace`). Before changing that code, its settings, the marketplace usage+ prices, or anything in a seller portal, read+ OneUptime Cloud is also a native integration on the Vercel Marketplace (`ee/Server/CloudMarketplace/Vercel` and+ `ee/Server/CloudMarketplace/API`: the provider API Vercel calls, sign-in from Vercel, webhooks, monitors of connected+ projects, Vercel invoices) with its log drain in the Telemetry service, which every edition serves. Before changing that+ code, the resources' secrets or plans, or anything in Vercel's Integration Console, read+ [the Vercel Marketplace guide](packages/Common/Server/Utils/Marketplace/VERCEL_RELEASING.md).+ `ee/Server/Marketplace/Reporters`, the chart editions and their release automation in

https://oneuptime.com/llms.txt

− - [OneUptime Security Events](https://oneuptime.com/product/security-events.md): Send security events from any source to one endpoint. They are normalized to OCSF, stored beside your logs, metrics and traces, matched by Sigma detection rules, enriched against your own STIX/TAXII threat-intel feeds, and turned into alerts that page your existing on-call rotation. Open source.− - [Resellers](https://oneuptime.com/resellers.md): Buy OneUptime through a reseller in your country, or apply to become one. See our resellers by region and send us your details.+ - [OneUptime Security Events](https://oneuptime.com/product/security-events.md): SIEM and SOAR beside your logs, metrics and traces. Security events from any source are normalized to OCSF, matched by Sigma rules, correlations and threat intel, grouped into cases that OneUptime AI triages, answered by playbooks that notify, page on-call or contain, and sent on to the SIEM you already run. Open source.+ - [Air-Gapped Monitoring & Observability](https://oneuptime.com/enterprise/air-gapped.md): Run OneUptime on a network with no internet: mirror the images, bring in the signed Helm chart, license offline, and use AI on a model you run.+ - [Resellers](https://oneuptime.com/resellers.md): Buy OneUptime through a reseller in your country, or on your cloud marketplace and pay on your cloud bill. Or apply to become a reseller.

version

14.0.91 → 14.0.92

version

14.0.90 → 14.0.91

• + create_postmortem_status
• + get_postmortem_status
• + list_postmortem_statuses
• + update_postmortem_status
• + delete_postmortem_status
• + count_postmortem_statuses

version

14.0.89 → 14.0.90

version

14.0.88 → 14.0.89

version

14.0.87 → 14.0.88

version

14.0.86 → 14.0.87

version

14.0.85 → 14.0.86

version

14.0.84 → 14.0.85

version

14.0.82 → 14.0.84

version

14.0.81 → 14.0.82

version

14.0.80 → 14.0.81

version

14.0.79 → 14.0.80

version

14.0.78 → 14.0.79

version

14.0.77 → 14.0.78

version

14.0.76 → 14.0.77

version

14.0.75 → 14.0.76

version

14.0.74 → 14.0.75

version

14.0.73 → 14.0.74