<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Insights | ARKTOS GROUP</title><link>https://arktoscompany.com/blog/en/</link><description>ARKTOS GROUP articles on observability, automation, agentic AI, data, cloud, service management, operating model and cybersecurity.</description><language>en</language><lastBuildDate>Tue, 22 Sep 2026 09:00:00 +0000</lastBuildDate><atom:link href="https://arktoscompany.com/blog/en/feed.xml" rel="self" type="application/rss+xml"/>
<item><title>The CIO and AI: from managing technology to orchestrating capabilities</title><link>https://arktoscompany.com/blog/en/cio-era-ia</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/cio-era-ia</guid><pubDate>Tue, 22 Sep 2026 09:00:00 +0000</pubDate><category>Operating model</category><description>With AI, the CIO&#x27;s role shifts from managing infrastructure and projects to orchestrating data, platforms, integrations, agents, vendors and talent. Responsibilities, decisions that stay with the CIO, board reporting and metrics.</description></item>
<item><title>Human in the loop: autonomy levels for agents in production</title><link>https://arktoscompany.com/blog/en/niveles-autonomia-agentes</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/niveles-autonomia-agentes</guid><pubDate>Tue, 16 Jun 2026 09:00:00 +0000</pubDate><category>Agentic AI</category><description>A four-level scale for deciding how much autonomy to give an AI agent in operations, with criteria for moving up a level, least privilege, a kill switch and an audit trail.</description></item>
<item><title>Modernizing the service desk: requests, knowledge and agents</title><link>https://arktoscompany.com/blog/en/modernizar-service-desk</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/modernizar-service-desk</guid><pubDate>Tue, 21 Apr 2026 09:00:00 +0000</pubDate><category>Service management</category><description>How to modernize the service desk beyond incidents: a request catalog, knowledge with KCS, self-service, automated fulfillment and AI agents that escalate with context, plus metrics to know whether it works.</description></item>
<item><title>Living documentation: agents that keep the CMDB and diagrams current</title><link>https://arktoscompany.com/blog/en/documentacion-viva-agentes</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/documentacion-viva-agentes</guid><pubDate>Tue, 10 Mar 2026 09:00:00 +0000</pubDate><category>Agentic AI</category><description>The CMDB and architecture diagrams start aging the day they are published. How to use agents that detect drift and propose updates for a person to review and approve.</description></item>
<item><title>Integration first: agents are only as good as their APIs</title><link>https://arktoscompany.com/blog/en/integracion-primero-agentes</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/integracion-primero-agentes</guid><pubDate>Tue, 27 Jan 2026 09:00:00 +0000</pubDate><category>Agentic AI</category><description>An AI agent can only do what its tools allow. What makes an API ready for agents, and how to prioritize which integrations to build first.</description></item>
<item><title>AI training by role, not one course for everyone</title><link>https://arktoscompany.com/blog/en/formacion-ia-por-roles</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/formacion-ia-por-roles</guid><pubDate>Tue, 18 Nov 2025 09:00:00 +0000</pubDate><category>Data and AI</category><description>A single AI course for the whole organization leaves gaps exactly where the risk is. How to design role-based training, with its own content, depth, format and measurement for each profile.</description></item>
<item><title>Monitoring agents: from fixed thresholds to context-aware detection</title><link>https://arktoscompany.com/blog/en/agentes-de-monitoreo</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/agentes-de-monitoreo</guid><pubDate>Tue, 07 Oct 2025 09:00:00 +0000</pubDate><category>Agentic AI</category><description>Why fixed thresholds fall short, how to use baselines, signal correlation and change context, and how an agent can summarize an anomaly without multiplying false positives.</description></item>
<item><title>FinOps for AI: the cost of models and agents in production</title><link>https://arktoscompany.com/blog/en/finops-para-ia</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/finops-para-ia</guid><pubDate>Tue, 23 Sep 2025 09:00:00 +0000</pubDate><category>Cloud</category><description>What makes up the cost of an AI agent, how to measure it per conversation or per resolved ticket, how to allocate it and which levers reduce it without sacrificing quality.</description></item>
<item><title>Governing MCP agents: identity, permissions and logging</title><link>https://arktoscompany.com/blog/en/gobernar-agentes-mcp</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/gobernar-agentes-mcp</guid><pubDate>Tue, 19 Aug 2025 09:00:00 +0000</pubDate><category>Agentic AI</category><description>MCP standardizes how an agent uses tools, but it does not decide who can use what. How to govern identity, per-tool permissions, consent, logging and the inventory of MCP servers.</description></item>
<item><title>Continuous rightsizing: why cloud savings evaporate</title><link>https://arktoscompany.com/blog/en/rightsizing-continuo-agentes</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/rightsizing-continuo-agentes</guid><pubDate>Tue, 24 Jun 2025 09:00:00 +0000</pubDate><category>Agentic AI</category><description>Rightsizing resources once saves money for a short while. Why savings decay and how an agent proposes changes backed by evidence, an approval flow and a rollback plan.</description></item>
<item><title>AI-ready data before the first pilot</title><link>https://arktoscompany.com/blog/en/datos-listos-para-ia</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/datos-listos-para-ia</guid><pubDate>Tue, 20 May 2025 09:00:00 +0000</pubDate><category>Data and AI</category><description>Before the first AI pilot, put four foundations in place: a catalog, measured quality, lineage and clear permissions. A practical approach for regulated organizations, with a checklist to decide whether you are ready.</description></item>
<item><title>Security guardrails for AI agents, layer by layer</title><link>https://arktoscompany.com/blog/en/barreras-seguridad-agentes-ia</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/barreras-seguridad-agentes-ia</guid><pubDate>Tue, 08 Apr 2025 09:00:00 +0000</pubDate><category>Agentic AI</category><description>Defense in depth for AI agents: guardrails at the input, the model, the tools and the output, with monitoring, against prompt injection, tool misuse and data leakage.</description></item>
<item><title>The CISO and AI: new risks, familiar controls</title><link>https://arktoscompany.com/blog/en/ciso-frente-a-ia</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/ciso-frente-a-ia</guid><pubDate>Tue, 11 Mar 2025 09:00:00 +0000</pubDate><category>Cybersecurity and governance</category><description>Which generative AI risks are genuinely new and how to place them in the six functions of NIST CSF 2.0, using controls your security program already runs.</description></item>
<item><title>DORA and ICT providers: what changes for those operating in Spain</title><link>https://arktoscompany.com/blog/en/dora-proveedores-tic</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/dora-proveedores-tic</guid><pubDate>Tue, 25 Feb 2025 09:00:00 +0000</pubDate><category>Cybersecurity and governance</category><description>DORA has applied to EU financial entities since January 2025. What they will ask of their IT providers, and how to prepare if you deliver services in Spain.</description></item>
<item><title>Incident triage with agents: design, controls and traceability</title><link>https://arktoscompany.com/blog/en/triaje-incidentes-con-agentes</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/triaje-incidentes-con-agentes</guid><pubDate>Tue, 21 Jan 2025 09:00:00 +0000</pubDate><category>Agentic AI</category><description>A reference flow for an AI agent that supports incident triage: start read only, log every decision, measure its accuracy against analysts and keep invented causes under control.</description></item>
<item><title>ISO/IEC 42001 in practice: governing AI before scaling it</title><link>https://arktoscompany.com/blog/en/iso-42001-en-la-practica</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/iso-42001-en-la-practica</guid><pubDate>Tue, 22 Oct 2024 09:00:00 +0000</pubDate><category>Cybersecurity and governance</category><description>ISO/IEC 42001 defines a management system for AI. Why it matters if you deploy agents, how it fits with ISO/IEC 27001 and the NIST AI RMF, and a roadmap to get started.</description></item>
<item><title>AI agents in IT operations: where they work today</title><link>https://arktoscompany.com/blog/en/agentes-ia-operacion-ti</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/agentes-ia-operacion-ti</guid><pubDate>Tue, 17 Sep 2024 09:00:00 +0000</pubDate><category>Agentic AI</category><description>What an AI agent is, which operations tasks it adds value to today, where it is still risky, and what you need in place before putting it to work.</description></item>
<item><title>Organizing cybersecurity: centralized, federated or product-aligned</title><link>https://arktoscompany.com/blog/en/organizar-area-ciberseguridad</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/organizar-area-ciberseguridad</guid><pubDate>Tue, 23 Jul 2024 09:00:00 +0000</pubDate><category>Cybersecurity and governance</category><description>Three models for organizing the cybersecurity function, with their strengths, risks and when each one fits, what always stays central, and how security champions and NIST CSF 2.0 roles fit in.</description></item>
<item><title>NIST CSF 2.0: the Govern function explained for the board</title><link>https://arktoscompany.com/blog/en/nist-csf-2-funcion-gobernar</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/nist-csf-2-funcion-gobernar</guid><pubDate>Tue, 07 May 2024 09:00:00 +0000</pubDate><category>Cybersecurity and governance</category><description>Govern is the main addition in NIST CSF 2.0. What it covers, how to present cyber risk to the board, and how to use profiles and tiers to make decisions.</description></item>
<item><title>Platform engineering: internal platforms that let teams operate on their own</title><link>https://arktoscompany.com/blog/en/platform-engineering-plataformas-internas</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/platform-engineering-plataformas-internas</guid><pubDate>Tue, 09 Apr 2024 09:00:00 +0000</pubDate><category>Operating model</category><description>An internal platform run as a product, with golden paths and self-service, lightens the load on development teams. Minimum capabilities, the platform team, adoption metrics and common mistakes.</description></item>
<item><title>Cloud repatriation: when it pays and when it doesn&#x27;t</title><link>https://arktoscompany.com/blog/en/repatriacion-de-cargas</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/repatriacion-de-cargas</guid><pubDate>Tue, 19 Mar 2024 09:00:00 +0000</pubDate><category>Cloud</category><description>A neutral way to decide whether a workload should move back to your own infrastructure: predictability, dependence on managed services, total cost, latency, sovereignty and execution risk.</description></item>
<item><title>How to choose an APM platform without vendor lock-in</title><link>https://arktoscompany.com/blog/en/elegir-plataforma-apm</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/elegir-plataforma-apm</guid><pubDate>Tue, 27 Feb 2024 09:00:00 +0000</pubDate><category>Observability</category><description>Vendor neutral criteria to evaluate an APM platform: coverage, OpenTelemetry support, cost, root cause, access control, data residency and ITSM integration, without getting locked into one tool.</description></item>
<item><title>From runbook to playbook: automating auditable procedures</title><link>https://arktoscompany.com/blog/en/del-runbook-al-playbook</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/del-runbook-al-playbook</guid><pubDate>Tue, 16 Jan 2024 09:00:00 +0000</pubDate><category>Automation</category><description>How to turn a manual procedure into an auditable playbook: choose the candidate with clear criteria, translate each step into validated tasks, handle failures and keep human approval where it adds control.</description></item>
<item><title>Edge observability: branches, ATMs and devices</title><link>https://arktoscompany.com/blog/en/observabilidad-en-el-borde</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/observabilidad-en-el-borde</guid><pubDate>Tue, 14 Nov 2023 09:00:00 +0000</pubDate><category>Observability</category><description>Branches, ATMs and devices generate telemetry far from the cloud, over links that fail. How to design the local collector, buffer, sampling, time, identity and inventory so you keep visibility.</description></item>
<item><title>Automated remediation: from event to playbook with Event-Driven Ansible</title><link>https://arktoscompany.com/blog/en/remediacion-automatica-event-driven-ansible</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/remediacion-automatica-event-driven-ansible</guid><pubDate>Tue, 10 Oct 2023 09:00:00 +0000</pubDate><category>Automation</category><description>Event-Driven Ansible connects alerts and webhooks to playbooks. With clear limits it resolves repetitive incidents in minutes; without them, it multiplies errors. How to design rules, guardrails, approvals and ticket closure.</description></item>
<item><title>Observability from the code: a practical OpenTelemetry guide</title><link>https://arktoscompany.com/blog/en/instrumentar-codigo-opentelemetry</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/instrumentar-codigo-opentelemetry</guid><pubDate>Tue, 22 Aug 2023 09:00:00 +0000</pubDate><category>Observability</category><description>Structured logs with trace_id, context propagated across services and queues, custom spans and business metrics: how to instrument your code with OpenTelemetry and what to avoid.</description></item>
<item><title>From NOC to command center: operating services, not devices</title><link>https://arktoscompany.com/blog/en/del-noc-al-centro-de-comando</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/del-noc-al-centro-de-comando</guid><pubDate>Tue, 18 Apr 2023 09:00:00 +0000</pubDate><category>Observability</category><description>A network-centric NOC sees healthy devices while customers cannot get anything done. A 24×7 command center watches services end to end and takes ownership of them.</description></item>
<item><title>How to measure the value of an automation before building it</title><link>https://arktoscompany.com/blog/en/medir-valor-automatizacion</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/medir-valor-automatizacion</guid><pubDate>Tue, 14 Feb 2023 09:00:00 +0000</pubDate><category>Automation</category><description>Hours saved are only part of the value. A rubric to score effort, risk, customer impact and compliance from 1 to 5 before investing in building.</description></item>
<item><title>Ansible in regulated environments: idempotency, inventories and change control</title><link>https://arktoscompany.com/blog/en/ansible-operaciones-reguladas</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/ansible-operaciones-reguladas</guid><pubDate>Tue, 24 Jan 2023 09:00:00 +0000</pubDate><category>Automation</category><description>How to use Ansible in regulated organizations so every run is repeatable and traceable: idempotency as evidence, per-environment inventories, secrets kept out of the repository and changes tied to their record.</description></item>
<item><title>Cloud resilience beyond high availability</title><link>https://arktoscompany.com/blog/en/resiliencia-nube-mas-alla-alta-disponibilidad</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/resiliencia-nube-mas-alla-alta-disponibilidad</guid><pubDate>Tue, 06 Dec 2022 09:00:00 +0000</pubDate><category>Cloud</category><description>Deploying across zones is not enough. How to cover regional failures and hidden dependencies, set RTO and RPO per service, choose a recovery pattern and actually test it.</description></item>
<item><title>Business observability: measuring the banking customer journey</title><link>https://arktoscompany.com/blog/en/observabilidad-de-negocio-banca</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/observabilidad-de-negocio-banca</guid><pubDate>Tue, 18 Oct 2022 09:00:00 +0000</pubDate><category>Observability</category><description>Instrumenting login, transfers, card payments and onboarding as business transactions reveals partial degradation before customers call, without putting personal data in your telemetry.</description></item>
<item><title>Data observability: freshness, volume, schema and lineage</title><link>https://arktoscompany.com/blog/en/observabilidad-de-datos</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/observabilidad-de-datos</guid><pubDate>Tue, 13 Sep 2022 09:00:00 +0000</pubDate><category>Data and AI</category><description>A data pipeline fails silently: the table exists, but it arrives late, incomplete or with a different schema. How to measure freshness, volume, schema, distribution and lineage, and manage them as a service with SLOs.</description></item>
<item><title>An observable platform is not an observable application</title><link>https://arktoscompany.com/blog/en/plataforma-observable-no-alcanza</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/plataforma-observable-no-alcanza</guid><pubDate>Tue, 12 Jul 2022 09:00:00 +0000</pubDate><category>Observability</category><description>An APM platform sees infrastructure, dependencies and most calls. It cannot see what your business means. Finding root cause fast requires software written to be observable.</description></item>
<item><title>Change enablement without bureaucracy: standard change models</title><link>https://arktoscompany.com/blog/en/habilitacion-de-cambios</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/habilitacion-de-cambios</guid><pubDate>Tue, 10 May 2022 09:00:00 +0000</pubDate><category>Service management</category><description>A board that reviews everything the same way slows operations without reducing failures. How to use standard, normal and emergency changes, approve by risk and automate so repetitive work is pre-approved.</description></item>
<item><title>Ansible at scale: roles, collections, testing and pipelines</title><link>https://arktoscompany.com/blog/en/ansible-a-escala</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/ansible-a-escala</guid><pubDate>Tue, 15 Mar 2022 09:00:00 +0000</pubDate><category>Automation</category><description>When automation grows from a few playbooks to several teams, it needs software discipline: an organized repository, roles and collections, testing with ansible-lint and Molecule, and controlled promotion between environments.</description></item>
<item><title>Logs, metrics and traces: what each signal answers</title><link>https://arktoscompany.com/blog/en/logs-metricas-trazas</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/logs-metricas-trazas</guid><pubDate>Tue, 18 Jan 2022 09:00:00 +0000</pubDate><category>Observability</category><description>Each telemetry signal answers a different question at a different cost. Understanding what each one provides and how they correlate is what turns scattered data into diagnosis.</description></item>
<item><title>Cloud governance in financial services: responsibilities and minimum controls</title><link>https://arktoscompany.com/blog/en/gobierno-nube-servicios-financieros</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/gobierno-nube-servicios-financieros</guid><pubDate>Tue, 16 Nov 2021 09:00:00 +0000</pubDate><category>Cloud</category><description>What a financial institution delegates and what it keeps under each cloud service model, and the minimum set of controls it should have in place before moving its first workload.</description></item>
<item><title>AIOps without the hype: the data it needs and the first year</title><link>https://arktoscompany.com/blog/en/aiops-sin-humo</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/aiops-sin-humo</guid><pubDate>Tue, 26 Oct 2021 09:00:00 +0000</pubDate><category>Observability</category><description>AIOps is not a magic box: it correlates events, reduces noise and detects anomalies when it gets clean data. What data to prepare first and what results to expect quarter by quarter in year one.</description></item>
<item><title>Burnout in security teams: a manageable operational risk</title><link>https://arktoscompany.com/blog/en/agotamiento-equipos-seguridad</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/agotamiento-equipos-seguridad</guid><pubDate>Tue, 24 Aug 2021 09:00:00 +0000</pubDate><category>Cybersecurity and governance</category><description>Burnout in a security team is not just a personal matter: it degrades detection and puts knowledge at risk. Operational causes, workload indicators and controls to manage it.</description></item>
<item><title>Root cause in minutes: a method for distributed systems</title><link>https://arktoscompany.com/blog/en/causa-raiz-sistemas-distribuidos</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/causa-raiz-sistemas-distribuidos</guid><pubDate>Tue, 15 Jun 2021 09:00:00 +0000</pubDate><category>Observability</category><description>A five-step triage method to find the root cause in distributed systems: scope the impact, follow the trace, correlate with changes, check saturation and validate hypotheses.</description></item>
<item><title>Problem management: the practice that actually reduces incidents</title><link>https://arktoscompany.com/blog/en/gestion-de-problemas</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/gestion-de-problemas</guid><pubDate>Tue, 13 Apr 2021 09:00:00 +0000</pubDate><category>Service management</category><description>Restoring service is not enough if the same incident returns every week. How to run reactive and proactive problem management, known errors, root cause techniques and metrics, supported by observability.</description></item>
<item><title>Governing the automation backlog: roles, cadence and metrics</title><link>https://arktoscompany.com/blog/en/gobernar-backlog-automatizacion</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/gobernar-backlog-automatizacion</guid><pubDate>Tue, 23 Feb 2021 09:00:00 +0000</pubDate><category>Automation</category><description>Prioritizing once is not enough. An intake sheet, three clear roles, quarterly re-scoring and four metrics keep the automation backlog in order and accountable.</description></item>
<item><title>Real complexity: the factors that sink an automation</title><link>https://arktoscompany.com/blog/en/medir-complejidad-automatizacion</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/medir-complejidad-automatizacion</guid><pubDate>Tue, 22 Sep 2020 09:00:00 +0000</pubDate><category>Automation</category><description>Automations rarely fail because of the tool. They fail because of exceptions, access and dependencies nobody measured. A rubric to score complexity and how to redesign what should not be automated yet.</description></item>
<item><title>Value × Complexity: how we prioritize what to automate</title><link>https://arktoscompany.com/blog/en/priorizar-automatizacion-valor-complejidad</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/priorizar-automatizacion-valor-complejidad</guid><pubDate>Tue, 16 Jun 2020 09:00:00 +0000</pubDate><category>Automation</category><description>An automation backlog ordered by whoever pushes hardest wastes capacity. Here is how our Value × Complexity framework works: define, classify and prioritize with two axes and four quadrants.</description></item>
<item><title>The product operating model: budget, teams and metrics</title><link>https://arktoscompany.com/blog/en/modelo-operativo-producto</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/modelo-operativo-producto</guid><pubDate>Tue, 11 Feb 2020 09:00:00 +0000</pubDate><category>Operating model</category><description>Moving from temporary projects to products with stable teams changes how IT is funded, how teams are organized and what gets measured. What changes and how it coexists with ITIL and the PMO.</description></item>
<item><title>PMO and VMO as a service: governing projects and vendors with metrics</title><link>https://arktoscompany.com/blog/en/pmo-vmo-como-servicio</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/pmo-vmo-como-servicio</guid><pubDate>Tue, 29 Oct 2019 09:00:00 +0000</pubDate><category>Service management</category><description>What a PMO and a VMO do, when it makes sense to run them as a service, and which metrics, SLAs and governance cadence you need to control your portfolio and your vendors.</description></item>
<item><title>SLAs that measure what the business cares about</title><link>https://arktoscompany.com/blog/en/sla-que-importan</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/sla-que-importan</guid><pubDate>Tue, 20 Aug 2019 09:00:00 +0000</pubDate><category>Service management</category><description>Green indicators and frustrated users: the watermelon effect. How to tell SLAs, OLAs and SLOs apart, define measures from the user journey and add experience metrics to availability.</description></item>
<item><title>The five ITIL 4 practices to start with</title><link>https://arktoscompany.com/blog/en/practicas-itil-fundacionales</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/practicas-itil-fundacionales</guid><pubDate>Tue, 14 May 2019 09:00:00 +0000</pubDate><category>Service management</category><description>ITIL 4 describes 34 practices, but a solid operation starts with five and a service desk. The purpose, minimum viable process, key metric and common mistake of each, plus a suggested sequence.</description></item>
<item><title>From administrators to SRE: a staged transition</title><link>https://arktoscompany.com/blog/en/de-administradores-a-sre</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/de-administradores-a-sre</guid><pubDate>Tue, 12 Mar 2019 09:00:00 +0000</pubDate><category>Operating model</category><description>How to move from a systems administration team to an SRE model without breaking operations: measure toil, set SLOs, fix on-call, automate and build new roles.</description></item>
<item><title>Alerts without fatigue: SLOs and error budgets in practice</title><link>https://arktoscompany.com/blog/en/alertas-sin-fatiga-slo</link><guid isPermaLink="true">https://arktoscompany.com/blog/en/alertas-sin-fatiga-slo</guid><pubDate>Tue, 06 Nov 2018 09:00:00 +0000</pubDate><category>Observability</category><description>How to define SLIs, SLOs and error budgets, alert on symptoms, and use multiwindow burn rate alerts so you only page people when customers are actually at risk.</description></item>
</channel>
</rss>
