<?xml version="1.0" encoding="UTF-8"?>
<!-- Generated by tools/build-blog.mjs — do not edit by hand. -->
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ZipLogger Blog</title>
    <link>https://ziplogger.ai/blog.html</link>
    <atom:link href="https://ziplogger.ai/blog/feed.xml" rel="self" type="application/rss+xml"/>
    <description>Practical guides on logging, tracing and debugging production systems.</description>
    <language>en</language>
    <lastBuildDate>Thu, 15 Oct 2026 09:00:00 GMT</lastBuildDate>
    <item>
      <title>Create GitHub, Jira or Linear issues from errors</title>
      <link>https://ziplogger.ai/blog/github-jira-linear-issues-from-errors.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/github-jira-linear-issues-from-errors.html</guid>
      <pubDate>Thu, 15 Oct 2026 09:00:00 GMT</pubDate>
      <description>Open a GitHub, Jira Cloud or Linear issue from a ZipLogger Issue, or link one you have. What gets sent, what never does, setup per tracker, and the limits.</description>
      <category>Error tracking</category>
      <category>GitHub</category>
      <category>Jira</category>
      <category>Linear</category>
    </item>
    <item>
      <title>Discord and Telegram incident alerts</title>
      <link>https://ziplogger.ai/blog/discord-telegram-incident-alerts.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/discord-telegram-incident-alerts.html</guid>
      <pubDate>Thu, 15 Oct 2026 09:00:00 GMT</pubDate>
      <description>Post ZipLogger incidents to a Discord channel or a Telegram chat as one message that is edited as the incident is acknowledged and resolved. Setup, payloads and limits.</description>
      <category>Discord</category>
      <category>Telegram</category>
      <category>Incidents</category>
      <category>Alerts</category>
    </item>
    <item>
      <title>Enterprise SSO with Microsoft Entra ID</title>
      <link>https://ziplogger.ai/blog/enterprise-sso-microsoft-entra-id.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/enterprise-sso-microsoft-entra-id.html</guid>
      <pubDate>Sat, 10 Oct 2026 09:00:00 GMT</pubDate>
      <description>Connect a ZipLogger workspace to Microsoft Entra ID, test it, require it for everyone, keep recovery codes, and know what enforcement does not reach.</description>
      <category>SSO</category>
      <category>Microsoft Entra ID</category>
      <category>OpenID Connect</category>
      <category>Security</category>
      <category>Workspaces</category>
    </item>
    <item>
      <title>Kubernetes monitoring with one Helm chart</title>
      <link>https://ziplogger.ai/blog/kubernetes-monitoring-helm-chart.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/kubernetes-monitoring-helm-chart.html</guid>
      <pubDate>Sat, 10 Oct 2026 09:00:00 GMT</pubDate>
      <description>Install one read-only Helm chart per cluster and see nodes, workloads, pods and events, plus crash loops, image pull errors and missing Secrets as incidents.</description>
      <category>Kubernetes</category>
      <category>Helm</category>
      <category>OpenTelemetry</category>
      <category>Incidents</category>
    </item>
    <item>
      <title>Metric monitors and anomaly alerts</title>
      <link>https://ziplogger.ai/blog/metric-threshold-anomaly-monitors.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/metric-threshold-anomaly-monitors.html</guid>
      <pubDate>Sat, 10 Oct 2026 09:00:00 GMT</pubDate>
      <description>Alert when any metric crosses a line or looks unusual for the time of day, with CPU per host from the OpenTelemetry Collector as a worked example.</description>
      <category>Alerts</category>
      <category>Metrics</category>
      <category>OpenTelemetry</category>
      <category>Anomaly detection</category>
      <category>Monitoring</category>
    </item>
    <item>
      <title>Parse log lines into fields and metrics</title>
      <link>https://ziplogger.ai/blog/log-pipelines-parse-logs-into-metrics.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/log-pipelines-parse-logs-into-metrics.html</guid>
      <pubDate>Sat, 10 Oct 2026 09:00:00 GMT</pubDate>
      <description>Add fields to plain-text logs as they arrive with pattern, JSON or key=value rules, then turn matching logs into a metric you can chart and alert on.</description>
      <category>Logging</category>
      <category>Log parsing</category>
      <category>Metrics</category>
      <category>Alerts</category>
    </item>
    <item>
      <title>Publish a status page for your customers</title>
      <link>https://ziplogger.ai/blog/public-status-page-for-customers.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/public-status-page-for-customers.html</guid>
      <pubDate>Sat, 10 Oct 2026 09:00:00 GMT</pubDate>
      <description>Give customers one page that shows whether your service works, with components driven by monitors, incidents, maintenance and email, Slack, webhook or SMS updates.</description>
      <category>Status page</category>
      <category>Uptime</category>
      <category>Incidents</category>
      <category>Communication</category>
    </item>
    <item>
      <title>Release health: crash-free sessions per release</title>
      <link>https://ziplogger.ai/blog/release-health-crash-free-sessions.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/release-health-crash-free-sessions.html</guid>
      <pubDate>Sat, 10 Oct 2026 09:00:00 GMT</pubDate>
      <description>See crash-free sessions, crash-free users and adoption for each release, from Sentry SDKs or ZipLogger's own SDKs, and get alerted when a release crashes more.</description>
      <category>Releases</category>
      <category>Errors</category>
      <category>Sentry</category>
      <category>JavaScript</category>
      <category>.NET</category>
    </item>
    <item>
      <title>SLOs and burn-rate alerts for your services</title>
      <link>https://ziplogger.ai/blog/service-slo-burn-rate-alerts.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/service-slo-burn-rate-alerts.html</guid>
      <pubDate>Sat, 10 Oct 2026 09:00:00 GMT</pubDate>
      <description>Set an availability or latency SLO on a service or endpoint in ZipLogger APM, watch the error budget, and page only when it burns fast.</description>
      <category>SLO</category>
      <category>APM</category>
      <category>Alerts</category>
      <category>Error budget</category>
    </item>
    <item>
      <title>Uptime monitoring: HTTP, TCP, DNS and ping checks</title>
      <link>https://ziplogger.ai/blog/uptime-monitoring-http-keyword-tcp.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/uptime-monitoring-http-keyword-tcp.html</guid>
      <pubDate>Sat, 10 Oct 2026 09:00:00 GMT</pubDate>
      <description>Check a URL, a page's text, a port, a DNS record or a ping on a schedule, page on-call only when locations agree, and get warned before a certificate or domain expires.</description>
      <category>Uptime</category>
      <category>Monitoring</category>
      <category>Alerts</category>
      <category>TLS</category>
    </item>
    <item>
      <title>Funnel drop-off: who left and what they did next</title>
      <link>https://ziplogger.ai/blog/funnel-drop-off-analysis.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/funnel-drop-off-analysis.html</guid>
      <pubDate>Sun, 04 Oct 2026 09:00:00 GMT</pubDate>
      <description>Build a saved checkout process in ZipLogger, open the exact people who dropped at a step, and see the next thing each of them did. Limits included.</description>
      <category>Product analytics</category>
      <category>Funnels</category>
      <category>Drop-off</category>
      <category>Events</category>
    </item>
    <item>
      <title>Separate staging and production logs</title>
      <link>https://ziplogger.ai/blog/separate-staging-production-logs.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/separate-staging-production-logs.html</guid>
      <pubDate>Sun, 04 Oct 2026 09:00:00 GMT</pubDate>
      <description>Keep Staging and Development telemetry apart from Production inside one ZipLogger workspace, with one ingest key per environment and alert rules that only count their own data.</description>
      <category>Environments</category>
      <category>Staging</category>
      <category>API keys</category>
      <category>Workspaces</category>
    </item>
    <item>
      <title>Use the Sentry SDK with ZipLogger</title>
      <link>https://ziplogger.ai/blog/sentry-sdk-to-ziplogger.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/sentry-sdk-to-ziplogger.html</guid>
      <pubDate>Sun, 04 Oct 2026 09:00:00 GMT</pubDate>
      <description>Keep your Sentry SDK and send its errors, traces and logs to ZipLogger by changing the DSN. Node, browser and Python setups, and what is dropped.</description>
      <category>Sentry</category>
      <category>Errors</category>
      <category>JavaScript</category>
      <category>Python</category>
      <category>Migration</category>
    </item>
    <item>
      <title>White label logging for agencies and MSPs</title>
      <link>https://ziplogger.ai/blog/white-label-workspace-branding.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/white-label-workspace-branding.html</guid>
      <pubDate>Sun, 04 Oct 2026 09:00:00 GMT</pubDate>
      <description>Put a client's name, logo, favicon and colours on their ZipLogger workspace, what white label removes on top of that, and what still says ZipLogger.</description>
      <category>White label</category>
      <category>Branding</category>
      <category>Workspaces</category>
      <category>Agencies</category>
    </item>
    <item>
      <title>AI log analysis with your own API key</title>
      <link>https://ziplogger.ai/blog/ai-root-cause-analysis.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/ai-root-cause-analysis.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>How ZipLogger's AI analysis works with your own Anthropic, OpenAI or Gemini key: what each feature does, exactly what is sent to the model, and the limits.</description>
      <category>AI</category>
      <category>LLM</category>
      <category>Root cause analysis</category>
      <category>Logs</category>
    </item>
    <item>
      <title>Alert on error logs and quiet services</title>
      <link>https://ziplogger.ai/blog/log-alert-rules.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/log-alert-rules.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Set up log-based alert rules that fire on error spikes or when a service goes quiet, send them to email or Slack, and keep them from paging for nothing.</description>
      <category>Alerts</category>
      <category>Logging</category>
      <category>Monitoring</category>
      <category>Incidents</category>
    </item>
    <item>
      <title>ASP.NET Core request metrics: p95 and throughput</title>
      <link>https://ziplogger.ai/blog/aspnet-core-metrics-apm.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/aspnet-core-metrics-apm.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Time every ASP.NET Core request with one NuGet package and see average latency, p95 and throughput per service. Real payloads, config, and limits.</description>
      <category>.NET</category>
      <category>ASP.NET Core</category>
      <category>Metrics</category>
      <category>APM</category>
    </item>
    <item>
      <title>Build an error rate dashboard in ZipLogger</title>
      <link>https://ziplogger.ai/blog/custom-dashboards.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/custom-dashboards.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Put error rate, top errors, active alerts, service health and the last deploy on one screen. Widgets, variables, filters, sharing and JSON export explained.</description>
      <category>Dashboards</category>
      <category>Observability</category>
      <category>Errors</category>
    </item>
    <item>
      <title>Centralized .NET logging with Serilog and ILogger</title>
      <link>https://ziplogger.ai/blog/serilog-dotnet-logging.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/serilog-dotnet-logging.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Send ASP.NET Core logs to ZipLogger with the Serilog sink or the ILogger provider, with structured properties you can search by user or order id.</description>
      <category>.NET</category>
      <category>Serilog</category>
      <category>ASP.NET Core</category>
      <category>Logging</category>
    </item>
    <item>
      <title>Centralized Go logging with slog and ZipLogger</title>
      <link>https://ziplogger.ai/blog/go-logging.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/go-logging.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>A log/slog handler that sends Go logs to the cloud. The real module path, how attributes become fields, errors, and what Close does.</description>
      <category>Go</category>
      <category>slog</category>
      <category>Logging</category>
    </item>
    <item>
      <title>Centralized Java logging with ZipLogger</title>
      <link>https://ziplogger.ai/blog/java-logging.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/java-logging.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Send Java logs to the cloud with the ZipLogger java.util.logging handler or its client. Maven and Gradle setup, fields, stack traces, shutdown.</description>
      <category>Java</category>
      <category>Logging</category>
    </item>
    <item>
      <title>Centralized Node.js logging with ZipLogger</title>
      <link>https://ziplogger.ai/blog/node-js-logging.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/node-js-logging.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Send Node.js logs to the cloud through Pino, Winston or a plain client. Setup, the JSON each line becomes, errors, and flushing on shutdown.</description>
      <category>Node.js</category>
      <category>Logging</category>
      <category>Pino</category>
      <category>Winston</category>
    </item>
    <item>
      <title>Centralized Python logging with ZipLogger</title>
      <link>https://ziplogger.ai/blog/python-logging.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/python-logging.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Send Python logs to the cloud with the standard logging module and one handler. Setup, Django config, searchable extra fields and tracebacks.</description>
      <category>Python</category>
      <category>Logging</category>
      <category>Django</category>
    </item>
    <item>
      <title>Cohort retention: how the numbers are counted</title>
      <link>https://ziplogger.ai/blog/retention-cohorts.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/retention-cohorts.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>What a ZipLogger retention chart counts, cell by cell: who enters a cohort, what counts as coming back, calendar buckets, and how saved cohorts narrow it.</description>
      <category>Product analytics</category>
      <category>Retention</category>
      <category>Cohorts</category>
    </item>
    <item>
      <title>Cron job monitoring: alert when a job doesn't run</title>
      <link>https://ziplogger.ai/blog/cron-job-monitoring.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/cron-job-monitoring.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Use a heartbeat to find out when a cron job stops running, fails or hangs: a plain ping URL, cron schedules with time zones, Sentry check-ins, and curl and .NET samples.</description>
      <category>Cron</category>
      <category>Monitoring</category>
      <category>Alerts</category>
      <category>.NET</category>
    </item>
    <item>
      <title>Find the commit that broke production</title>
      <link>https://ziplogger.ai/blog/find-commit-that-broke-production.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/find-commit-that-broke-production.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>How to trace a production error back to the commit that caused it, from stack trace to git blame to a short list of suspects, and how ZipLogger does it for you.</description>
      <category>Git</category>
      <category>Debugging</category>
      <category>Regression detection</category>
    </item>
    <item>
      <title>Follow one error across logs, traces and events</title>
      <link>https://ziplogger.ai/blog/investigate-error-across-signals.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/investigate-error-across-signals.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Correlate logs, traces and product events by trace id and session id on ZipLogger's Investigate page, and what your apps must send for the join to work.</description>
      <category>Tracing</category>
      <category>Logs</category>
      <category>Correlation</category>
      <category>OpenTelemetry</category>
    </item>
    <item>
      <title>Funnel analysis: sequential vs presence funnels</title>
      <link>https://ziplogger.ai/blog/funnel-analysis.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/funnel-analysis.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Build a conversion funnel from tracked events, see why sequential and presence modes give different numbers, and trace a drop-off to the errors behind it.</description>
      <category>Product analytics</category>
      <category>Funnels</category>
      <category>Events</category>
    </item>
    <item>
      <title>Identify anonymous users and follow their journey</title>
      <link>https://ziplogger.ai/blog/user-journeys-profiles.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/user-journeys-profiles.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Link a visitor's anonymous events to their account with identify(), then read their profile and session timeline with the errors and replay beside it.</description>
      <category>Product analytics</category>
      <category>Identity</category>
      <category>Sessions</category>
    </item>
    <item>
      <title>JavaScript and React error tracking</title>
      <link>https://ziplogger.ai/blog/javascript-error-tracking.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/javascript-error-tracking.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Catch uncaught JavaScript errors, promise rejections and React render errors with @ziplogger/browser. Real payloads, plus what it does not do.</description>
      <category>JavaScript</category>
      <category>React</category>
      <category>Errors</category>
      <category>Browser</category>
    </item>
    <item>
      <title>Log pattern clustering, explained with real output</title>
      <link>https://ziplogger.ai/blog/log-pattern-clustering.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/log-pattern-clustering.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>How Drain-style log pattern detection groups similar log messages into templates, where it gets things wrong, and how to use patterns in ZipLogger.</description>
      <category>Logging</category>
      <category>Log patterns</category>
      <category>Drain</category>
    </item>
    <item>
      <title>Microsoft Teams incident alerts with actions</title>
      <link>https://ziplogger.ai/blog/microsoft-teams-incident-alerts.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/microsoft-teams-incident-alerts.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Get ZipLogger incident cards in a Teams channel or chat, and acknowledge, assign or resolve them from the card. Setup, account linking and limits.</description>
      <category>Microsoft Teams</category>
      <category>Incidents</category>
      <category>Alerts</category>
      <category>On-call</category>
    </item>
    <item>
      <title>Move off Mixpanel without rewriting tracking</title>
      <link>https://ziplogger.ai/blog/mixpanel-sdk-migration.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/mixpanel-sdk-migration.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Point mixpanel-browser or the Mixpanel Node library at ZipLogger with one host setting. What carries over, what does not, and the native alternative.</description>
      <category>Mixpanel</category>
      <category>Product analytics</category>
      <category>JavaScript</category>
    </item>
    <item>
      <title>On-call schedules and escalation policies</title>
      <link>https://ziplogger.ai/blog/on-call-schedules-escalation.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/on-call-schedules-escalation.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Set up on-call teams, rotations with primary and secondary layers, overrides, a repeating escalation policy, calendar subscriptions and postmortems in ZipLogger.</description>
      <category>On-call</category>
      <category>Incidents</category>
      <category>Escalation</category>
      <category>Alerts</category>
    </item>
    <item>
      <title>Query and export logs over HTTP</title>
      <link>https://ziplogger.ai/blog/query-logs-api.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/query-logs-api.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Read logs out of ZipLogger from a script or CI job: the REST search API with cursor paging, the read-key Loki endpoint, real requests and their limits.</description>
      <category>API</category>
      <category>Logs</category>
      <category>Export</category>
      <category>curl</category>
      <category>Python</category>
    </item>
    <item>
      <title>Query production logs from Claude Code or Cursor</title>
      <link>https://ziplogger.ai/blog/mcp-query-logs-from-ai-assistant.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/mcp-query-logs-from-ai-assistant.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Connect Claude Code, Cursor or any MCP client to ZipLogger's MCP server so your AI assistant can read logs, error patterns, traces and git regressions.</description>
      <category>MCP</category>
      <category>Claude Code</category>
      <category>Cursor</category>
      <category>AI</category>
    </item>
    <item>
      <title>Query ZipLogger from Grafana, no plugin</title>
      <link>https://ziplogger.ai/blog/grafana-data-source.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/grafana-data-source.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Point Grafana's built-in Loki, Prometheus and Tempo data sources at ZipLogger. The real URLs, auth, and exactly which LogQL and PromQL queries work.</description>
      <category>Grafana</category>
      <category>Loki</category>
      <category>Prometheus</category>
      <category>Tempo</category>
      <category>Logs</category>
    </item>
    <item>
      <title>Route CloudWatch and Datadog alerts to on-call</title>
      <link>https://ziplogger.ai/blog/route-cloudwatch-datadog-alerts.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/route-cloudwatch-datadog-alerts.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Send CloudWatch, Datadog, Alertmanager and other alerts into ZipLogger incidents by webhook, with dedup, auto-resolve and optional hand-off to PagerDuty.</description>
      <category>Incidents</category>
      <category>CloudWatch</category>
      <category>Prometheus</category>
      <category>Datadog</category>
      <category>Webhooks</category>
    </item>
    <item>
      <title>Send logs over HTTP with curl</title>
      <link>https://ziplogger.ai/blog/http-api-log-ingestion.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/http-api-log-ingestion.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Send logs from shell scripts, CI jobs or any language with one HTTP POST. Real curl samples, body formats, severity rules, limits and responses.</description>
      <category>HTTP API</category>
      <category>curl</category>
      <category>Logging</category>
      <category>CI</category>
    </item>
    <item>
      <title>Send OpenTelemetry traces over OTLP/HTTP</title>
      <link>https://ziplogger.ai/blog/opentelemetry-otlp-traces.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/opentelemetry-otlp-traces.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Point any OpenTelemetry SDK or Collector at ZipLogger over OTLP/HTTP. The exact endpoints, the auth header, .NET and Node.js setups, and what is not supported.</description>
      <category>OpenTelemetry</category>
      <category>OTLP</category>
      <category>Tracing</category>
    </item>
    <item>
      <title>Session replay without recording passwords</title>
      <link>https://ziplogger.ai/blog/session-replay-privacy-masking.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/session-replay-privacy-masking.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>How ZipLogger's session replay masks passwords, card fields and typed input in the browser before upload, and how to mask or block anything else.</description>
      <category>Session replay</category>
      <category>Privacy</category>
      <category>JavaScript</category>
    </item>
    <item>
      <title>Ship logs with Fluent Bit or Vector</title>
      <link>https://ziplogger.ai/blog/fluent-bit-vector-log-shipping.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/fluent-bit-vector-log-shipping.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Send log files and Docker or Kubernetes container output to ZipLogger with Fluent Bit's http output or Vector's http sink. Configs and field rules.</description>
      <category>Fluent Bit</category>
      <category>Vector</category>
      <category>Docker</category>
      <category>Kubernetes</category>
      <category>Logging</category>
    </item>
    <item>
      <title>Slack incident alerts you can acknowledge</title>
      <link>https://ziplogger.ai/blog/slack-incident-alerts.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/slack-incident-alerts.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Post ZipLogger incidents to a Slack channel as one message that updates in place, with Acknowledge, Assign to me and Resolve buttons that act as the person who clicked.</description>
      <category>Slack</category>
      <category>Incidents</category>
      <category>Alerts</category>
      <category>On-call</category>
    </item>
    <item>
      <title>SMS and voice call paging for incidents</title>
      <link>https://ziplogger.ai/blog/sms-voice-paging.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/sms-voice-paging.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Page on-call engineers by SMS and phone call in ZipLogger, and let them acknowledge by replying or pressing 1. Built-in sender or your own Twilio or Telnyx.</description>
      <category>On-call</category>
      <category>SMS</category>
      <category>Twilio</category>
      <category>Incidents</category>
    </item>
    <item>
      <title>Synthetic monitoring: replay a real user journey</title>
      <link>https://ziplogger.ai/blog/synthetic-browser-monitoring.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/synthetic-browser-monitoring.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Record a sign-in or checkout once in a real browser, replay it on a schedule in Chromium, and get the failing step with a screenshot, console errors and failed requests.</description>
      <category>Synthetic monitoring</category>
      <category>Playwright</category>
      <category>Uptime</category>
    </item>
    <item>
      <title>Trace a click from the browser to the backend</title>
      <link>https://ziplogger.ai/blog/browser-to-backend-tracing.html</link>
      <guid isPermaLink="true">https://ziplogger.ai/blog/browser-to-backend-tracing.html</guid>
      <pubDate>Tue, 29 Sep 2026 09:00:00 GMT</pubDate>
      <description>Send a W3C traceparent header from the browser so your backend's OpenTelemetry spans join the same trace. CORS setup and real output included.</description>
      <category>Tracing</category>
      <category>OpenTelemetry</category>
      <category>JavaScript</category>
      <category>Browser</category>
    </item>
  </channel>
</rss>
