[{"id":625864,"date":"2026-09-04T08:00:00","date_gmt":"2026-09-04T13:00:00","guid":{"rendered":"https:\/\/www.logicmonitor.com\/?p=625864"},"modified":"2026-09-02T15:22:18","modified_gmt":"2026-09-02T20:22:18","slug":"edwin-ai-operational-resilience-itops","status":"publish","type":"post","link":"https:\/\/www.logicmonitor.com\/fr\/blog\/edwin-ai-operational-resilience-itops","title":{"rendered":"Edwin AI et les nouvelles exigences de r\u00e9silience op\u00e9rationnelle en ITOps"},"content":{"rendered":"<?xml encoding=\"UTF-8\"><p class=\"wp-block-paragraph\">Operational resilience breaks down in the time it takes to understand an incident well enough to act. Most ITOps teams can detect that something is wrong. The delay comes later, when engineers have to sort through noisy alerts, disconnected tools, and unclear service dependencies to determine cause, scope, and next steps.<\/p><p class=\"wp-block-paragraph\">That delay carries real cost in hybrid environments, where a change in one layer can surface somewhere else and spread before the incident is contained.&nbsp;<\/p><p class=\"wp-block-paragraph\"><a href=\"https:\/\/www.logicmonitor.com\/fr\/edwin-ai\">Edwin AI<\/a> reduces that exposure by correlating signals across domains, applying topology and change context, and supporting governed action. The result is faster root cause isolation, tighter incident response, and fewer decisions made under incomplete information.<\/p><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50 rtc-text-content--no-top-pad\">\n      <span class=\"head-icon\"><svg class=\"\" width=\"50px\" height=\"50px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-light-book-open\"><\/use>\n    <\/svg><\/span>\n  \n  <div class=\"rtc-text-content__wrapper\">\n    \n          <div class=\"rtc-text-content__body fs-sm-text-md fs-md-text-lg fs-lg-text-lg text-core-blue-900 headline-is-quote\">\n        <p>Edwin AI improves operational resilience by helping ITOps teams detect issues earlier, isolate root cause faster, reduce alert noise, and act with more control across hybrid environments.<\/p>\n      <\/div>\n    \n                  <ul class=\"rtc-text-content__bullet-list\">\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p><span style=\"font-weight: 400\">Modern resilience failures are rarely isolated to one domain, which is why Edwin AI correlates signals across infrastructure, cloud, applications, and services instead of treating alerts as separate events.<\/span><\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p><span style=\"font-weight: 400\">Edwin AI reduces the time lost to manual triage by combining topology, change history, and contextual reasoning into a clearer picture of cause, impact, and next best action.<\/span><\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p><span style=\"font-weight: 400\">Governed automation, incident routing, and early warning insights help teams respond faster without giving up control, auditability, or operational safety.<\/span><\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                  <\/ul>\n      \n      \n            <\/div>\n<\/div><h2 id=\"h-operational-resilience-is-harder-to-maintain-in-itops-today\" class=\"wp-block-heading\">Operational Resilience Is Harder to Maintain in ITOps Today<\/h2><p class=\"wp-block-paragraph\">Operational resilience in ITOps means detecting problems before users notice them, isolating which services are affected and why, coordinating a response without losing time to miscommunication, and fixing the underlying cause rather than the symptom.&nbsp;<\/p><p class=\"wp-block-paragraph\">When any of those break down, it <a href=\"https:\/\/www.logicmonitor.com\/blog\/ai-automation-cuts-operational-waste-incident-investigation\">immediately<\/a> impacts uptime, customer experience, and revenue. A 30-minute outage affecting a payment service or customer-facing application is not just an internal IT issue. It is a business issue with direct consequences.<\/p><p class=\"wp-block-paragraph\">Modern environments make those four capabilities harder to sustain at the same time. Infrastructure is no longer contained in a single data center with visible dependencies and tightly controlled change. Most environments now span on-premises systems, multiple cloud providers, containerized workloads, SaaS applications, and third-party network dependencies. Each layer produces its own telemetry, is monitored through its own tools, and is often managed by a different team. Complexity is distributed, and dependency chains are often invisible until something fails.<\/p><p class=\"wp-block-paragraph\">Manual operations do not scale in that environment. Teams still have to correlate noisy events, review context, pivot across disconnected tools, and build a working hypothesis before they can act. Each step costs minutes. Together, they can consume an hour or more before anyone has a clear view of the problem. By then, the blast radius has often expanded.<\/p><p class=\"wp-block-paragraph\">The deeper issue is structural. Most ITOps teams still operate with tools built to report on individual domains, such as network performance, APM, logs, cloud configuration. Each tool can be useful on its own, but none has a complete view of how a failure in one domain propagates into another. When a change ripples through interdependent systems, teams investigate symptoms in parallel while the actual cause sits upstream. That is the gap that erodes resilience: not a shortage of telemetry, but a shortage of connected, contextual intelligence.<\/p><h2 id=\"h-why-edwin-ai-matters-for-operational-resilience\" class=\"wp-block-heading\">Why Edwin AI Matters for Operational Resilience<\/h2><p class=\"wp-block-paragraph\">Edwin AI is the intelligence and orchestration layer built into the <a href=\"https:\/\/www.logicmonitor.com\/fr\/platform\">Plate-forme LogicMonitor<\/a>. It ingests telemetry from across an IT environment, helping teams correlate signals across hybrid environments.<\/p><p class=\"wp-block-paragraph\">What sets Edwin AI apart from <a href=\"https:\/\/www.logicmonitor.com\/blog\/what-is-aiops\">conventional AIOps<\/a> tooling is its ability to use topology, change data, and <a href=\"https:\/\/www.logicmonitor.com\/blog\/why-itops-automation-needs-context-graphs\">operational context<\/a> to reason across incidents. Rather than treating alerts as isolated events, Edwin AI maps relationships between services, components, and dependencies in real time. When a failure occurs, it can evaluate how that component connects to the rest of the environment, what changed recently, which services depend on it, and where impact is likely to spread. That structural awareness is what separates cause-and-effect reasoning from symptom reporting.<\/p><p class=\"wp-block-paragraph\">Edwin AI also moves beyond analysis into execution. It can recommend remediation steps, <a href=\"https:\/\/www.logicmonitor.com\/fr\/edwin-ai\/ai-automation\">generate and execute playbooks<\/a>, and operate within defined guardrails. Teams decide which actions require approval and which can run automatically, so accountability is built into the execution model from the start.<\/p><p class=\"wp-block-paragraph\">Edwin AI operates with the understanding that most ITOps teams <em>do not<\/em> lack data. Instead, they lack a fast, reliable way to turn signals into action. The time between detection and response is often lost to manual triage, <a href=\"https:\/\/www.logicmonitor.com\/blog\/reduce-fragmentation-in-it-operations-with-aiops-and-automation\">fragmentation<\/a>, and coordination overhead. Edwin AI compresses that gap by combining cross-domain visibility, contextual reasoning, and governed execution in one system. Instead of spending hours reconstructing what happened across disconnected tools, teams can work from a single, continuously updated view of what is happening, why it matters, and what to do next.<\/p><h2 id=\"h-how-edwin-ai-improves-signal-quality-for-resilience-decisions\" class=\"wp-block-heading\">How Edwin AI Improves Signal Quality for Resilience Decisions<\/h2><p class=\"wp-block-paragraph\">Alert volume is a symptom, but the underlying problem is decision quality. When teams receive thousands of alerts without context about which ones reflect real risk, they lose time <em>et<\/em> make worse decisions. They escalate the wrong incidents, delay response on the right ones, and spend investigative capacity on noise instead of service-impacting issues. Operational resilience depends on teams receiving accurate, contextualized information at the moment it matters.<\/p><p class=\"wp-block-paragraph\">Edwin AI addresses that problem at the source. Rather than filtering alerts after the fact, it processes signals across hybrid infrastructure to determine what each alert means in context: which service is affected, what the likely cause is, what else may be at risk, and what action makes sense next. That is what turns a notification into a usable signal.<\/p><h3 id=\"h-event-deduplication-and-correlation\" class=\"wp-block-heading\">Event Deduplication and Correlation<\/h3><p class=\"wp-block-paragraph\">When a configuration change causes cascading failures across dependent services, monitoring tools typically generate separate alerts for each affected component. Edwin AI groups those related signals into a single actionable event and traces the causal chain across the stack. That lets teams work the incident itself instead of triaging dozens of downstream symptoms.<\/p><h3 id=\"h-business-impact-prioritization\" class=\"wp-block-heading\">Business Impact Prioritization<\/h3><p class=\"wp-block-paragraph\">Edwin AI evaluates incidents based on scope, severity, and service impact, not just technical severity codes. A critical alert on a non-production system and a major alert on a payment service do not carry the same business weight. Edwin AI helps teams prioritize the incidents most likely to affect customers and operations, which reduces exposure when something goes wrong.<\/p><h3 id=\"h-suppressing-low-value-alerts-without-hiding-real-risk\" class=\"wp-block-heading\">Suppressing Low-Value Alerts Without Hiding Real Risk<\/h3><p class=\"wp-block-paragraph\">Context-aware suppression is different from blanket filtering. Edwin AI uses historical patterns and environmental context to suppress alerts that do not require action, such as recurring flapping conditions, scheduled maintenance noise, or low-priority events that consistently resolve on their own. It is not applying a broad threshold that risks hiding a real problem. That distinction matters. Suppress too aggressively and teams create blind spots. Suppress nothing and they stay buried in noise. Edwin AI aims to reduce noise without obscuring risk.<\/p><h2 id=\"h-how-edwin-ai-accelerates-root-cause-identification-across-hybrid-environments\" class=\"wp-block-heading\">How Edwin AI Accelerates Root Cause Identification Across Hybrid Environments<\/h2><p class=\"wp-block-paragraph\">In hybrid environments, the source of a problem and its visible symptoms are often far apart. A configuration change can lead to downstream application failures. Resource exhaustion on a cloud instance can surface first as latency reported by end users. When teams investigate from the symptom backward, they lose time, and in a production incident, time is service continuity.<\/p><p class=\"wp-block-paragraph\">Edwin AI approaches root cause identification differently. Instead of presenting teams with a stack of domain-specific alerts to sort through manually, it reasons across infrastructure, cloud, applications, network, and service dependencies at the same time. It uses topology-aware context, change history, and cross-domain signal patterns to identify likely causes based on how the environment actually behaves, not just which alert is loudest.<\/p><p class=\"wp-block-paragraph\">The resilience benefit is direct. Faster isolation of the source means faster containment. Teams that spend 45 minutes reconstructing what happened across multiple tools spend 45 minutes with an unresolved incident affecting users. Edwin AI shortens that investigation window by surfacing the likely causal chain with enough context to support action.<\/p><h3 id=\"h-cross-domain-signal-correlation\" class=\"wp-block-heading\">Cross-Domain Signal Correlation<\/h3><p class=\"wp-block-paragraph\">Edwin AI connects signals across infrastructure, cloud, applications, and service dependencies to trace issues back to their origin rather than their visible effects. If a configuration change triggers a wave of alerts across dependent services, Edwin AI can connect those signals to the originating event using change history and topology-aware context. That closes one of the biggest blind spots in hybrid environments: failures rarely stay inside one domain.<\/p><h3 id=\"h-context-graph-relationship-mapping\" class=\"wp-block-heading\">Context Graph Relationship Mapping<\/h3><p class=\"wp-block-paragraph\">Edwin AI maintains a dynamic <a href=\"https:\/\/www.logicmonitor.com\/edwin-ai-itops-context-graph\">context map<\/a> of service dependencies and component relationships as environments change. When a failure occurs, it uses that map to reason about propagation: what broke, what else is exposed, and which dependencies are carrying the impact. For teams operating complex hybrid stacks, that makes blast radius visible much earlier in the incident.<\/p><h3 id=\"h-plain-language-incident-summaries\" class=\"wp-block-heading\">Plain-Language Incident Summaries<\/h3><p class=\"wp-block-paragraph\">Edwin AI generates plain-language summaries that explain what happened, what is affected, and the likely cause. During an active incident, that does more than save time for an individual engineer. It gives NOC teams, specialists, and operations managers a shared factual baseline, reducing the coordination overhead that often extends MTTR in multi-team incidents.<\/p><h2 id=\"h-how-edwin-ai-predicts-and-prevents-outages-before-they-escalate\" class=\"wp-block-heading\">How Edwin AI Predicts and Prevents Outages Before They Escalate<\/h2><p class=\"wp-block-paragraph\">Recovering well from incidents matters. Avoiding preventable incidents matters more. Edwin AI shifts operations from response toward prevention by analyzing historical patterns, correlating early telemetry signals, and surfacing risk before it crosses into user impact.<\/p><p class=\"wp-block-paragraph\">The most important cases are often not dramatic failures, but instead slow-building conditions: configuration drift accumulating across a fleet, a database host trending toward saturation, or a dependency degrading quietly while individual checks still pass.&nbsp;<\/p><p class=\"wp-block-paragraph\">Reactive monitoring often misses these cases until thresholds are breached. Edwin AI connects the signals that precede them, including change records, topology relationships, and historical incident patterns, to identify elevated risk earlier.<\/p><h3 id=\"h-anomaly-detection-and-forecasting\" class=\"wp-block-heading\">Anomaly Detection and Forecasting<\/h3><p class=\"wp-block-paragraph\">Edwin AI uses historical telemetry to establish behavioral baselines across infrastructure, cloud, and application layers, then flags deviations before they escalate. A memory trend accelerating faster than expected, or a latency pattern that resembles a previous change-related incident, can surface as an early warning instead of a post-incident data point. That gives teams room to intervene during normal operations rather than during an outage.<\/p><h3 id=\"h-proactive-early-warning-insights\" class=\"wp-block-heading\">Proactive Early Warning Insights<\/h3><p class=\"wp-block-paragraph\">Detection alone is not enough. Edwin AI surfaces early warnings with relevant context: which services may be affected, what similar incidents looked like, and what remediation worked previously. That is what makes an early warning actionable rather than easy to ignore.<\/p><h3 id=\"h-early-intervention-through-automated-remediation\" class=\"wp-block-heading\">Early Intervention Through Automated Remediation<\/h3><p class=\"wp-block-paragraph\">When early warning signals appear, Edwin AI can recommend or execute playbooks within defined guardrails. In cases such as configuration drift or resource pressure, remediation can happen before the issue reaches production impact. Acting early with scoped, validated automation is usually safer than acting late under incident pressure, when the blast radius is larger and the margin for error is smaller.<\/p><h2 id=\"h-how-edwin-ai-automates-incident-routing-and-escalation\" class=\"wp-block-heading\">How Edwin AI Automates Incident Routing and Escalation<\/h2><p class=\"wp-block-paragraph\">Every minute an incident spends in the wrong queue extends recovery. In high-volume environments, manual triage is where coordination often breaks down. Severity gets misread, context is lost in handoffs, and the wrong team gets paged while the right one is brought in later.<\/p><p class=\"wp-block-paragraph\">Edwin AI automates routing decisions based on what an incident actually involves, not just how it was labeled. The result is fewer handoffs, faster assignment, and triage logic that stays consistent even when alert volume spikes. That consistency is itself part of resilience. Recovery improves when the right team starts with the right context.<\/p><h3 id=\"h-context-driven-triage\" class=\"wp-block-heading\">Context-Driven Triage<\/h3><p class=\"wp-block-paragraph\">Edwin AI routes incidents using scope, severity, and service impact. A storage issue affecting a revenue-critical application should not land in a generic queue for manual sorting. Edwin AI can attach context and route the incident to the team best positioned to resolve it.<\/p><h3 id=\"h-itsm-integration-and-orchestration\" class=\"wp-block-heading\">ITSM Integration and Orchestration<\/h3><p class=\"wp-block-paragraph\">Edwin AI integrates with ITSM platforms, including <a href=\"https:\/\/www.logicmonitor.com\/blog\/edwin-ai-servicenow-now-assist\">ServiceNow<\/a>, to keep incident records synchronized and support workflow orchestration. Updates can flow between Edwin AI and the ticketing system so teams are not managing separate versions of the incident. That reduces coordination overhead and helps preserve a complete audit trail from detection through resolution.<\/p><p class=\"wp-block-paragraph\">Core capabilities include incident routing, escalation triggering, enriched ticket creation, bidirectional synchronization, and workflow orchestration across connected tools.<\/p><h2 id=\"h-how-edwin-ai-enables-governed-autonomy-without-introducing-new-risk\" class=\"wp-block-heading\">How Edwin AI Enables Governed Autonomy Without Introducing New Risk<\/h2><p class=\"wp-block-paragraph\">Autonomous operations make IT leaders cautious for good reason. A misapplied remediation can worsen an incident, and undocumented automated actions can create compliance and operational risk long after the event itself. The issue is not whether automation is useful. It is whether it can be trusted in production.<\/p><p class=\"wp-block-paragraph\">With Edwin AI, <a href=\"https:\/\/www.logicmonitor.com\/blog\/ai-agent-governance-agentic-itops-workflows\">gouvernance<\/a> is part of the execution model. Teams decide how much authority to delegate, which actions require approval, and where autonomous action is appropriate. That changes the tradeoff. Engineers are not choosing between speed and control. They are choosing how to apply both.<\/p><h3 id=\"h-human-in-the-loop-approvals\" class=\"wp-block-heading\">Human-in-the-Loop Approvals<\/h3><p class=\"wp-block-paragraph\">Edwin AI can complete the reasoning work behind an action, including correlation, root cause identification, playbook selection, and remediation staging, while leaving final execution to an engineer. Approval becomes a confirmation step rather than the start of the investigation.<\/p><h3 id=\"h-audit-trails-and-rollback-controls\" class=\"wp-block-heading\">Audit Trails and Rollback Controls<\/h3><p class=\"wp-block-paragraph\">Every action Edwin AI takes can be logged with context: what triggered it, what was executed, and what changed. That matters during post-incident review and in regulated environments where traceability is required. Rollback support also helps teams recover quickly if an automated action produces an unexpected result.<\/p><h3 id=\"h-agentic-actions-with-built-in-validation\" class=\"wp-block-heading\">Agentic Actions With Built-In Validation<\/h3><p class=\"wp-block-paragraph\">Edwin AI&rsquo;s agentic actions operate within defined guardrails that validate proposed steps before execution. That matters because automation itself can become a source of incidents in complex environments. Pre-execution validation helps reduce the risk that remediation becomes the next failure.<\/p><h2 id=\"h-measurable-resilience-gains-teams-can-expect-from-edwin-ai\" class=\"wp-block-heading\">Measurable Resilience Gains Teams Can Expect From Edwin AI<\/h2><p class=\"wp-block-paragraph\">The most meaningful outcomes are the ones tied to resilience itself: how quickly teams detect problems, how accurately they isolate impact, how often issues recur, and whether critical services remain available under pressure.<\/p><p class=\"wp-block-paragraph\">Edwin AI can also shorten the path from detection to isolation by correlating related signals into a single incident with service context, likely origin, and affected dependencies. In some environments, teams have reported meaningful value quickly, including early correlation shortly after deployment.<\/p><p class=\"wp-block-paragraph\">It also supports prevention, not just faster recovery. By connecting incidents to change activity, dependency relationships, and historical patterns, Edwin AI helps teams identify the conditions behind recurring failures and address them at the source.<\/p><p class=\"wp-block-paragraph\">Production deployments have also reported reductions in ITSM incidents and <a href=\"https:\/\/www.logicmonitor.com\/blog\/reduce-mttr-with-ai\">Temps moyen pour r\u00e9parer<\/a>. Taken together, those results reflect better signal quality, faster root cause identification, and faster engagement of the right team.<\/p><p class=\"wp-block-paragraph\">For broader examples across industries and environments, <a href=\"https:\/\/www.logicmonitor.com\/case-studies\">LogicMonitor&rsquo;s customer stories<\/a> show how organizations are using Edwin AI to improve service continuity and reduce operational noise.<\/p><h2 id=\"h-build-operational-resilience-with-edwin-ai\" class=\"wp-block-heading\">Build Operational Resilience With Edwin AI<\/h2><p class=\"wp-block-paragraph\">Operational resilience in hybrid IT comes from three things:&nbsp;<\/p><ol class=\"wp-block-list\">\n<li>Seeing across the environment,&nbsp;<\/li>\n\n\n\n<li>Reasoning about what those signals mean,&nbsp;<\/li>\n\n\n\n<li>And acting within defined controls.&nbsp;<\/li>\n<\/ol><p class=\"wp-block-paragraph\">Edwin AI brings those capabilities together in a single operating model. Its cross-domain visibility provides the foundation. Its contextual reasoning improves correlation, prioritization, and root cause identification. Its governed execution extends those gains into remediation and workflow automation without giving up accountability.<\/p><p class=\"wp-block-paragraph\">That changes the day-to-day reality of incident response. Teams spend less time reconstructing context, less time routing work manually, and less time working downstream symptoms as separate problems. They can identify what matters faster, understand the likely source sooner, and act with more confidence.<\/p><p class=\"wp-block-paragraph\">For ITOps teams trying to improve service continuity in environments that are only becoming more distributed, that is the practical value of resilience: fewer blind spots, faster decisions, and less time lost between signal and action.<\/p><div style=\"height:30px\" aria-hidden=\"true\" class=\"wp-block-spacer key-takeaways\"><\/div><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50\">\n      <span class=\"head-icon\"><svg class=\"\" width=\"50px\" height=\"50px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-light-calendar-check\"><\/use>\n    <\/svg><\/span>\n  \n  <div class=\"rtc-text-content__wrapper\">\n          <h4 class=\"rtc-text-content__headline fs-sm-text-display-xxs fs-md-text-display-xs fs-lg-text-display-sm font-medium text-core-blue-900\">\n         D\u00e9couvrez comment l'automatisation de l'IA fera passer votre \u00e9quipe de la r\u00e9activit\u00e9 \u00e0 la proactivit\u00e9 avec Edwin AI.      <\/h4>\n    \n    \n          \n      \n              <div>\n            <a href=\"https:\/\/www.logicmonitor.com\/fr\/edwin-ai-demo\" class=\"btn btn-link\" target=\"_self\">\n        Demandez une d\u00e9mo          <span class=\"icon-end\"><svg class=\"\" width=\"20px\" height=\"20px\" style=\"fill: #060F4B\">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-arrow-right\"><\/use>\n    <\/svg><\/span>\n      <\/a>\n        <\/div>\n            <\/div>\n<\/div><h4 id=\"h-faqs\" class=\"wp-block-heading\">FAQ<\/h4><div class=\"accordion-block accordion-block--light\">\n      <div class=\"accordion-block__items\">\n              <div class=\"accordion-block__item active\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-how-quickly-can-teams-see-value-after-deploying-edwin-ai\">\n            How quickly can teams see value after deploying Edwin AI?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer active\">\n            <p><span style=\"font-weight: 400\">Some customers see value within hours of deployment, while others begin seeing measurable improvements within days. Alert correlation, deduplication, and noise reduction are often among the first gains. More advanced benefits, such as more accurate root cause identification and stronger early-warning signals, continue to improve over time as Edwin AI builds a deeper understanding of dependency patterns and incident history.<\/span><\/p>\n                      <\/div>\n        <\/div>\n              <div class=\"accordion-block__item\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-can-itops-teams-adopt-edwin-ai-without-disrupting-existing-workflows\">\n            Can ITOps teams adopt Edwin AI without disrupting existing workflows?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer\">\n            <p><span style=\"font-weight: 400\">Yes. Edwin AI is designed to layer into existing ITOps workflows rather than replace them. It connects to existing observability, APM, security, and ITSM tools through APIs and native integrations, so teams can introduce capabilities like alert correlation, noise reduction, and AI-assisted investigation while continuing to work in the systems they already use. Adoption can then expand over time as teams are ready to introduce more advanced automation.<\/span><\/p>\n                      <\/div>\n        <\/div>\n              <div class=\"accordion-block__item\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-how-does-edwin-ai-handle-false-positive-alerts\">\n            How does Edwin AI handle false positive alerts?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer\">\n            <p><span style=\"font-weight: 400\">Edwin AI uses cross-domain correlation, historical incident patterns, and contextual enrichment to identify alerts that do not reflect meaningful service risk. Instead of relying on blanket suppression rules, it evaluates alerts against related signals, maintenance context, and historical behavior. The goal is a smaller, higher-confidence queue, not a quieter but less trustworthy one.<\/span><\/p>\n                      <\/div>\n        <\/div>\n              <div class=\"accordion-block__item\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-can-edwin-ai-integrate-with-existing-monitoring-and-itsm-tools\">\n            Can Edwin AI integrate with existing monitoring and ITSM tools?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer\">\n            <p><span style=\"font-weight: 400\">es. Edwin AI connects with third-party event sources and ITSM platforms, including ServiceNow, and helps teams correlate signals across both legacy and modern environments. That allows teams to improve triage and incident response without first standardizing the entire tooling stack.<\/span><\/p>\n                      <\/div>\n        <\/div>\n              <div class=\"accordion-block__item\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-what-compliance-and-audit-capabilities-does-edwin-ai-provide-for-governed-automation\">\n            What compliance and audit capabilities does Edwin AI provide for governed automation?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer\">\n            <p><b>Edwin AI supports governed automation through role-based access controls (RBAC), human-in-the-loop workflows, guardrails for agent actions, and traceability of automated activity. Actions and execution context can be logged to support audit, review, and post-incident analysis, while rollback <\/b><span style=\"font-weight: 400\">capabilities help teams reverse remediation when needed. Together, these controls allow organizations to define who can take action, maintain oversight, and expand automation within established governance boundaries.<\/span><\/p>\n                      <\/div>\n        <\/div>\n          <\/div>\n  <\/div><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">For more detail on access controls, data handling, auditability, and AI governance, see our <a href=\"https:\/\/www.logicmonitor.com\/resources\/edwin-ai-security-faq\/?utm_source=chatgpt.com\">&nbsp;AI Security FAQ<\/a>.<\/p><p class=\"wp-block-paragraph\"><\/p><div class=\"wp-block-group has-background is-layout-constrained wp-container-core-group-is-layout-02b8269e wp-block-group-is-layout-constrained\" style=\"border-top-color:var(--wp--preset--color--lm-type-core-blue);border-top-width:4px;background-color:#1a31ff0d;padding-top:var(--wp--preset--spacing--50);padding-right:var(--wp--preset--spacing--50);padding-bottom:var(--wp--preset--spacing--50);padding-left:var(--wp--preset--spacing--50)\">\n<div class=\"wp-block-columns are-vertically-aligned-center is-layout-flex wp-container-core-columns-is-layout-6d2d2de7 wp-block-columns-is-layout-flex\">\n<div class=\"wp-block-column is-vertically-aligned-center is-layout-flow wp-block-column-is-layout-flow\" style=\"flex-basis:80px\">\n<figure class=\"wp-block-image size-full is-resized has-custom-border is-style-default\"><img loading=\"lazy\" decoding=\"async\" width=\"800\" height=\"800\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2025\/02\/margo.jpeg\" alt=\"\" class=\"wp-image-575227\" style=\"border-top-left-radius:99999px;border-top-right-radius:99999px;border-bottom-left-radius:99999px;border-bottom-right-radius:99999px;object-fit:cover;width:80px;height:80px\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2025\/02\/margo.jpeg 800w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2025\/02\/margo-300x300.jpeg 300w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2025\/02\/margo-150x150.jpeg 150w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2025\/02\/margo-768x768.jpeg 768w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\"><\/figure>\n<\/div>\n\n\n\n<div class=\"wp-block-column is-vertically-aligned-center is-layout-flow wp-block-column-is-layout-flow\">\n<h5 id=\"h-by-margo-poda\" class=\"wp-block-heading has-lm-display-xs-font-size\" style=\"margin-top:0;margin-bottom:0\">Par Margo Poda<\/h5>\n\n\n\n<p class=\"has-lm-text-md-font-size wp-block-paragraph\" id=\"h-\" style=\"margin-top:0;margin-bottom:0\">Responsable du marketing de contenu, IA<\/p>\n<\/div>\n\n\n\n<div class=\"wp-block-column is-vertically-aligned-center is-layout-flow wp-block-column-is-layout-flow\">\n<figure class=\"wp-block-image alignright size-large is-resized\"><a href=\"https:\/\/www.linkedin.com\/in\/mspoda\/\" target=\"_blank\" rel=\" noreferrer noopener\"><img decoding=\"async\" src=\"data:image\/svg+xml,%3Csvg%20xmlns='http:\/\/www.w3.org\/2000\/svg'%20height='72'%20viewBox='0%200%2072%2072'%20width='72'%3E%3Cg%20fill='none'%20fill-rule='evenodd'%3E%3Cpath%20d='M8,72%20L64,72%20C68.418278,72%2072,68.418278%2072,64%20L72,8%20C72,3.581722%2068.418278,-8.11624501e-16%2064,0%20L8,0%20C3.581722,8.11624501e-16%20-5.41083001e-16,3.581722%200,8%20L0,64%20C5.41083001e-16,68.418278%203.581722,72%208,72%20Z'%20fill='%230d6efd'\/%3E%3Cpath%20d='M62,62%20L51.315625,62%20L51.315625,43.8021149%20C51.315625,38.8127542%2049.4197917,36.0245323%2045.4707031,36.0245323%20C41.1746094,36.0245323%2038.9300781,38.9261103%2038.9300781,43.8021149%20L38.9300781,62%20L28.6333333,62%20L28.6333333,27.3333333%20L38.9300781,27.3333333%20L38.9300781,32.0029283%20C38.9300781,32.0029283%2042.0260417,26.2742151%2049.3825521,26.2742151%20C56.7356771,26.2742151%2062,30.7644705%2062,40.051212%20L62,62%20Z%20M16.349349,22.7940133%20C12.8420573,22.7940133%2010,19.9296567%2010,16.3970067%20C10,12.8643566%2012.8420573,10%2016.349349,10%20C19.8566406,10%2022.6970052,12.8643566%2022.6970052,16.3970067%20C22.6970052,19.9296567%2019.8566406,22.7940133%2016.349349,22.7940133%20Z%20M11.0325521,62%20L21.769401,62%20L21.769401,27.3333333%20L11.0325521,27.3333333%20L11.0325521,62%20Z'%20fill='%23FFF'\/%3E%3C\/g%3E%3C\/svg%3E\" alt=\"\" style=\"object-fit:cover;width:34px;height:34px\"><\/a><\/figure>\n<\/div>\n<\/div>\n\n\n\n<p class=\"has-lm-type-ballpoint-blue-color has-text-color has-link-color has-lm-text-lg-font-size wp-elements-1 wp-block-paragraph\" style=\"margin-top:var(--wp--preset--spacing--40);margin-bottom:var(--wp--preset--spacing--40);font-style:normal;font-weight:500\">Margo Poda leads content strategy for Edwin AI at LogicMonitor. With a background in both enterprise tech and AI startups, she focuses on making complex topics clear, relevant, and worth reading&mdash;especially in a space where too much content sounds the same. She&rsquo;s not here to hype AI; she&rsquo;s here to help people understand what it can actually do.<\/p>\n\n\n\n<p class=\"has-lm-type-ballpoint-blue-color has-text-color has-link-color has-lm-text-sm-font-size wp-elements-2 wp-block-paragraph\" style=\"font-style:normal;font-weight:500\">Clause de non-responsabilit\u00e9 : les opinions exprim\u00e9es sur ce blog sont celles de l'auteur et ne refl\u00e8tent pas n\u00e9cessairement celles de LogicMonitor ou de ses filiales.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>La r\u00e9silience op\u00e9rationnelle d\u00e9pend de bien plus que de la simple d\u00e9tection d'incidents. D\u00e9couvrez comment Edwin AI aide les \u00e9quipes ITOps \u00e0 relier les signaux, \u00e0 isoler la cause racine, \u00e0 pr\u00e9dire les risques et \u00e0 r\u00e9agir plus rapidement dans les environnements hybrides.<\/p>","protected":false},"author":16,"featured_media":625868,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"unicorn_plugin_options_block_body_class":"","footnotes":""},"categories":[5035],"tags":[],"industry":[6790],"role":[6786],"lm_strategic_tags":[],"topic":[6769],"author_attribution":[],"lm_product":[],"class_list":["post-625864","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","industry-all","role-itops","topic-aiops-automation"],"acf":{"page_language":"english","translated_pages":"","updated_date":null,"author_section_checkbox":true,"author_image":575231,"author_linkedin":"https:\/\/www.linkedin.com\/in\/mspoda\/","author_name":"Margo Poda","author_job_title":"Sr. Content Marketing Manager, AI","author_dept":"Edwin AI","author_bio":"Margo Poda leads content strategy for Edwin AI at LogicMonitor, covering agentic AI, AIOps, observability, and AI-powered IT operations. She focuses on making technically complex topics clear and useful for IT leaders and practitioners. Her work translates emerging AI capabilities into practical stories about how teams can improve the way they operate.","reviewer_name":""},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.4 (Yoast SEO v28.4) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Edwin AI and the New Requirements for Operational Resilience in ITOps - LogicMonitor<\/title>\n<meta name=\"description\" content=\"Edwin AI improves operational resilience with cross-domain correlation, faster root cause analysis, proactive insights, and governed automation.\" \/>\n<meta name=\"robots\" content=\"noindex, nofollow\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Edwin AI and the New Requirements for Operational Resilience in ITOps\" \/>\n<meta property=\"og:description\" content=\"Edwin AI improves operational resilience with cross-domain correlation, faster root cause analysis, proactive insights, and governed automation.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.logicmonitor.com\/fr\/blog\/edwin-ai-operational-resilience-itops\" \/>\n<meta property=\"og:site_name\" content=\"LogicMonitor\" \/>\n<meta property=\"article:published_time\" content=\"2026-09-04T13:00:00+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/09\/Blog_Edwin-AI-and-the-New-Requirements_940x528_Featured-Image.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1410\" \/>\n\t<meta property=\"og:image:height\" content=\"792\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"destiny.setzer@logicmonitor.com\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"23 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/edwin-ai-operational-resilience-itops#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/edwin-ai-operational-resilience-itops\"},\"author\":{\"name\":\"destiny.setzer@logicmonitor.com\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\"},\"headline\":\"Edwin AI and the New Requirements for Operational Resilience in ITOps\",\"datePublished\":\"2026-09-04T13:00:00+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/edwin-ai-operational-resilience-itops\"},\"wordCount\":2511,\"image\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/edwin-ai-operational-resilience-itops#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/Blog_Edwin-AI-and-the-New-Requirements_940x528_Featured-Image.png\",\"articleSection\":[\"Blog\"],\"inLanguage\":\"fr-FR\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/edwin-ai-operational-resilience-itops\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/edwin-ai-operational-resilience-itops\",\"name\":\"Edwin AI and the New Requirements for Operational Resilience in ITOps - LogicMonitor\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/edwin-ai-operational-resilience-itops#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/edwin-ai-operational-resilience-itops#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/Blog_Edwin-AI-and-the-New-Requirements_940x528_Featured-Image.png\",\"datePublished\":\"2026-09-04T13:00:00+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\"},\"description\":\"Edwin AI improves operational resilience with cross-domain correlation, faster root cause analysis, proactive insights, and governed automation.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/edwin-ai-operational-resilience-itops#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/edwin-ai-operational-resilience-itops\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/edwin-ai-operational-resilience-itops#primaryimage\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/Blog_Edwin-AI-and-the-New-Requirements_940x528_Featured-Image.png\",\"contentUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/Blog_Edwin-AI-and-the-New-Requirements_940x528_Featured-Image.png\",\"width\":1410,\"height\":792},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/edwin-ai-operational-resilience-itops#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.logicmonitor.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Edwin AI and the New Requirements for Operational Resilience in ITOps\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#website\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/\",\"name\":\"LogicMonitor\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\",\"name\":\"destiny.setzer@logicmonitor.com\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Edwin AI and the New Requirements for Operational Resilience in ITOps - LogicMonitor","description":"Edwin AI improves operational resilience with cross-domain correlation, faster root cause analysis, proactive insights, and governed automation.","robots":{"index":"noindex","follow":"nofollow"},"og_locale":"fr_FR","og_type":"article","og_title":"Edwin AI and the New Requirements for Operational Resilience in ITOps","og_description":"Edwin AI improves operational resilience with cross-domain correlation, faster root cause analysis, proactive insights, and governed automation.","og_url":"https:\/\/www.logicmonitor.com\/fr\/blog\/edwin-ai-operational-resilience-itops","og_site_name":"LogicMonitor","article_published_time":"2026-09-04T13:00:00+00:00","og_image":[{"width":1410,"height":792,"url":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/09\/Blog_Edwin-AI-and-the-New-Requirements_940x528_Featured-Image.png","type":"image\/png"}],"author":"destiny.setzer@logicmonitor.com","twitter_card":"summary_large_image","twitter_misc":{"Written by":"","Est. reading time":"23 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/edwin-ai-operational-resilience-itops#article","isPartOf":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/edwin-ai-operational-resilience-itops"},"author":{"name":"destiny.setzer@logicmonitor.com","@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def"},"headline":"Edwin AI and the New Requirements for Operational Resilience in ITOps","datePublished":"2026-09-04T13:00:00+00:00","mainEntityOfPage":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/edwin-ai-operational-resilience-itops"},"wordCount":2511,"image":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/edwin-ai-operational-resilience-itops#primaryimage"},"thumbnailUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/09\/Blog_Edwin-AI-and-the-New-Requirements_940x528_Featured-Image.png","articleSection":["Blog"],"inLanguage":"fr-FR"},{"@type":"WebPage","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/edwin-ai-operational-resilience-itops","url":"https:\/\/www.logicmonitor.com\/fr\/blog\/edwin-ai-operational-resilience-itops","name":"Edwin AI and the New Requirements for Operational Resilience in ITOps - LogicMonitor","isPartOf":{"@id":"https:\/\/www.logicmonitor.com\/fr\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/edwin-ai-operational-resilience-itops#primaryimage"},"image":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/edwin-ai-operational-resilience-itops#primaryimage"},"thumbnailUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/09\/Blog_Edwin-AI-and-the-New-Requirements_940x528_Featured-Image.png","datePublished":"2026-09-04T13:00:00+00:00","author":{"@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def"},"description":"Edwin AI improves operational resilience with cross-domain correlation, faster root cause analysis, proactive insights, and governed automation.","breadcrumb":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/edwin-ai-operational-resilience-itops#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.logicmonitor.com\/fr\/blog\/edwin-ai-operational-resilience-itops"]}]},{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/edwin-ai-operational-resilience-itops#primaryimage","url":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/09\/Blog_Edwin-AI-and-the-New-Requirements_940x528_Featured-Image.png","contentUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/09\/Blog_Edwin-AI-and-the-New-Requirements_940x528_Featured-Image.png","width":1410,"height":792},{"@type":"BreadcrumbList","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/edwin-ai-operational-resilience-itops#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.logicmonitor.com\/"},{"@type":"ListItem","position":2,"name":"Edwin AI and the New Requirements for Operational Resilience in ITOps"}]},{"@type":"WebSite","@id":"https:\/\/www.logicmonitor.com\/fr\/#website","url":"https:\/\/www.logicmonitor.com\/fr\/","name":"LogicMonitor","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.logicmonitor.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Person","@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def","name":"destiny.setzer@logicmonitor.com"}]}},"_links":{"self":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/625864","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/users\/16"}],"replies":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/comments?post=625864"}],"version-history":[{"count":5,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/625864\/revisions"}],"predecessor-version":[{"id":625874,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/625864\/revisions\/625874"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/media\/625868"}],"wp:attachment":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/media?parent=625864"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/categories?post=625864"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/tags?post=625864"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/industry?post=625864"},{"taxonomy":"role","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/role?post=625864"},{"taxonomy":"lm_strategic_tags","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/lm_strategic_tags?post=625864"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/topic?post=625864"},{"taxonomy":"author_attribution","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/author_attribution?post=625864"},{"taxonomy":"lm_product","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/lm_product?post=625864"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":533224,"date":"2026-09-02T16:44:00","date_gmt":"2026-09-02T21:44:00","guid":{"rendered":"https:\/\/www.logicmonitor.com\/?p=533224"},"modified":"2026-09-04T14:57:25","modified_gmt":"2026-09-04T19:57:25","slug":"how-to-use-quarkus-live-coding-in-docker","status":"publish","type":"post","link":"https:\/\/www.logicmonitor.com\/fr\/blog\/how-to-use-quarkus-live-coding-in-docker","title":{"rendered":"Comment utiliser le Live Coding (Live Reload) de Quarkus dans Docker"},"content":{"rendered":"<?xml encoding=\"UTF-8\"><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50 rtc-text-content--no-top-pad\">\n      <span class=\"head-icon\"><svg class=\"\" width=\"50px\" height=\"50px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-light-book-open\"><\/use>\n    <\/svg><\/span>\n  \n  <div class=\"rtc-text-content__wrapper\">\n          <h4 class=\"rtc-text-content__headline fs-sm-text-display-xs fs-md-text-display-sm fs-lg-text-display-md font-medium text-core-blue-900\">\n        Le t\u00e9l\u00e9chargement rapide      <\/h4>\n    \n          <div class=\"rtc-text-content__body fs-sm-text-md fs-md-text-lg fs-lg-text-lg text-core-blue-900 headline-is-quote\">\n        <p><b> Quarkus Live Coding, also called Live Reload, works with Docker when the container runs in Quarkus development mode and is configured for remote development.<\/b><\/p>\n<p><\/p>\n      <\/div>\n    \n                  <ul class=\"rtc-text-content__bullet-list\">\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p><span style=\"font-weight: 400\">Generated Quarkus container configurations typically use production-style execution, so enable dev mode explicitly with <code>QUARKUS_LAUNCH_DEVMODE=true.<\/code><br>\n<\/span><\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p><span style=\"font-weight: 400\">The workflow requires three elements: dev mode, a mutable JAR, and a reachable quarkusRemoteDev connection.<br>\n<\/span><\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p><span style=\"font-weight: 400\">Keep Live Coding settings in application-dev.properties so a standard production build does not include them.<br>\n<\/span><\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p><span style=\"font-weight: 400\">After development, use LogicMonitor to monitor the resulting service across containers, JVM resources, dependencies, and network performance before production traffic exposes an issue.<br>\n<\/span><\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                  <\/ul>\n      \n      \n            <\/div>\n<\/div><p class=\"wp-block-paragraph\">Quarkus Live Coding lets you edit source code and see changes in the running application after Quarkus automatically recompiles and reloads the affected code, without a manual rebuild or redeployment.&nbsp;<\/p><p class=\"wp-block-paragraph\">Locally, this happens automatically in dev mode. Inside a Docker container, it takes a few extra configuration steps because containers default to production mode, which disables Live Coding on purpose.<\/p><p class=\"wp-block-paragraph\">In this Quarkus Docker guide, we&rsquo;ll cover how to create a Quarkus app, run it locally with Live Coding, and then get that same Live Coding workflow running inside a Docker container.<\/p><div id=\"\" class=\"lm-callout-box lm-callout-box-disclaimer\" style=\"--lm-callout-box-indent: 0\">\n    <p><b>Avis de non-responsabilit\u00e9 :<\/b> Last verified against Quarkus 3.33 LTS (current as of mid-2026). Quarkus releases new minor versions every 4-6 weeks, so check quarkus.io\/releases for the latest LTS before you pin a version in production.<\/p>\n  <\/div><h2 id=\"h-prerequisites\" class=\"wp-block-heading\">Prerequisites<\/h2><p class=\"wp-block-paragraph\">Install these before starting:<\/p><ul class=\"wp-block-list\">\n<li>JDK 17, 21, or 25, depending on the Quarkus version and project requirements<\/li>\n\n\n\n<li>Docker or Podman<\/li>\n\n\n\n<li>Gradle or Maven, preferably using the Maven or Gradle wrapper generated with the project.<\/li>\n<\/ul><div id=\"\" class=\"lm-callout-box lm-callout-box-note\" style=\"--lm-callout-box-indent: 0\">\n    <p><b>Remarque :<\/b><\/p>\n<p><strong>Enable Live Coding in Docker<\/strong><\/p>\n<p>If you already have a Quarkus application and need the abbreviated workflow:<\/p>\n<p><strong>Step 1:<\/strong> <code>Set QUARKUS_LAUNCH_DEVMODE=true<\/code> as an environment variable on your Docker container.<\/p>\n<p><strong>Step 2:<\/strong> Ajouter <code>quarkus.package.jar.type=mutable-jar, quarkus.live-reload.password=<\/code>, et <code>quarkus.live-reload.url=https:\/\/localhost:8080<\/code> to application.properties or application-dev.properties.<\/p>\n<p><strong>Step 3:<\/strong> Build the JAR, build the Docker image, and run the container.<\/p>\n<p><strong>Step 4:<\/strong> Connect with .\/gradlew quarkusRemoteDev (Gradle) or .\/mvnw quarkus:remote-dev (Maven).<\/p>\n  <\/div><p class=\"wp-block-paragraph\">If you put the config in application-dev.properties, add -Dquarkus.profile=dev to both the build command and the remote-dev command. The rest of this guide walks through why each step is necessary and what to do when one of them doesn&rsquo;t work.&nbsp;&nbsp;<\/p><div id=\"\" class=\"lm-callout-box lm-callout-box-note\" style=\"--lm-callout-box-indent: 0\">\n    <p><b>Version Note:<\/b> Examples were verified against Quarkus 3.33 LTS and Java 25. Confirm the current Quarkus LTS and generate Dockerfile templates before using these commands in a new project.<\/p>\n  <\/div><h2 id=\"h-what-is-live-coding-in-quarkus\" class=\"wp-block-heading\">What Is Live Coding in Quarkus?<\/h2><p class=\"wp-block-paragraph\">Live coding in Quarkus, also called Development Mode or dev mode, continuously monitors your source files and automatically rebuilds and reloads the application when you make changes by eliminating the need for manual restarts.<\/p><p class=\"wp-block-paragraph\">This only works in dev mode, not in a production build. It speeds up the loop of writing code and testing it, not to be part of how you deploy your app; you still use a normal, unchanging build everywhere else.<\/p><p class=\"wp-block-paragraph\">The workflow is: when your app runs in dev mode, it checks for source changes each time a request comes in. If something changed, Quarkus compiles just that part of the code and updates the running app before answering the request.&nbsp;<\/p><p class=\"wp-block-paragraph\">That first request after a change takes a bit longer because of the compile step; after that, things run at normal speed again until you make another edit.<\/p><p class=\"wp-block-paragraph\">This works the same way whether the app is running directly on your machine or inside a Docker container. The one difference with a container is that you have to tell it to run in dev mode and give your local Quarkus CLI a way to reach it.<\/p><h2 id=\"h-how-to-create-my-first-quarkus-app\" class=\"wp-block-heading\">How to Create My First Quarkus App<\/h2><p class=\"wp-block-paragraph\">The most direct way to create a Quarkus project is the Quarkus CLI. Installation and Java or build-tool requirements depend on the selected setup, so verify them against the current Quarkus documentation.&nbsp;<\/p><p class=\"wp-block-paragraph\">Alternatively, code.quarkus.io generates the same project structure through a browser-based form.<\/p><p class=\"wp-block-paragraph\">With the CLI installed, create a new Gradle-based project:<\/p><div class=\"wp-block-melonpan-block-code mbcode-theme-tomorrow_night mbcode-scheme-dark mbcode-padding_tb-40 mbcode-padding_lr-30\"><pre><code>quarkus create app --gradle org.acme:docker-live-coding<\/code><\/pre><\/div><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">For Maven, drop the <code>--gradle flag<\/code>; Maven is the default build tool. Run quarkus create app <code>--help<\/code> to see the project-creation options, or quarkus -h to see the CLI&rsquo;s other general help commands.<\/p><p class=\"wp-block-paragraph\">This creates a docker-live-coding directory with a working REST endpoint, a unit test for it, and a set of Dockerfiles already wired up for you.<\/p><h2 class=\"wp-block-heading\" id=\"h-whats-inside-the-generated-project\">What&rsquo;s Inside the Generated Project?<\/h2><p class=\"wp-block-paragraph\">The endpoint is present at <code>src\/main\/java\/org\/acme\/GreetingResource.java<\/code>:<\/p><div class=\"wp-block-melonpan-block-code mbcode-theme-tomorrow_night mbcode-scheme-dark mbcode-padding_tb-40 mbcode-padding_lr-30\"><pre><code>@Path(\"\/hello\")\npublic class GreetingResource {\n    @GET\n    @Produces(MediaType.TEXT_PLAIN)\n    public String hello() {\n        return \"Hello from Quarkus REST\";\n    }\n}<\/code><\/pre><\/div><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">A matching test is at <code>src\/test\/java\/org\/acme\/GreetingResourceTest.java<\/code>:<br><\/p><div class=\"wp-block-melonpan-block-code mbcode-theme-tomorrow_night mbcode-scheme-dark mbcode-padding_tb-40 mbcode-padding_lr-30\"><pre><code>@QuarkusTest\npublic class GreetingResourceTest {\n\n    @Test\npublic void testHelloEndpoint() {\n        given()\n          .when().get(\"\/hello\")\n          .then()\n            .statusCode(200)\n            .body(is(\"Hello from Quarkus REST\"));\n    }\n\n}<\/code><\/pre><\/div><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">The CLI also generates Dockerfiles in <code>src\/main\/docker\/<\/code>:<\/p><figure class=\"wp-block-table is-style-stripes\"><table class=\"has-fixed-layout\"><thead><tr><th><strong>Dockerfile<\/strong><\/th><th><strong>Objectif<\/strong><\/th><\/tr><\/thead><tbody><tr><td>Dockerfile.jvm<\/td><td>This Dockerfile is used to build a container that runs the Quarkus application in JVM mode&nbsp;<\/td><\/tr><tr><td>Dockerfile.legacy-jar<\/td><td>The pre-Quarkus-1.12 JAR layout. Only relevant if you&rsquo;re maintaining an older project.<\/td><\/tr><tr><td>Dockerfile.native<\/td><td>This Dockerfile is used to build a container that runs the Quarkus application in native (no JVM) mode. It copies in a native executable, already compiled separately with GraalVM.&nbsp;<\/td><\/tr><tr><td>Dockerfile.native-micro<\/td><td>The same native build on a smaller, more minimal base image.<\/td><\/tr><\/tbody><\/table><\/figure><h2 class=\"wp-block-heading\" id=\"h-how-do-i-run-my-quarkus-app-locally-in-dev-mode\">How Do I Run My Quarkus App Locally in Dev Mode?<\/h2><p class=\"wp-block-paragraph\">You can run it from the project directory:<\/p><p class=\"wp-block-paragraph\"><strong>CLI<\/strong><\/p><p class=\"wp-block-paragraph\"><code>quarkus dev<\/code><\/p><p class=\"wp-block-paragraph\"><strong>Gradle<\/strong><\/p><p class=\"wp-block-paragraph\"><code>.\/gradlew quarkusDev<\/code><\/p><p class=\"wp-block-paragraph\"><strong>Maven<\/strong><\/p><p class=\"wp-block-paragraph\"><code>.\/mvnw quarkus:dev<\/code><\/p><p class=\"wp-block-paragraph\">Once it starts, you&rsquo;ll see a log line confirming dev mode and Live Coding are active, and your app is reachable at <code>http:\/\/localhost:8080<\/code>. Open a second terminal and send a request to <code>http:\/\/localhost:8080\/hello<\/code>. You should receive: <code>Hello from Quarkus REST<\/code>.<\/p><h2 class=\"wp-block-heading\" id=\"h-how-does-live-reload-work-in-quarkus-dev-mode\">How Does Live Reload Work in Quarkus Dev Mode?<\/h2><p class=\"wp-block-paragraph\">With the app still running, edit GreetingResource.java:<\/p><div class=\"wp-block-melonpan-block-code mbcode-theme-tomorrow_night mbcode-scheme-dark mbcode-padding_tb-40 mbcode-padding_lr-30\"><pre><code>public String hello() {\n\n&nbsp;&nbsp;&nbsp;&nbsp;return \"Hello from Quarkus REST. How are you?\";\n\n}<\/code><\/pre><\/div><p class=\"wp-block-paragraph\">Save the file, then run the same curl command again. The next request should reflect the new text after Quarkus detects the change, recompiles the affected source, and redeploys the application in dev mode.<\/p><p class=\"wp-block-paragraph\">Quarkus detected the change on the next incoming request and recompiled only what changed before serving it. Simple edits like this one, which only change a method body, are usually applied through Quarkus&rsquo;s state-preserving reload, so the app doesn&rsquo;t lose its in-memory state.&nbsp;<\/p><p class=\"wp-block-paragraph\">Structural changes like adding a field or changing a method signature trigger a full application restart instead, which does reset state.&nbsp;<\/p><h2 class=\"wp-block-heading\" id=\"h-how-do-i-use-a-dockerfile-for-quarkus-live-coding\">How Do I Use a Dockerfile for Quarkus Live Coding?<\/h2><p class=\"wp-block-paragraph\">First, build the JAR.&nbsp;<\/p><p class=\"wp-block-paragraph\"><strong>Using the Quarkus CLI:<\/strong><\/p><p class=\"wp-block-paragraph\"><code>quarkus build<\/code><\/p><p class=\"wp-block-paragraph\"><strong>Using Gradle:<\/strong><\/p><p class=\"wp-block-paragraph\"><code>.\/gradlew build<\/code><\/p><p class=\"wp-block-paragraph\"><strong>Using Maven:&nbsp;<\/strong><\/p><p class=\"wp-block-paragraph\"><code>.\/mvnw package<\/code><\/p><p class=\"wp-block-paragraph\">If you leave the hello() change in place from the previous step, either revert it or update the test, the build fails if the test doesn&rsquo;t match the endpoint.<\/p><p class=\"wp-block-paragraph\"><strong>Build the image with Dockerfile.jvm:<\/strong><\/p><p class=\"wp-block-paragraph\"><code>docker build -f src\/main\/docker\/Dockerfile.jvm -t quarkus\/docker-live-coding .<\/code><\/p><p class=\"wp-block-paragraph\"><strong>Run it:<\/strong><\/p><p class=\"wp-block-paragraph\"><code>docker run -i --rm -p 8080:8080 quarkus\/docker-live-coding<\/code><\/p><p class=\"wp-block-paragraph\">Curl the endpoint again, and you&rsquo;ll get the original greeting back. The container doesn&rsquo;t have your local uncommitted changes baked in unless you rebuilt the image with them. Editing the source file while this container is running does not change the application.&nbsp;<\/p><p class=\"wp-block-paragraph\">The startup logs explain why: Profile prod activated. A container built from Dockerfile.jvm runs in production mode, and production mode has no Live Coding to activate.<\/p><h2 class=\"wp-block-heading\" id=\"h-why-doesnt-live-coding-work-in-docker-by-default\">Why Doesn&rsquo;t Live Coding Work in Docker by Default?<\/h2><p class=\"wp-block-paragraph\">Live Coding is a dev-mode-only feature, and the default Dockerfiles Quarkus generates are built for production mode.&nbsp;<\/p><p class=\"wp-block-paragraph\">Getting Live Coding working in a container means telling that container to run in dev mode instead, then giving your local machine a way to connect to it and push source changes.&nbsp;<\/p><p class=\"wp-block-paragraph\">Docker isolates the container filesystem from the host, so the container cannot watch local source files in the same way as Quarkus dev.<\/p><p class=\"wp-block-paragraph\">A typical remote-development workflow requires:<\/p><ul class=\"wp-block-list\">\n<li>Quarkus development mode, enabled with <code>QUARKUS_LAUNCH_DEVMODE=true<\/code><\/li>\n\n\n\n<li>a mutable JAR and write access to the deployment resources<\/li>\n\n\n\n<li>a reachable remote-development endpoint and the required authentication password.<\/li>\n<\/ul><p class=\"wp-block-paragraph\">The next three sections cover each one.<\/p><h2 class=\"wp-block-heading\" id=\"h-how-to-configure-docker-for-quarkusremotedev\">How to Configure Docker for quarkusRemoteDev<\/h2><p class=\"wp-block-paragraph\">Follow these steps:&nbsp;<\/p><h3 id=\"h-step-1-switch-the-container-to-dev-mode\" class=\"wp-block-heading\">Step 1: Switch the Container to dev Mode<\/h3><p class=\"wp-block-paragraph\">Add this environment variable to your Dockerfile:<\/p><p class=\"wp-block-paragraph\"><code>ENV QUARKUS_LAUNCH_DEVMODE=true<\/code><\/p><p class=\"wp-block-paragraph\">Rather than editing Dockerfile.jvm directly, copy it to a new Dockerfile.dev so you keep a clean production reference. Since this Dockerfile copies in an already-built JAR rather than compiling inside the container, use the runtime variant of the base image (openjdk-25-runtime), not the full builder image:<\/p><div class=\"wp-block-melonpan-block-code mbcode-theme-tomorrow_night mbcode-scheme-dark mbcode-padding_tb-40 mbcode-padding_lr-30\"><pre><code>FROM registry.access.redhat.com\/ubi9\/openjdk-25-runtime:1.24-3.1786536503\nENV LANG='en_US.UTF-8' LANGUAGE='en_US:en'\n\nCOPY --chown=185 build\/quarkus-app\/lib\/ \/deployments\/lib\/\nCOPY --chown=185 build\/quarkus-app\/*.jar \/deployments\/\nCOPY --chown=185 build\/quarkus-app\/app\/ \/deployments\/app\/\nCOPY --chown=185 build\/quarkus-app\/quarkus\/ \/deployments\/quarkus\/\nRUN chmod o+rw -R \/deployments\n\nEXPOSE 8080\nUSER 185\nENV JAVA_OPTS=\"-Dquarkus.http.host=0.0.0.0 -Djava.util.logging.manager=org.jboss.logmanager.LogManager\"\nENV JAVA_APP_JAR=\"\/deployments\/quarkus-run.jar\"\n\nENV QUARKUS_LAUNCH_DEVMODE=true<\/code><\/pre><\/div><p class=\"wp-block-paragraph\"><code>registry.access.redhat.com\/ubi9\/openjdk-25-runtime<\/code> is Red Hat&rsquo;s official UBI9 OpenJDK 25 runtime image. See the Red Hat Ecosystem Catalog listing for the current tag before you pin one; it&rsquo;s a recent addition (GA in December 2025), so confirm the tag is still current rather than copying it verbatim from this guide.<\/p><p class=\"wp-block-paragraph\">If the Quarkus CLI generates a slightly different Dockerfile.jvm for your version, that&rsquo;s expected. Quarkus updates these templates over time. As long as the <code>QUARKUS_LAUNCH_DEVMODE=true<\/code> line is present, the rest of this walkthrough applies.<\/p><p class=\"wp-block-paragraph\">The RUN chmod o+rw -R \/deployments line is required and easy to miss: without it, the container doesn&rsquo;t have write permission to update its own deployment files, so the remote-dev connection you&rsquo;ll set up next can&rsquo;t actually push your code changes into the running app.&nbsp;<\/p><h3 id=\"h-step-2-make-the-build-mutable-and-reachable\" class=\"wp-block-heading\">Step 2: Make the Build Mutable and Reachable<\/h3><p class=\"wp-block-paragraph\">Open application.properties (in src\/main\/resources) and add:<\/p><div class=\"wp-block-melonpan-block-code mbcode-theme-tomorrow_night mbcode-scheme-dark mbcode-padding_tb-40 mbcode-padding_lr-30\"><pre><code>quarkus.package.type=mutable-jar\nquarkus.live-reload.password=changeit\nquarkus.live-reload.url=https:\/\/localhost:8080<\/code><\/pre><\/div><p class=\"wp-block-paragraph\"><code>mutable-jar<\/code> tells Quarkus to package the build so the running application can be updated in place;&nbsp; a standard <code>fast-jar<\/code> build can&rsquo;t be.&nbsp;<\/p><p class=\"wp-block-paragraph\">Replace <code>changeit<\/code> with a real password; even for local-only use, it&rsquo;s worth doing correctly, because Quarkus also supports remote Live Coding against non-local machines, and a default password there is a real credential exposed to the network.<\/p><p class=\"wp-block-paragraph\"><code>quarkus.live-reload.url<\/code> is technically optional. You can pass it as a command-line flag instead,&nbsp; but setting it here means you don&rsquo;t have to remember it later.<\/p><h3 id=\"h-step-3-build-and-run-the-dev-mode-container\" class=\"wp-block-heading\">Step 3: Build and Run the dev-mode Container<\/h3><p class=\"wp-block-paragraph\">Run the following commands:<\/p><div class=\"wp-block-melonpan-block-code mbcode-theme-tomorrow_night mbcode-scheme-dark mbcode-padding_tb-40 mbcode-padding_lr-30\"><pre><code>quarkus build\ndocker build -f src\/main\/docker\/Dockerfile.dev -t quarkus\/docker-live-coding .\ndocker run -i --rm -p 8080:8080 quarkus\/docker-live-coding<\/code><\/pre><\/div><p class=\"wp-block-paragraph\">Maven equivalent for the first command: <code>.\/mvnw package<\/code>.<\/p><h3 id=\"h-step-4-connect-your-local-machine-to-the-container\" class=\"wp-block-heading\">Step 4: Connect Your Local Machine to the Container<\/h3><p class=\"wp-block-paragraph\">In a new terminal, from your project directory, run:<\/p><p class=\"wp-block-paragraph\"><code>.\/gradlew quarkusRemoteDev<\/code><\/p><p class=\"wp-block-paragraph\">For Maven:&nbsp;<\/p><p class=\"wp-block-paragraph\"><code>.\/mvnw quarkus:remote-dev.<\/code><\/p><p class=\"wp-block-paragraph\">If you didn&rsquo;t set `quarkus.live-reload.url` in application.properties, pass it explicitly:<\/p><p class=\"wp-block-paragraph\"><code>.\/gradlew quarkusRemoteDev -Dquarkus.live-reload.url=<a href=\"https:\/\/localhost:8080\">https:\/\/localhost:8080<\/a><\/code><\/p><p class=\"wp-block-paragraph\">A successful connection logs Connected to remote server. From here, edit your source file and curl the endpoint the same way you did locally. The container picks up the change through the remote-dev connection.<\/p><h2 class=\"wp-block-heading\" id=\"h-how-to-scope-live-coding-to-a-dev-profile-only\">How to Scope Live Coding to a Dev Profile Only<\/h2><p class=\"wp-block-paragraph\">The config from the previous section applies to every build, including one you might accidentally ship to production. A mutable JAR with live-reload enabled has no place outside a development environment, so the fix is to move those three properties into a profile-specific file instead of the shared application.properties.<\/p><p class=\"wp-block-paragraph\">Cr\u00e9er <code>application-dev.properties<\/code> next to the existing <code>application.properties<\/code>, and move the three Live Coding properties into it.&nbsp;<\/p><p class=\"wp-block-paragraph\">Quarkus requires <code>application.properties<\/code> to still exist in that same location, even if empty, for the profile-specific file to be chosen at all, so don&rsquo;t delete it once you&rsquo;ve moved the properties out:<\/p><p class=\"wp-block-paragraph\"><\/p><div class=\"wp-block-melonpan-block-code mbcode-theme-tomorrow_night mbcode-scheme-dark mbcode-padding_tb-40 mbcode-padding_lr-30\"><pre><code>quarkus.package.jar.type=mutable-jar\n\nquarkus.live-reload.password=changeit\n\nquarkus.live-reload.url=https:\/\/localhost:8080<\/code><\/pre><\/div><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">Now these settings apply only when you explicitly build with the dev profile:<\/p><p class=\"wp-block-paragraph\"><\/p><div class=\"wp-block-melonpan-block-code mbcode-theme-tomorrow_night mbcode-scheme-dark mbcode-padding_tb-40 mbcode-padding_lr-30\"><pre><code>quarkus build -Dquarkus.profile=dev\n\n.\/gradlew quarkusRemoteDev -Dquarkus.profile=dev<\/code><\/pre><\/div><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">For Maven:&nbsp;<\/p><p class=\"wp-block-paragraph\"><code>.\/mvnw package -Dquarkus.profile=dev and .\/mvnw quarkus:remote-dev -Dquarkus.profile=dev.<\/code><\/p><p class=\"wp-block-paragraph\">Build without the profile flag, and Quarkus ignores the dev-only properties entirely, so a standard production build stays a standard production build.<\/p><h2 class=\"wp-block-heading\" id=\"h-is-it-safe-to-use-these-live-coding-configs-in-production\">Is It Safe to Use These Live Coding Configs in Production?<\/h2><p class=\"wp-block-paragraph\">No, don&rsquo;t run <code>mutable-jar<\/code> packaging or an active <code>quarkus.live-reload<\/code> connection in production. Both let a remote client push code changes into a live process, which is exactly what you don&rsquo;t want outside a development environment.&nbsp;<\/p><p class=\"wp-block-paragraph\">Scoping these settings to <code>application-dev.properties<\/code>, as covered in the previous section, is what prevents that from happening by accident, since a normal Quarkus build with no profile flag never picks them up.&nbsp;<\/p><p class=\"wp-block-paragraph\">Treat any environment where Live Coding is accessible, including a shared dev or staging cluster, with the same access controls you&rsquo;d use for a production secret.&nbsp;<\/p><h2 class=\"wp-block-heading\" id=\"h-what-are-my-options-for-building-a-quarkus-container-image\">What Are My Options for Building a Quarkus Container Image?<\/h2><p class=\"wp-block-paragraph\">You don&rsquo;t have to use docker build and docker run manually. Quarkus has extensions that build the image for you, usually without a hand-written Dockerfile. Which one to use depends on your setup.<\/p><p class=\"wp-block-paragraph\">Use one Quarkus container-image extension per build. If multiple builder extensions are present, select one explicitly with quarkus.container-image.builder or remove the others.&nbsp;<\/p><p class=\"wp-block-paragraph\">Choose Docker, Podman, Jib, Buildpacks, or OpenShift according to the build environment; do not enable multiple providers for the same build unless the selection is explicitly controlled.<\/p><h3 class=\"wp-block-heading\" id=\"h-docker\">Docker<\/h3><p class=\"wp-block-paragraph\">Use this if you&rsquo;re already comfortable with Dockerfiles. It uses the Docker binary and the Dockerfiles Quarkus already generated under <code>src\/main\/docker<\/code>.<\/p><p class=\"wp-block-paragraph\">Here&rsquo;s how to use it:<\/p><p class=\"wp-block-paragraph\"><strong>CLI:<\/strong><\/p><p class=\"wp-block-paragraph\"><code>quarkus extension add quarkus-container-image-docker<\/code><\/p><p class=\"wp-block-paragraph\"><strong>Maven:<\/strong><\/p><p class=\"wp-block-paragraph\"><code>.\/mvnw quarkus:add-extension -Dextensions='quarkus-container-image-docker'<\/code><\/p><p class=\"wp-block-paragraph\"><strong>Gradle:<\/strong><\/p><p class=\"wp-block-paragraph\"><code>.\/gradlew addExtension --extensions='quarkus-container-image-docker'<\/code><\/p><p class=\"wp-block-paragraph\">This extension can also build multi-platform images using docker buildx. But docker buildx build only loads the result into a single platform&rsquo;s Docker image.&nbsp;<\/p><p class=\"wp-block-paragraph\">Si vous d\u00e9finissez <code>quarkus.docker.buildx.platform<\/code> to more than one platform (for example, linux\/amd64,linux\/arm64), the images won&rsquo;t show up locally. You need to push them with <code>quarkus.container-image.push=true<\/code> as part of the same build instead, since Docker buildx cannot load a multi-platform result into the local Docker image store; push it to a registry as part of the build.<\/p><h3 class=\"wp-block-heading\" id=\"h-podman\">Podman<\/h3><p class=\"wp-block-paragraph\">Use this if you need something Podman does that Docker doesn&rsquo;t, such as native multi-platform builds. Otherwise, the Docker extension above already works with Podman, since Podman exposes a Docker-compatible API.<\/p><p class=\"wp-block-paragraph\">Here&rsquo;s how to add the following extensions:<\/p><p class=\"wp-block-paragraph\"><strong>CLI:<\/strong><\/p><p class=\"wp-block-paragraph\"><code>quarkus extension add quarkus-container-image-podman<\/code><\/p><p class=\"wp-block-paragraph\"><strong>Maven:<\/strong><\/p><p class=\"wp-block-paragraph\"><code>.\/mvnw quarkus:add-extension -Dextensions='quarkus-container-image-podman'<\/code><\/p><p class=\"wp-block-paragraph\"><strong>Gradle:<\/strong><\/p><p class=\"wp-block-paragraph\"><code>.\/gradlew addExtension --extensions='quarkus-container-image-podman'<\/code><\/p><h3 class=\"wp-block-heading\" id=\"h-jib\">Jib<\/h3><p class=\"wp-block-paragraph\">Use this in CI environments without a Docker daemon. Jib builds and pushes the image directly, with no Docker build step.<\/p><p class=\"wp-block-paragraph\">Here&rsquo;s how to add the following extensions:<\/p><p class=\"wp-block-paragraph\"><strong>CLI:<\/strong><\/p><p class=\"wp-block-paragraph\"><code>quarkus extension add quarkus-container-image-jib<\/code><\/p><p class=\"wp-block-paragraph\"><strong>Maven:<\/strong><\/p><p class=\"wp-block-paragraph\"><code>.\/mvnw quarkus:add-extension -Dextensions='quarkus-container-image-jib'<\/code><\/p><p class=\"wp-block-paragraph\"><strong>Gradle:<\/strong><\/p><p class=\"wp-block-paragraph\"><code>.\/gradlew addExtension --extensions='quarkus-container-image-jib'<\/code><\/p><h3 class=\"wp-block-heading\" id=\"h-buildpacks\">Buildpacks<\/h3><p class=\"wp-block-paragraph\">Use this if you want to skip writing or maintaining a Dockerfile. Buildpacks builds the image from your build output using a standard process instead.<\/p><p class=\"wp-block-paragraph\">Here&rsquo;s how to add the following extensions:<\/p><p class=\"wp-block-paragraph\"><strong>CLI:<\/strong><\/p><p class=\"wp-block-paragraph\"><code>quarkus extension add quarkus-container-image-buildpack<\/code><\/p><p class=\"wp-block-paragraph\"><strong>Maven:<\/strong><\/p><p class=\"wp-block-paragraph\"><code>.\/mvnw quarkus:add-extension -Dextensions='quarkus-container-image-buildpack'<\/code><\/p><p class=\"wp-block-paragraph\"><strong>Gradle:<\/strong><\/p><p class=\"wp-block-paragraph\"><code>.\/gradlew addExtension --extensions='quarkus-container-image-buildpack'<\/code><\/p><p class=\"wp-block-paragraph\">Buildpacks still needs a Docker daemon behind the scenes for the actual build. Unlike the other extensions, it doesn&rsquo;t ship with a default builder image, so you have to set <code>quarkus.buildpack.jvm-builder-image<\/code> (and <code>quarkus.buildpack.native-builder-image<\/code> for native builds) yourself.<\/p><h3 class=\"wp-block-heading\" id=\"h-openshift-binary-build\">OpenShift Binary Build<\/h3><p class=\"wp-block-paragraph\">Use this to build directly inside an OpenShift cluster. You upload your build artifacts, and OpenShift merges them into a builder image as part of the build.<\/p><p class=\"wp-block-paragraph\">Here&rsquo;s how to add the following extensions:<\/p><p class=\"wp-block-paragraph\"><strong>CLI:<\/strong><\/p><p class=\"wp-block-paragraph\"><code>quarkus extension add quarkus-container-image-openshift<\/code><\/p><p class=\"wp-block-paragraph\"><strong>Maven:<\/strong><\/p><p class=\"wp-block-paragraph\"><code>.\/mvnw quarkus:add-extension -Dextensions='quarkus-container-image-openshift'<\/code><\/p><p class=\"wp-block-paragraph\"><strong>Gradle:<\/strong><\/p><p class=\"wp-block-paragraph\"><code>.\/gradlew addExtension --extensions='quarkus-container-image-openshift'<\/code><\/p><h3 class=\"wp-block-heading\" id=\"h-building-and-pushing-once-an-extension-is-added\">Building and Pushing, Once an Extension Is Added<\/h3><p class=\"wp-block-paragraph\">To build a container image, set <code>quarkus.container-image.build=true<\/code> using whichever of these matches your setup:<\/p><p class=\"wp-block-paragraph\"><strong>CLI:<\/strong><\/p><p class=\"wp-block-paragraph\"><code>quarkus build<\/code><\/p><p class=\"wp-block-paragraph\"><strong>Maven:<\/strong><\/p><p class=\"wp-block-paragraph\"><code>.\/mvnw install -Dquarkus.container-image.build=true<\/code><\/p><p class=\"wp-block-paragraph\"><strong>Gradle:<\/strong><\/p><p class=\"wp-block-paragraph\"><code>.\/gradlew build -Dquarkus.container-image.build=true<\/code><\/p><p class=\"wp-block-paragraph\">If you already have a native image built and just want to rebuild the container around it, add <code>-Dquarkus.native.reuse-existing=true<\/code> and Quarkus skips re-running the native build.<\/p><p class=\"wp-block-paragraph\">To push the image, set <code>quarkus.container-image.push=true<\/code>. If you don&rsquo;t set a registry with <code>quarkus.container-image.registry<\/code>, Quarkus pushes to docker.io by default.<\/p><p class=\"wp-block-paragraph\">For Buildpacks, avoid setting quarkus.container-image.build=true permanently in application properties because it can trigger nested builds (builds inside builds). Pass the property on the build command instead. Pass it as a -D flag on the build command instead: <code>-Dquarkus.container-image.build=true<\/code> directly on the command line.<\/p><h2 class=\"wp-block-heading\" id=\"h-how-to-debug-a-quarkus-application-inside-a-container\">How to Debug a Quarkus Application Inside a Container<\/h2><p class=\"wp-block-paragraph\">Container debugging is separate from Live Coding. For a JVM build, start the application with the Java debug agent enabled, expose the debug port from the container, and map that port to the host so an IDE or debugger can attach.&nbsp;<\/p><p class=\"wp-block-paragraph\">Keep the port restricted to the development environment and avoid exposing it through a shared or public interface.<\/p><p class=\"wp-block-paragraph\">Native executables require a different workflow. Build the executable with debug symbols and use gdb or an equivalent native debugger; a production-stripped binary does not contain enough information for source-level debugging.<\/p><p class=\"wp-block-paragraph\">JVM-only tests may also need to be excluded from native or HTTP-only integration runs. Use Quarkus test annotations such as @DisabledOnIntegrationTest where a test depends on JVM-specific behavior.<\/p><h3 class=\"wp-block-heading\" id=\"h-how-to-run-a-live-coding-container-with-docker-compose\">How to Run a Live Coding Container with Docker Compose<\/h3><p class=\"wp-block-paragraph\">If you&rsquo;re already running other services locally, like a database or a message broker, Compose is a cleaner way to start the dev-mode container alongside them than a long <em>docker run<\/em> command. Here&rsquo;s a minimal <em>docker-compose.yml<\/em> for the setup above:<\/p><div class=\"wp-block-melonpan-block-code mbcode-theme-tomorrow_night mbcode-scheme-dark mbcode-padding_tb-40 mbcode-padding_lr-30\"><pre><code>services:\n  docker-live-coding:\n    build:\n      context: .\n      dockerfile: src\/main\/docker\/Dockerfile.dev\n    ports:\n      - \"8080:8080\"\n    environment:\n      QUARKUS_LAUNCH_DEVMODE: \"true\"<\/code><\/pre><\/div><p class=\"wp-block-paragraph\">Build the JAR first with <em>quarkus build<\/em> (or the Gradle or Maven equivalent), the same as before. Then start the stack with <em>docker compose up &ndash;build<\/em>, and connect with <em><code>.\/gradlew quarkusRemoteDev<\/code><\/em> (or the Maven equivalent) just like you would without Compose. The remote-dev connection still targets <em>localhost:8080<\/em>, whether Docker or Compose started the container.<\/p><h2 class=\"wp-block-heading\" id=\"h-how-to-build-and-run-a-native-quarkus-executable-in-docker\">How to Build and Run a Native Quarkus Executable in Docker<\/h2><p class=\"wp-block-paragraph\">A native executable is your Quarkus app compiled ahead of time with GraalVM into a standalone binary that skips the JVM entirely, giving you a much smaller image and near-instant startup.&nbsp;<\/p><p class=\"wp-block-paragraph\">The downside is a longer build, and you lose Live Coding along the way, so think of this as a separate workflow you reach for once you&rsquo;re getting closer to a production image, not something you use day-to-day.<\/p><p class=\"wp-block-paragraph\">You don&rsquo;t need GraalVM installed on your machine if you build inside a container instead:&nbsp;<\/p><p class=\"wp-block-paragraph\">Run <code>quarkus build --native --no-tests -Dquarkus.native.container-build=true<\/code> (or the Maven or Gradle equivalent), then build and run the generated Dockerfile.native the same way you already built and ran Dockerfile.jvm earlier in this guide.&nbsp;<\/p><p class=\"wp-block-paragraph\">Two things worth knowing before you try it:<\/p><ul class=\"wp-block-list\">\n<li>The executable you get is a 64-bit Linux binary, so if you&rsquo;re on macOS or Windows and you skip the container build. It won&rsquo;t run in a Linux container.&nbsp;<\/li>\n\n\n\n<li>Since Quarkus 3.19, the container build uses a UBI9-based builder image, so don&rsquo;t pair the result with a UBI8 base image in your Dockerfile. It won&rsquo;t run.<\/li>\n<\/ul><h2 class=\"wp-block-heading\" id=\"h-which-base-image-should-i-use\">Which Base Image Should I Use?<\/h2><p class=\"wp-block-paragraph\">The right base image depends on what you&rsquo;re deploying:<\/p><figure class=\"wp-block-table is-style-stripes\"><table class=\"has-fixed-layout\"><thead><tr><th><strong>Base image<\/strong><\/th><th><strong>Fits<\/strong><\/th><th><strong>Tradeoff<\/strong><\/th><\/tr><\/thead><tbody><tr><td>Standard UBI (<em>ubi9\/openjdk-25<\/em>)<\/td><td>JVM-mode apps, general use<\/td><td>Bigger image, but it has everything a JVM app needs already installed, so you won&rsquo;t hit missing-dependency errors<\/td><\/tr><tr><td>UBI Micro<\/td><td>Native executables<\/td><td>Small image that still has what native builds need; the default for <em>Dockerfile.native-micro<\/em><\/td><\/tr><tr><td>Distroless<\/td><td>Native executables, advanced use<\/td><td>No shell, smaller attack surface. Quarkus calls this experimental and says to test it thoroughly before using it in production<\/td><\/tr><tr><td>Scratch<\/td><td>Fully statically linked native executables,&nbsp; typically built with musl<\/td><td>Smallest image possible. Quarkus says not to use it in production without thorough testing, since anything that needs a system library at runtime, like a DNS lookup, can fail unless the binary is fully static<\/td><\/tr><\/tbody><\/table><\/figure><h2 class=\"wp-block-heading\" id=\"h-troubleshooting-live-coding-in-docker\">Troubleshooting Live Coding in Docker<\/h2><p class=\"wp-block-paragraph\">If Live Coding isn&rsquo;t working, check these first:<\/p><ul class=\"wp-block-list\">\n<li><strong>Dev mode won&rsquo;t activate:<\/strong> Check the container startup logs for Profile dev activated. Live Coding activated. If the logs show Profile prod activated, the <code>QUARKUS_LAUNCH_DEVMODE=true<\/code> environment variable isn&rsquo;t reaching the container. Confirm it&rsquo;s in the Dockerfile you actually built with, not left over in an unused one.<\/li>\n\n\n\n<li><strong>The main app reloads, but changes to a library module in the same project:<\/strong> If your project is multi-module (a separate library alongside your main app), <code>quarkusRemoteDev<\/code> can silently skip reloading the library even though local quarkus dev uses the same change fine. Quarkus logs a warning like Live reload was disabled for the following project artifacts: &hellip; The artifacts above appear to be either dependencies of non-reloadable application dependencies or Quarkus extensions.&nbsp;<\/li>\n\n\n\n<li><strong>Code changes aren&rsquo;t reflected after <code>quarkusRemoteDev<\/code> connects:<\/strong> Confirmer <code>quarkus.package.type=mutable-jar<\/code> was set at build time.&nbsp;If you built the JAR before adding that property, rebuild it. Also confirm you&rsquo;re editing the file in the project you actually connected from; quarkusRemoteDev syncs from the local project directory, not from inside the container.<\/li>\n<\/ul><h2 class=\"wp-block-heading\" id=\"h-validate-the-service-beyond-development\">Validate the Service Beyond Development<\/h2><p class=\"wp-block-paragraph\">Once the Docker development workflow is working, validate the service as it will run beyond development. Keep the dev profile, mutable JAR, and remote Live Coding connection out of production builds, then test the resulting image with production-like traffic and dependencies.<\/p><p class=\"wp-block-paragraph\">Live Coding confirms that source changes can be applied quickly during development. It does not show whether the deployed container will remain healthy, whether dependencies are creating latency, or whether resource pressure will affect users.<\/p><p class=\"wp-block-paragraph\"><a href=\"https:\/\/www.logicmonitor.com\/fr\">LogicMonitor<\/a> stands out by connecting those production signals in one operational view: container health and restarts, JVM memory and garbage collection, application response time and errors, host or cluster pressure, dependency latency, network-path performance, and deployment changes.&nbsp;<\/p><p class=\"wp-block-paragraph\">That cross-layer context helps teams move from an application symptom to the infrastructure or dependency that caused it, across cloud, container, and hybrid environments.<\/p><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50\">\n      <span class=\"head-icon\"><svg class=\"\" width=\"50px\" height=\"50px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-log-management-analytics\"><\/use>\n    <\/svg><\/span>\n  \n  <div class=\"rtc-text-content__wrapper\">\n          <h4 class=\"rtc-text-content__headline fs-sm-text-display-xxs fs-md-text-display-xs fs-lg-text-display-sm font-medium text-core-blue-900\">\n        LogicMonitor Supports Production Readiness      <\/h4>\n    \n          <div class=\"rtc-text-content__body fs-sm-text-md fs-md-text-lg fs-lg-text-lg text-core-blue-900\">\n        <p>Use LogicMonitor to carry visibility from deployment through production operation, with the context needed to identify performance issues before they become user-facing incidents.<\/p>\n      <\/div>\n    \n          \n      \n              <div>\n            <a href=\"\/book-a-demo%20\" class=\"btn btn-link\" target=\"_self\">\n        Explore LogicMonitor for Quarkus and container monitoring          <span class=\"icon-end\"><svg class=\"\" width=\"20px\" height=\"20px\" style=\"fill: #060F4B\">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-arrow-right\"><\/use>\n    <\/svg><\/span>\n      <\/a>\n        <\/div>\n            <\/div>\n<\/div><h4 id=\"h-faqs\" class=\"wp-block-heading\">FAQ<\/h4><div class=\"accordion-block accordion-block--light\">\n      <div class=\"accordion-block__items\">\n              <div class=\"accordion-block__item active\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-does-this-still-work-if-im-on-an-older-quarkus-version\">\n            Does This Still Work if I&rsquo;m on an Older Quarkus Version?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer active\">\n            <p><span style=\"font-weight: 400\">The Live Coding mechanism and the QUARKUS_LAUNCH_DEVMODE \/ mutable-jar \/ live-reload configuration have been stable since early Quarkus 2.x. The container-image extensions, Docker Compose approach, and native-build flags in this guide assume a current 3.x release; check the Quarkus migration guides if you&rsquo;re upgrading from 2.x.<br>\n<\/span><\/p>\n                      <\/div>\n        <\/div>\n              <div class=\"accordion-block__item\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-can-i-use-live-coding-with-kubernetes-or-openshift-not-just-local-docker\">\n            Can I Use Live Coding With Kubernetes or OpenShift, Not Just Local Docker?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer\">\n            <p><span style=\"font-weight: 400\"> Yes, Quarkus supports remote development against containers running in Kubernetes, Minikube, and OpenShift using the same underlying mechanism: dev mode, a mutable build, and a quarkusRemoteDev connection to a reachable URL.<br>\n<\/span><\/p>\n                      <\/div>\n        <\/div>\n              <div class=\"accordion-block__item\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-why-does-live-coding-not-work-in-docker-by-default\">\n             Why Does Live Coding Not Work in Docker by Default?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer\">\n            <p><span style=\"font-weight: 400\">Generated Dockerfiles are intended for production-style execution and start the application in the prod profile. Enable dev mode explicitly with QUARKUS_LAUNCH_DEVMODE=true, use a mutable JAR, and establish the quarkusRemoteDev connection.<br>\n<\/span><\/p>\n                      <\/div>\n        <\/div>\n              <div class=\"accordion-block__item\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-are-mutable-jar-and-live-coding-settings-safe-in-production\">\n            Are Mutable JAR and Live Coding Settings Safe in Production?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer\">\n            <p><span style=\"font-weight: 400\">No. Keep mutable-jar packaging, Live Coding passwords, and remote reload connections in a development-only profile. A standard production build should not include settings that allow a client to push code into a running process.<\/span><\/p>\n<p><\/p>\n                      <\/div>\n        <\/div>\n              <div class=\"accordion-block__item\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-what-should-i-check-when-quarkusremotedev-cannot-connect\">\n            What Should I Check When quarkusRemoteDev Cannot Connect?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer\">\n            <p><span style=\"font-weight: 400\">Confirm that the container is running in dev mode, the remote URL is reachable from the host, the Live Coding password matches, port 8080 is mapped correctly, and the JAR was rebuilt after mutable-jar was enabled. Check the container logs for the active profile and connection status.<br>\n<\/span><\/p>\n                      <\/div>\n        <\/div>\n              <div class=\"accordion-block__item\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-does-the-native-workflow-support-live-coding\">\n            Does the Native Workflow Support Live Coding?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer\">\n            <p><span style=\"font-weight: 400\">No, native builds are a separate packaging path for deployment-oriented testing and production preparation. Use JVM dev mode for Live Coding, then validate the native executable separately.<br>\n<\/span><\/p>\n                      <\/div>\n        <\/div>\n              <div class=\"accordion-block__item\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-do-i-need-a-current-quarkus-version-for-these-commands\">\n            Do I Need a Current Quarkus Version for These Commands?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer\">\n            <p><span style=\"font-weight: 400\">The core Live Coding workflow is available across multiple Quarkus generations, but the container-image extensions, Java baseline, Dockerfile templates, and native-build options change. Verify the commands against the Quarkus release and JDK version you plan to use.<br>\n<\/span><\/p>\n                      <\/div>\n        <\/div>\n          <\/div>\n  <\/div>","protected":false},"excerpt":{"rendered":"<p>Cr\u00e9ez une boucle de d\u00e9veloppement Quarkus plus rapide avec Docker : activez le Live Coding \u00e0 distance, rechargez instantan\u00e9ment les modifications de code et d\u00e9pannez les conteneurs avant la production.<\/p>","protected":false},"author":112,"featured_media":533231,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"unicorn_plugin_options_block_body_class":"","footnotes":""},"categories":[5035,5064],"tags":[5611,5800,5893],"industry":[6790],"role":[],"lm_strategic_tags":[],"topic":[],"author_attribution":[],"lm_product":[],"class_list":["post-533224","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","industry-all"],"acf":{"page_language":"english","translated_pages":"","updated_date":null,"author_section_checkbox":true,"author_image":"","author_linkedin":"","author_name":"","author_job_title":"","author_dept":"","author_bio":"","reviewer_name":""},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.4 (Yoast SEO v28.4) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Quarkus Live Coding in Docker: Remote Dev Guide - LogicMonitor<\/title>\n<meta name=\"description\" content=\"Explore Quarkus Live Coding in Docker, with remote development, mutable JARs, dev profiles, Compose, native builds, and debugging.\" \/>\n<meta name=\"robots\" content=\"noindex, nofollow\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to Use Quarkus Live Coding (Live Reload) in Docker\" \/>\n<meta property=\"og:description\" content=\"Explore Quarkus Live Coding in Docker, with remote development, mutable JARs, dev profiles, Compose, native builds, and debugging.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.logicmonitor.com\/fr\/blog\/how-to-use-quarkus-live-coding-in-docker\" \/>\n<meta property=\"og:site_name\" content=\"LogicMonitor\" \/>\n<meta property=\"article:published_time\" content=\"2026-09-02T21:44:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-09-04T19:57:25+00:00\" \/>\n<meta name=\"author\" content=\"zackary.wika@logicmonitor.com\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2022\/11\/549_EngineeringBlog_HowtoUseQuarkusLiveCodinginDocker_SocialGraphics_v1_Blog_1182x737.png\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"14 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/how-to-use-quarkus-live-coding-in-docker#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/how-to-use-quarkus-live-coding-in-docker\"},\"author\":{\"name\":\"zackary.wika@logicmonitor.com\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/2d4f89313dd368979b57d908e32847fc\"},\"headline\":\"How to Use Quarkus Live Coding (Live Reload) in Docker\",\"datePublished\":\"2026-09-02T21:44:00+00:00\",\"dateModified\":\"2026-09-04T19:57:25+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/how-to-use-quarkus-live-coding-in-docker\"},\"wordCount\":3078,\"image\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/how-to-use-quarkus-live-coding-in-docker#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2022\\\/11\\\/549_EngineeringBlog_HowtoUseQuarkusLiveCodinginDocker_SocialGraphics_v1_Blog_1182x737.png\",\"keywords\":[\"container monitoring\",\"docker\",\"engineering\"],\"articleSection\":[\"Blog\",\"Engineering\"],\"inLanguage\":\"fr-FR\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/how-to-use-quarkus-live-coding-in-docker\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/how-to-use-quarkus-live-coding-in-docker\",\"name\":\"Quarkus Live Coding in Docker: Remote Dev Guide - LogicMonitor\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/how-to-use-quarkus-live-coding-in-docker#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/how-to-use-quarkus-live-coding-in-docker#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2022\\\/11\\\/549_EngineeringBlog_HowtoUseQuarkusLiveCodinginDocker_SocialGraphics_v1_Blog_1182x737.png\",\"datePublished\":\"2026-09-02T21:44:00+00:00\",\"dateModified\":\"2026-09-04T19:57:25+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/2d4f89313dd368979b57d908e32847fc\"},\"description\":\"Explore Quarkus Live Coding in Docker, with remote development, mutable JARs, dev profiles, Compose, native builds, and debugging.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/how-to-use-quarkus-live-coding-in-docker#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/how-to-use-quarkus-live-coding-in-docker\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/how-to-use-quarkus-live-coding-in-docker#primaryimage\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2022\\\/11\\\/549_EngineeringBlog_HowtoUseQuarkusLiveCodinginDocker_SocialGraphics_v1_Blog_1182x737.png\",\"contentUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2022\\\/11\\\/549_EngineeringBlog_HowtoUseQuarkusLiveCodinginDocker_SocialGraphics_v1_Blog_1182x737.png\",\"width\":2463,\"height\":1536,\"caption\":\"How to Use Quarkus Live Coding in Docker\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/how-to-use-quarkus-live-coding-in-docker#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.logicmonitor.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Use Quarkus Live Coding (Live Reload) in Docker\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#website\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/\",\"name\":\"LogicMonitor\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/2d4f89313dd368979b57d908e32847fc\",\"name\":\"zackary.wika@logicmonitor.com\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Quarkus Live Coding in Docker: Remote Dev Guide - LogicMonitor","description":"Explore Quarkus Live Coding in Docker, with remote development, mutable JARs, dev profiles, Compose, native builds, and debugging.","robots":{"index":"noindex","follow":"nofollow"},"og_locale":"fr_FR","og_type":"article","og_title":"How to Use Quarkus Live Coding (Live Reload) in Docker","og_description":"Explore Quarkus Live Coding in Docker, with remote development, mutable JARs, dev profiles, Compose, native builds, and debugging.","og_url":"https:\/\/www.logicmonitor.com\/fr\/blog\/how-to-use-quarkus-live-coding-in-docker","og_site_name":"LogicMonitor","article_published_time":"2026-09-02T21:44:00+00:00","article_modified_time":"2026-09-04T19:57:25+00:00","author":"zackary.wika@logicmonitor.com","twitter_card":"summary_large_image","twitter_image":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2022\/11\/549_EngineeringBlog_HowtoUseQuarkusLiveCodinginDocker_SocialGraphics_v1_Blog_1182x737.png","twitter_misc":{"Written by":"","Est. reading time":"14 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/how-to-use-quarkus-live-coding-in-docker#article","isPartOf":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/how-to-use-quarkus-live-coding-in-docker"},"author":{"name":"zackary.wika@logicmonitor.com","@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/2d4f89313dd368979b57d908e32847fc"},"headline":"How to Use Quarkus Live Coding (Live Reload) in Docker","datePublished":"2026-09-02T21:44:00+00:00","dateModified":"2026-09-04T19:57:25+00:00","mainEntityOfPage":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/how-to-use-quarkus-live-coding-in-docker"},"wordCount":3078,"image":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/how-to-use-quarkus-live-coding-in-docker#primaryimage"},"thumbnailUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2022\/11\/549_EngineeringBlog_HowtoUseQuarkusLiveCodinginDocker_SocialGraphics_v1_Blog_1182x737.png","keywords":["container monitoring","docker","engineering"],"articleSection":["Blog","Engineering"],"inLanguage":"fr-FR"},{"@type":"WebPage","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/how-to-use-quarkus-live-coding-in-docker","url":"https:\/\/www.logicmonitor.com\/fr\/blog\/how-to-use-quarkus-live-coding-in-docker","name":"Quarkus Live Coding in Docker: Remote Dev Guide - LogicMonitor","isPartOf":{"@id":"https:\/\/www.logicmonitor.com\/fr\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/how-to-use-quarkus-live-coding-in-docker#primaryimage"},"image":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/how-to-use-quarkus-live-coding-in-docker#primaryimage"},"thumbnailUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2022\/11\/549_EngineeringBlog_HowtoUseQuarkusLiveCodinginDocker_SocialGraphics_v1_Blog_1182x737.png","datePublished":"2026-09-02T21:44:00+00:00","dateModified":"2026-09-04T19:57:25+00:00","author":{"@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/2d4f89313dd368979b57d908e32847fc"},"description":"Explore Quarkus Live Coding in Docker, with remote development, mutable JARs, dev profiles, Compose, native builds, and debugging.","breadcrumb":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/how-to-use-quarkus-live-coding-in-docker#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.logicmonitor.com\/fr\/blog\/how-to-use-quarkus-live-coding-in-docker"]}]},{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/how-to-use-quarkus-live-coding-in-docker#primaryimage","url":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2022\/11\/549_EngineeringBlog_HowtoUseQuarkusLiveCodinginDocker_SocialGraphics_v1_Blog_1182x737.png","contentUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2022\/11\/549_EngineeringBlog_HowtoUseQuarkusLiveCodinginDocker_SocialGraphics_v1_Blog_1182x737.png","width":2463,"height":1536,"caption":"How to Use Quarkus Live Coding in Docker"},{"@type":"BreadcrumbList","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/how-to-use-quarkus-live-coding-in-docker#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.logicmonitor.com\/"},{"@type":"ListItem","position":2,"name":"How to Use Quarkus Live Coding (Live Reload) in Docker"}]},{"@type":"WebSite","@id":"https:\/\/www.logicmonitor.com\/fr\/#website","url":"https:\/\/www.logicmonitor.com\/fr\/","name":"LogicMonitor","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.logicmonitor.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Person","@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/2d4f89313dd368979b57d908e32847fc","name":"zackary.wika@logicmonitor.com"}]}},"_links":{"self":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/533224","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/users\/112"}],"replies":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/comments?post=533224"}],"version-history":[{"count":4,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/533224\/revisions"}],"predecessor-version":[{"id":626403,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/533224\/revisions\/626403"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/media\/533231"}],"wp:attachment":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/media?parent=533224"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/categories?post=533224"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/tags?post=533224"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/industry?post=533224"},{"taxonomy":"role","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/role?post=533224"},{"taxonomy":"lm_strategic_tags","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/lm_strategic_tags?post=533224"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/topic?post=533224"},{"taxonomy":"author_attribution","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/author_attribution?post=533224"},{"taxonomy":"lm_product","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/lm_product?post=533224"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":619142,"date":"2026-09-01T12:26:24","date_gmt":"2026-09-01T17:26:24","guid":{"rendered":"https:\/\/www.logicmonitor.com\/?p=619142"},"modified":"2026-09-02T12:02:54","modified_gmt":"2026-09-02T17:02:54","slug":"the-1-million-lesson-building-a-culture-of-quality-through-slas","status":"publish","type":"post","link":"https:\/\/www.logicmonitor.com\/fr\/blog\/the-1-million-lesson-building-a-culture-of-quality-through-slas","title":{"rendered":"La le\u00e7on du \u00ab $1 Million \u00bb : instaurer une culture de la qualit\u00e9 gr\u00e2ce aux accords de niveau de service (SLA)"},"content":{"rendered":"<?xml encoding=\"UTF-8\"><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50 rtc-text-content--no-top-pad\">\n      <span class=\"head-icon\"><svg class=\"\" width=\"50px\" height=\"50px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-light-book-open\"><\/use>\n    <\/svg><\/span>\n  \n  <div class=\"rtc-text-content__wrapper\">\n          <h4 class=\"rtc-text-content__headline fs-sm-text-display-xs fs-md-text-display-sm fs-lg-text-display-md font-medium text-core-blue-900\">\n        Le t\u00e9l\u00e9chargement rapide :      <\/h4>\n    \n          <div class=\"rtc-text-content__body fs-sm-text-md fs-md-text-lg fs-lg-text-lg text-core-blue-900 headline-is-quote\">\n        <p>Never promise what you can&rsquo;t measure from the customer&rsquo;s point of view.<\/p>\n      <\/div>\n    \n                  <ul class=\"rtc-text-content__bullet-list\">\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>A single 100% uptime promise cost $1 million in penalties, because no system measured or managed the commitment behind it.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>SLAs stay honest when you measure outside-in, from where the customer sits, across many vantage points on the Internet path.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>Aligning external promises with internal targets gave legal, sales, finance, engineering, and ops one shared service language and one set of metrics.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>Grade your own SLA program against customer experience today, so you can see risk coming and act before a commitment breaks.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                  <\/ul>\n      \n      \n            <\/div>\n<\/div><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">In the early days of DoubleClick, back when SaaS was still known as Application Service Provider (ASP), I was tasked with setting up the QoS (Quality of Service) Team. Our primary mission was to establish a monitoring system, but we quickly found ourselves managing Service Level Agreements (SLAs), a task that became critical after we paid out over <strong>$1 million in penalties<\/strong> for SLA violations to a single customer. The cause was straightforward: someone had signed a contract promising <strong>100% uptime<\/strong>, an impossible commitment.<\/p><p class=\"wp-block-paragraph\">That penalty taught me a lesson I&rsquo;ve carried into every service I&rsquo;ve helped run since: never promise what you can&rsquo;t measure from the customer&rsquo;s point of view. A good SLA depends on measuring the service the way the user experiences it, from many vantage points, and correlating what you control against what you don&rsquo;t. That same principle sits at the center of how LogicMonitor approaches Autonomous IT today, and it&rsquo;s what makes the DoubleClick story worth revisiting as a case study for anyone running cloud and SaaS services now.<\/p><p class=\"wp-block-paragraph\">This is the story of how we took control of our SLAs, stopped the financial bleeding, and built a shared service language across legal, sales, finance, engineering, and operations. Whether you&rsquo;re managing SLAs today or just curious about how they work, this post walks through the challenges we faced, the solutions we built, and how each lesson maps to modern practice.<\/p><h2 id=\"h-what-are-slas\" class=\"wp-block-heading\">What are SLAs?<\/h2><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1600\" height=\"1066\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-7.jpeg\" alt=\"\" class=\"wp-image-619147\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-7.jpeg 1600w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-7-18x12.jpeg 18w\" sizes=\"auto, (max-width: 1600px) 100vw, 1600px\"><\/figure><p class=\"wp-block-paragraph\">An <strong>SLA (Service Level Agreement)<\/strong> is a contractual agreement between a vendor and a customer that outlines the expected level of service. Under this legal umbrella, you&rsquo;ll find <strong>Service Level Objectives (SLOs)<\/strong>, which define specific metrics like uptime, speed, or transactions per second.<\/p><p class=\"wp-block-paragraph\">At DoubleClick, we defined SLAs with the following principles in mind:<\/p><ul class=\"wp-block-list\">\n<li><strong>Attainable:<\/strong> The goals should be realistic.<\/li>\n\n\n\n<li><strong>Repeatable:<\/strong> The metrics should be consistently measurable.<\/li>\n\n\n\n<li><strong>Measurable:<\/strong> The performance should be quantifiable.<\/li>\n\n\n\n<li><strong>Meaningful:<\/strong> The metrics should matter to the business.<\/li>\n\n\n\n<li><strong>Mutually Acceptable:<\/strong> Both parties should agree on the terms.<\/li>\n<\/ul><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">SLAs benefit both the customer and the vendor. For customers, they provide <strong>objective grading criteria<\/strong> and protection from poor service. For vendors, they set clear expectations and incentivize quality improvements.<\/p><h2 id=\"h-ground-zero-discovery\" class=\"wp-block-heading\">Ground zero, discovery<\/h2><p class=\"wp-block-paragraph\">When we first tackled the SLA problem, we were in crisis mode. The first step was to compile a list of all contracts, extract the SLAs and SLOs, and document the associated penalties. We stored this information in a database and began educating stakeholders, including business leaders, legal teams, and executives, about the importance of SLAs.<\/p><p class=\"wp-block-paragraph\">From the beginning, we focused on <strong>end-user experience-based SLAs<\/strong>. This meant measuring performance from the user&rsquo;s perspective, not only from the server&rsquo;s perspective. That distinction is where many SLA programs still break down today. Internal dashboards tend to measure what teams control, such as server health, CPU, and internal service uptime, which isn&rsquo;t always what the customer actually experiences across the Internet path. A server can report healthy while the user sees timeouts, slow pages, or failed transactions. Measuring outside-in, from where the customer sits, is what keeps an SLA program honest.<\/p><h2 id=\"h-a-universal-challenge\" class=\"wp-block-heading\">A universal challenge<\/h2><p class=\"wp-block-paragraph\">Over the years, I&rsquo;ve seen many companies face similar issues. Some SRE and Dev teams don&rsquo;t fully grasp the SLAs their organization has with customers. They often focus heavily on internal SLOs while overlooking how those metrics tie directly to contractual commitments. For instance, after facing significant penalties, companies like<a href=\"https:\/\/www.techtarget.com\/searchunifiedcommunications\/news\/252470248\/Slack-waters-down-cloud-SLA-after-82-million-payout\"> Slack<\/a> revised their SLA terms to better align internal goals with customer promises.<\/p><h2 id=\"h-sla-application-performance\" class=\"wp-block-heading\">SLA application performance<\/h2><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1600\" height=\"524\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-8.jpeg\" alt=\"\" class=\"wp-image-619148\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-8.jpeg 1600w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-8-18x6.jpeg 18w\" sizes=\"auto, (max-width: 1600px) 100vw, 1600px\"><\/figure><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">Establishing an SLA is more than putting a few sentences in a contract. The reason we paid $1 million is that there was no SLA Management System in place. We started by building a Service Level Management (SLM) practice that relied on four pillars: Administration, Monitoring, Reporting, and Compliance (AMRC).<\/p><h2 id=\"h-the-slm-process\" class=\"wp-block-heading\">The SLM process<\/h2><p class=\"wp-block-paragraph\">We sat down with business partners, customers, legal, and finance teams to create a process that would prevent costly mistakes in the future. This process, which we called the SLA lifecycle, was reviewed quarterly to ensure it stayed effective and aligned with our business goals.<\/p><ol class=\"wp-block-list\">\n<li><strong>Risk simulations with data science:<\/strong> One of the most critical steps in our SLM process was using our in-house data scientists to run simulations. These simulations analyzed historical data from our monitoring tools to assess the risk of breaching SLAs. The goal was to set realistic SLAs that wouldn&rsquo;t be breached every day, while still meeting customer expectations.<\/li>\n\n\n\n<li><strong>&ldquo;What-if&rdquo; scenarios:<\/strong> We also ran multiple &ldquo;what-if&rdquo; scenarios to understand the relationship between availability and revenue. These scenarios helped us evaluate the impact of downtime at different hours of the day and days of the week. For example, we could see how a 10-minute outage during peak traffic hours would affect revenue compared to the same outage during off-peak times.<\/li>\n\n\n\n<li><strong>The SLA desk:<\/strong> To streamline the process, we created an online tool in 2001, essentially an &ldquo;SLA desk,&rdquo; that allowed our sales team to request SLA portfolios for customers. These requests were reviewed and approved by our QoS team, ensuring that every SLA was realistic, measurable, and aligned with our capabilities.<\/li>\n<\/ol><h2 id=\"h-aligning-external-and-internal-slas\" class=\"wp-block-heading\">Aligning external and internal SLAs<\/h2><p class=\"wp-block-paragraph\">One of the biggest challenges we faced was the mismatch between external SLAs (what we promised customers) and internal SLAs (what we measured internally). For example, customers would ask for ad-serving uptime, while our tech team measured server availability.<\/p><p class=\"wp-block-paragraph\">To solve this, we aligned our external and internal SLOs and made the internal objectives (the targets) very high. This was a huge victory because it let us rely on one set of metrics to understand our SLA risk position and drive operational excellence. Our tech group (Ops, Engineering, and others) also became more sensitive to the notion of a business SLA and started to care a lot about not breaching them. In modern cloud and SaaS terms, this is the practice of tying your internal SLOs and error budgets directly to the customer-facing commitments in the contract, so one signal serves both the on-call engineer and the account team.<\/p><h2 id=\"h-monitoring-the-key-to-sla-success\" class=\"wp-block-heading\">Monitoring, the key to SLA success<\/h2><p class=\"wp-block-paragraph\">For availability and performance, we relied on three synthetic products. Internally, we ran Sitescope, at the time an early synthetic and infrastructure monitoring tool, across 17 data centers, and used two external synthetic products. We wanted as many data points as possible from as many tools as possible. The stakes were just too high not to invest in multiple tools. This entire SLM project wasn&rsquo;t cheap to implement and run on an annual basis, but I also knew the cost of not doing it right the hard way.<\/p><p class=\"wp-block-paragraph\">For monitoring, it became clear we needed to test as often as possible from as many vantage points as possible:<\/p><ul class=\"wp-block-list\">\n<li>Infrequent checks distort the picture. If you only test your SLO endpoints once an hour, a short outage inside that 59-minute gap can be missed entirely, and a longer one can have its duration measured inaccurately, which erodes confidence in the reported numbers when you sit down with a customer.<\/li>\n\n\n\n<li>You also need many data points to ensure statistical significance. Smaller datasets lower precision and power, while larger ones help manage false positives and false negatives.<\/li>\n<\/ul><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">Today that instinct translates into a concrete standard: measure from a global set of vantage points, test frequently enough to catch short outages, and gather enough samples for the numbers to be statistically credible when a contract is on the line. LM Internet Performance Monitoring measures experience from a global network of vantage points, which closes the kind of blind spots a single internal check leaves open.<\/p><h2 id=\"h-enter-differential-performance-measurement-dpm\" class=\"wp-block-heading\">Enter Differential Performance Measurement (DPM)<\/h2><p class=\"wp-block-paragraph\">One of our biggest challenges was finding an effective way to measure ad delivery speed and capture it in our SLAs. Clients would look at their site performance, notice spikes, and attribute them to our system, while our performance telemetry showed no problems. We couldn&rsquo;t correlate the two charts, so we couldn&rsquo;t agree on whether it was our problem or someone else&rsquo;s problem.<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"800\" height=\"274\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-5.jpeg\" alt=\"\" class=\"wp-image-619145\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-5.jpeg 800w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-5-18x6.jpeg 18w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\"><\/figure><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"800\" height=\"268\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-4.jpeg\" alt=\"\" class=\"wp-image-619144\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-4.jpeg 800w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-4-18x6.jpeg 18w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\"><\/figure><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">To address this, we developed a methodology called <a href=\"https:\/\/contracts.onecle.com\/ask\/doubleclick.svc.2004.02.27.shtml\">Differential Performance Measurement<\/a> (DPM). Our goal was to measure DoubleClick&rsquo;s performance and availability with precision, and to understand how it affected our customers&rsquo; pages. We also wanted to be accountable for what we controlled, so we could avoid blame and finger-pointing.<\/p><p class=\"wp-block-paragraph\">The methodology added context to the measurements. DPM introduced clarity and comparison, removing absolute performance numbers from the SLAs. Looking back, DPM was an early version of a principle that modern observability now takes for granted: isolate the performance you&rsquo;re responsible for from the external noise around it, so you can hold yourself accountable for your part and measure it cleanly.<\/p><p class=\"wp-block-paragraph\"><strong>Recipe for Differential Performance Measurement (example with an advert):<\/strong><\/p><ol class=\"wp-block-list\">\n<li>Take two pages, one without ads and one with a single ad call.<\/li>\n<\/ol><ul class=\"wp-block-list\">\n<li>Page A = No ads<\/li>\n\n\n\n<li>Page B = One ad<\/li>\n<\/ul><ol start=\"2\" class=\"wp-block-list\">\n<li>Make sure the pages don&rsquo;t contain any other third-party references (CDNs, and so on).<\/li>\n\n\n\n<li>Make sure the page sizes (in KB) are the same.<\/li>\n\n\n\n<li>&ldquo;Bake&rdquo;: Measure response times for both pages and you get the following metrics:<\/li>\n<\/ol><ul class=\"wp-block-list\">\n<li><strong>Differential Response<\/strong> (DR) will be (Response Time of page B) minus (Response Time of page A).<\/li>\n\n\n\n<li><strong>Differential Response Percentage<\/strong> (DRP) = DR \/ A. (For example, if Page A is 2 seconds and Page B is 2.1 seconds, DR is 0.1 second, and DRP is 0.1\/2 = 0.05 or 5%.)<\/li>\n<\/ul><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">This approach helped eliminate noise caused by:<\/p><ol class=\"wp-block-list\">\n<li>Internet-related issues beyond our control (for example, fiber cuts).<\/li>\n\n\n\n<li>Monitoring agent inconsistencies (raising the need to monitor our monitoring tools).<\/li>\n\n\n\n<li>Other third-party dependencies.<\/li>\n<\/ol><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">To visualize the impact of Differential Performance Measurement (DPM), the chart below compares response times for two scenarios.<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"800\" height=\"409\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-6.jpeg\" alt=\"\" class=\"wp-image-619146\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-6.jpeg 800w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-6-18x9.jpeg 18w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\"><\/figure><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\"><strong>Sc\u00e9nario 1 :<\/strong> The ad-serving company experienced performance issues, which negatively impacted the customer&rsquo;s site. The vendor breached the SLA threshold between Time 4 and Time 8.<\/p><p class=\"wp-block-paragraph\"><strong>Sc\u00e9nario 2 :<\/strong> The website itself encountered performance problems, unrelated to the ad-serving company.<\/p><h2 id=\"h-reporting-transparency-and-accountability\" class=\"wp-block-heading\">Reporting, transparency and accountability<\/h2><p class=\"wp-block-paragraph\">After the $1 million penalty, SLA management became a top priority, with visibility extending all the way to the CEO. We reported monthly on compliance and breaches, using tools like DigitalFuel, a service-level reporting tool we used at the time, to detect issues in real time.<\/p><p class=\"wp-block-paragraph\">By the end of 2001, we were tracking over 100 Operational Level Agreements (OLAs), and a culture of quality had emerged at DoubleClick. The biggest change came from people rather than tools. Engineers, executives, sales, legal, and finance all started speaking the same service language, grading themselves against the same business metrics, and no one wanted to be the reason we breached an SLA. That shared language is what made the numbers mean something across the company.<\/p><h2 id=\"h-lessons-learned-and-the-road-ahead\" class=\"wp-block-heading\">Lessons learned and the road ahead<\/h2><p class=\"wp-block-paragraph\">Implementing a comprehensive SLM process at DoubleClick allowed us to:<\/p><ul class=\"wp-block-list\">\n<li><strong>Manage hundreds of contracts<\/strong> with up to five SLOs each.<\/li>\n\n\n\n<li><strong>Offer scalable SLAs<\/strong> that could adapt to new products.<\/li>\n\n\n\n<li><strong>Reduce financial risks<\/strong> by avoiding costly penalties.<\/li>\n\n\n\n<li><strong>Maintain our reputation<\/strong> by providing accurate and meaningful SLAs.<\/li>\n\n\n\n<li><strong>Detect breaches in real time<\/strong>, allowing us to take proactive measures.<\/li>\n<\/ul><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">One of the biggest advantages was knowing in advance when an SLA was at risk. For example, we could predict that adding four minutes of downtime would breach 12 contracts and result in $X in penalties. That kind of foresight changed operational decisions: our Ops team could pause a release, hold a change, or reroute traffic before a breach became revenue lost and customer trust spent.<\/p><p class=\"wp-block-paragraph\">The hard part in 2001 was that these signals lived in different places. SLA risk sat in one database, infrastructure health in the monitoring tools, Internet conditions in the synthetic products, and customer experience in whatever the client happened to report. Stitching them together took people and time. Correlating them in one system is what <a href=\"https:\/\/www.logicmonitor.com\/fr\/edwin-ai\">LogicMonitor<\/a> does today.<\/p><p class=\"wp-block-paragraph\"><a href=\"https:\/\/www.logicmonitor.com\/fr\/infrastructure-monitoring\">LM Envision<\/a> provides the telemetry foundation across hybrid infrastructure, cloud, and applications, <a href=\"https:\/\/www.logicmonitor.com\/fr\/internet-performance-monitoring\">LogicMonitor Synthetics and Internet Performance Monitoring<\/a> show what users experience across the Internet path, and <a href=\"https:\/\/www.logicmonitor.com\/fr\/edwin-ai\">Edwin AI<\/a> reasons across those signals to prioritize by business impact and turn correlation into governed, prioritized action.<\/p><p class=\"wp-block-paragraph\">Put together, that means a team can see SLA risk, the infrastructure driving it, the Internet dependencies around it, and the user impact behind it in one view, and act on it before a commitment is broken.<\/p><p class=\"wp-block-paragraph\">The business case for getting this right hasn&rsquo;t changed since our $1 million lesson. A missed SLA is revenue exposure, eroded customer trust, and a broken legal and commercial commitment, all at once. Measuring service from the customer&rsquo;s point of view is what lets a team protect all three at the same time.<\/p><p class=\"wp-block-paragraph\">Some people dismiss SLAs, and in many cases that skepticism is justified. Bad SLAs, the ones with unrealistic guarantees, no real penalties, or vague measurement criteria, undermine trust. I often see SLAs promising 0% packet loss, but when you ask how it&rsquo;s measured, you quickly realize it&rsquo;s meaningless. These kinds of SLAs give the entire concept a bad reputation.<\/p><p class=\"wp-block-paragraph\">When done right, SLAs are essential. They align customers and vendors, reduce friction, and eliminate blame games. Customers need to demand useful SLAs that hold up in practice, rather than ones that only sound good on paper. The goal is to hold vendors accountable so that if they fail to deliver, they feel the impact.<\/p><h2 id=\"h-what-every-sla-and-slo-program-should-measure-today\" class=\"wp-block-heading\">What every SLA and SLO program should measure today<\/h2><p class=\"wp-block-paragraph\">If I were setting up a QoS practice now, this is the short list I&rsquo;d hold every SLA and SLO program to:<\/p><ul class=\"wp-block-list\">\n<li><strong>Availability and uptime:<\/strong> measured from where the customer sits, not only at the server.<\/li>\n\n\n\n<li><strong>Temps de latence :<\/strong> response times for the interactions that matter to the user.<\/li>\n\n\n\n<li><strong>Transaction success:<\/strong> whether real user actions complete, not just whether endpoints respond.<\/li>\n\n\n\n<li><strong>Third-party dependencies:<\/strong> the CDNs, APIs, and services you rely on but don&rsquo;t control.<\/li>\n\n\n\n<li><strong>Internet path health:<\/strong> the network conditions between your service and the customer.<\/li>\n\n\n\n<li><strong>User-impact signals:<\/strong> who is affected, where, and how badly, so you can tie technical health to business risk.<\/li>\n<\/ul><p class=\"wp-block-paragraph\"><\/p><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50\">\n  \n  <div class=\"rtc-text-content__wrapper\">\n    \n          <div class=\"rtc-text-content__body fs-sm-text-md fs-md-text-lg fs-lg-text-lg text-core-blue-900\">\n        <p>Building or fixing an SLA program? Start with the fundamentals and modern best practices.<\/p>\n      <\/div>\n    \n          \n      \n              <div>\n            <a href=\"https:\/\/www.logicmonitor.com\/blog\/implementing-slas-slis-and-slos\" class=\"btn btn-link\" target=\"_self\">\n        Read the SLA, SLI, and SLO guide          <span class=\"icon-end\"><svg class=\"\" width=\"20px\" height=\"20px\" style=\"fill: #060F4B\">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-arrow-right\"><\/use>\n    <\/svg><\/span>\n      <\/a>\n        <\/div>\n            <\/div>\n<\/div><h2 id=\"h-the-evolution-of-slas\" class=\"wp-block-heading\">The evolution of SLAs<\/h2><p class=\"wp-block-paragraph\">Back in 2001, we knew SLA management was critical, but few of us could have predicted how integral it would become in today&rsquo;s cloud-driven world. SLAs have evolved from simple uptime guarantees to complex agreements that cover everything from latency to data residency. XLOs (Experience Level Objectives) are a thing now, metrics that focus on the customer&rsquo;s experience rather than only the server&rsquo;s performance. That shift, from internal metrics to customer outcomes, is exactly the lesson the $1 million penalty forced on us more than two decades ago.<\/p><p class=\"wp-block-paragraph\">The takeaway holds for any team running services today: a good SLA is only as good as your ability to measure it the way the customer feels it. Honoring service commitments means correlating SLA risk, infrastructure health, Internet dependencies, and user experience in one place, and acting on that picture before a breach happens. If you&rsquo;re building or fixing an SLA program now, start with the fundamentals and the modern practice around them.<\/p><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50\">\n      <span class=\"head-icon\"><svg class=\"\" width=\"50px\" height=\"50px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-light-calendar-check\"><\/use>\n    <\/svg><\/span>\n  \n  <div class=\"rtc-text-content__wrapper\">\n          <h4 class=\"rtc-text-content__headline fs-sm-text-display-xxs fs-md-text-display-xs fs-lg-text-display-sm font-medium text-core-blue-900\">\n        See your SLA risk from the customer's point of view before a commitment breaks.      <\/h4>\n    \n          <div class=\"rtc-text-content__body fs-sm-text-md fs-md-text-lg fs-lg-text-lg text-core-blue-900\">\n        <p>LogicMonitor brings SLA risk, the infrastructure that drives it, Internet dependencies, and user impact into a single view, so your team can act while there&rsquo;s still time to protect the commitment.<\/p>\n      <\/div>\n    \n          \n      \n              <div>\n            <a href=\"https:\/\/www.logicmonitor.com\/catchpoint-demo\" class=\"btn btn-link\" target=\"_self\">\n        Demander une d\u00e9monstration          <span class=\"icon-end\"><svg class=\"\" width=\"20px\" height=\"20px\" style=\"fill: #060F4B\">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-arrow-right\"><\/use>\n    <\/svg><\/span>\n      <\/a>\n        <\/div>\n            <\/div>\n<\/div><h4 id=\"h-faqs\" class=\"wp-block-heading\">FAQ<\/h4><div class=\"accordion-block accordion-block--light\">\n      <div class=\"accordion-block__items\">\n              <div class=\"accordion-block__item active\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-why-is-a-100-uptime-sla-a-problem\">\n            Why is a 100% uptime SLA a problem?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer active\">\n            <p> A 100% uptime guarantee promises something no service can measure or sustain across the real Internet path. At DoubleClick, that single promise led to more than $1 million in penalties. A strong SLA sets goals that are attainable, repeatable, measurable, meaningful, and mutually acceptable.<\/p>\n                      <\/div>\n        <\/div>\n              <div class=\"accordion-block__item\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-what-does-it-mean-to-measure-an-sla-from-the-customers-point-of-view\">\n            What does it mean to measure an SLA from the customer's point of view?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer\">\n            <p>It means measuring the service the way the user experiences it, not only from the server. A server can report healthy while the customer sees timeouts, slow pages, or failed transactions. Measuring outside-in, from a global set of vantage points and often enough to catch short outages, keeps the reported numbers credible when a contract is on the line.<\/p>\n                      <\/div>\n        <\/div>\n              <div class=\"accordion-block__item\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-how-does-logicmonitor-help-teams-manage-sla-risk-today\">\n            How does LogicMonitor help teams manage SLA risk today?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer\">\n            <p>LM Envision provides the telemetry foundation across hybrid infrastructure, cloud, and applications. LogicMonitor Synthetics and Internet Performance Monitoring show what users experience across the Internet path. Edwin AI reasons across those signals and prioritizes by business impact. Together, teams see SLA risk, its infrastructure, Internet dependencies, and user impact in one view and act before a breach happens.<\/p>\n                      <\/div>\n        <\/div>\n          <\/div>\n  <\/div>","protected":false},"excerpt":{"rendered":"<p>Une seule p\u00e9nalit\u00e9 li\u00e9e au SLA de type \u00ab $1M \u00bb nous a enseign\u00e9 une r\u00e8gle fondamentale : \u00e9valuer la qualit\u00e9 du service en fonction de la perception qu&#x27;en ont vos clients. Voici comment \u00e9laborer des SLA fiables qui prot\u00e8gent votre chiffre d&#x27;affaires.<\/p>","protected":false},"author":16,"featured_media":623735,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"unicorn_plugin_options_block_body_class":"","footnotes":""},"categories":[5035],"tags":[7850,7777,7760,7752,7863,6677,7862,7018,7860,7883],"industry":[6790],"role":[6783],"lm_strategic_tags":[],"topic":[7842],"author_attribution":[7976],"lm_product":[],"class_list":["post-619142","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","industry-all","role-it-leadership","topic-internet-performance-monitoring","author_attribution-mehdi-daoudi"],"acf":{"page_language":"english","translated_pages":"","updated_date":null,"author_section_checkbox":true,"author_image":617027,"author_linkedin":"https:\/\/www.linkedin.com\/in\/denton-chikura-422186201\/","author_name":"Denton Chikura","author_job_title":"Technical Writer","author_dept":"","author_bio":"Denton Chikura is a technical writer and longtime observability advocate focused on helping site reliability engineers and engineering teams discover the tools and capabilities that strengthen internet resilience. He works at the intersection of monitoring, performance, and infrastructure to make complex systems more understandable and usable, bridging the gap between deep technical detail and real\u2011world operations. His goal is to help teams build faster, detect issues earlier, and recover smarter, ultimately making the internet a better, more reliable place for everyone.","reviewer_name":""},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.4 (Yoast SEO v28.4) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>The $1 Million SLA Lesson: Build a Culture of Quality | LogicMonitor<\/title>\n<meta name=\"description\" content=\"Learn how a structured approach to SLA management can drive accountability, improve service quality, and prevent costly penalties while aligning teams on key metrics.\" \/>\n<meta name=\"robots\" content=\"noindex, nofollow\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"The $1 Million Lesson: Building a Culture of Quality Through SLAs\" \/>\n<meta property=\"og:description\" content=\"Learn how a structured approach to SLA management can drive accountability, improve service quality, and prevent costly penalties while aligning teams on key metrics.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.logicmonitor.com\/fr\/blog\/the-1-million-lesson-building-a-culture-of-quality-through-slas\" \/>\n<meta property=\"og:site_name\" content=\"LogicMonitor\" \/>\n<meta property=\"article:published_time\" content=\"2026-09-01T17:26:24+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-09-02T17:02:54+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Blog_The-1-Million-Lesson_-Building-a-Culture-of-Quality-Through-SLAs_1600x900_MetaTag.png\" \/>\n\t<meta property=\"og:image:width\" content=\"2400\" \/>\n\t<meta property=\"og:image:height\" content=\"1350\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"destiny.setzer@logicmonitor.com\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"13 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/the-1-million-lesson-building-a-culture-of-quality-through-slas#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/the-1-million-lesson-building-a-culture-of-quality-through-slas\"},\"author\":{\"name\":\"destiny.setzer@logicmonitor.com\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\"},\"headline\":\"The $1 Million Lesson: Building a Culture of Quality Through SLAs\",\"datePublished\":\"2026-09-01T17:26:24+00:00\",\"dateModified\":\"2026-09-02T17:02:54+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/the-1-million-lesson-building-a-culture-of-quality-through-slas\"},\"wordCount\":2491,\"image\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/the-1-million-lesson-building-a-culture-of-quality-through-slas#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/Blog_The-1-Million-Lesson_-Building-a-Culture-of-Quality-Through-SLAs_940x600_Featured-Image.png\",\"keywords\":[\"Catchpoint\",\"Edwin\",\"Incident Response\",\"LM Envision\",\"Network Path Analysis\",\"Performance optimization\",\"SLA Monitoring\",\"synthetics\",\"User Experience\",\"Web Performance\"],\"articleSection\":[\"Blog\"],\"inLanguage\":\"fr-FR\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/the-1-million-lesson-building-a-culture-of-quality-through-slas\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/the-1-million-lesson-building-a-culture-of-quality-through-slas\",\"name\":\"The $1 Million SLA Lesson: Build a Culture of Quality | LogicMonitor\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/the-1-million-lesson-building-a-culture-of-quality-through-slas#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/the-1-million-lesson-building-a-culture-of-quality-through-slas#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/Blog_The-1-Million-Lesson_-Building-a-Culture-of-Quality-Through-SLAs_940x600_Featured-Image.png\",\"datePublished\":\"2026-09-01T17:26:24+00:00\",\"dateModified\":\"2026-09-02T17:02:54+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\"},\"description\":\"Learn how a structured approach to SLA management can drive accountability, improve service quality, and prevent costly penalties while aligning teams on key metrics.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/the-1-million-lesson-building-a-culture-of-quality-through-slas#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/the-1-million-lesson-building-a-culture-of-quality-through-slas\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/the-1-million-lesson-building-a-culture-of-quality-through-slas#primaryimage\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/Blog_The-1-Million-Lesson_-Building-a-Culture-of-Quality-Through-SLAs_940x600_Featured-Image.png\",\"contentUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/Blog_The-1-Million-Lesson_-Building-a-Culture-of-Quality-Through-SLAs_940x600_Featured-Image.png\",\"width\":1410,\"height\":900},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/the-1-million-lesson-building-a-culture-of-quality-through-slas#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.logicmonitor.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"The $1 Million Lesson: Building a Culture of Quality Through SLAs\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#website\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/\",\"name\":\"LogicMonitor\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\",\"name\":\"destiny.setzer@logicmonitor.com\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"The $1 Million SLA Lesson: Build a Culture of Quality | LogicMonitor","description":"Learn how a structured approach to SLA management can drive accountability, improve service quality, and prevent costly penalties while aligning teams on key metrics.","robots":{"index":"noindex","follow":"nofollow"},"og_locale":"fr_FR","og_type":"article","og_title":"The $1 Million Lesson: Building a Culture of Quality Through SLAs","og_description":"Learn how a structured approach to SLA management can drive accountability, improve service quality, and prevent costly penalties while aligning teams on key metrics.","og_url":"https:\/\/www.logicmonitor.com\/fr\/blog\/the-1-million-lesson-building-a-culture-of-quality-through-slas","og_site_name":"LogicMonitor","article_published_time":"2026-09-01T17:26:24+00:00","article_modified_time":"2026-09-02T17:02:54+00:00","og_image":[{"width":2400,"height":1350,"url":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Blog_The-1-Million-Lesson_-Building-a-Culture-of-Quality-Through-SLAs_1600x900_MetaTag.png","type":"image\/png"}],"author":"destiny.setzer@logicmonitor.com","twitter_card":"summary_large_image","twitter_misc":{"Written by":"","Est. reading time":"13 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/the-1-million-lesson-building-a-culture-of-quality-through-slas#article","isPartOf":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/the-1-million-lesson-building-a-culture-of-quality-through-slas"},"author":{"name":"destiny.setzer@logicmonitor.com","@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def"},"headline":"The $1 Million Lesson: Building a Culture of Quality Through SLAs","datePublished":"2026-09-01T17:26:24+00:00","dateModified":"2026-09-02T17:02:54+00:00","mainEntityOfPage":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/the-1-million-lesson-building-a-culture-of-quality-through-slas"},"wordCount":2491,"image":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/the-1-million-lesson-building-a-culture-of-quality-through-slas#primaryimage"},"thumbnailUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Blog_The-1-Million-Lesson_-Building-a-Culture-of-Quality-Through-SLAs_940x600_Featured-Image.png","keywords":["Catchpoint","Edwin","Incident Response","LM Envision","Network Path Analysis","Performance optimization","SLA Monitoring","synthetics","User Experience","Web Performance"],"articleSection":["Blog"],"inLanguage":"fr-FR"},{"@type":"WebPage","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/the-1-million-lesson-building-a-culture-of-quality-through-slas","url":"https:\/\/www.logicmonitor.com\/fr\/blog\/the-1-million-lesson-building-a-culture-of-quality-through-slas","name":"The $1 Million SLA Lesson: Build a Culture of Quality | LogicMonitor","isPartOf":{"@id":"https:\/\/www.logicmonitor.com\/fr\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/the-1-million-lesson-building-a-culture-of-quality-through-slas#primaryimage"},"image":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/the-1-million-lesson-building-a-culture-of-quality-through-slas#primaryimage"},"thumbnailUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Blog_The-1-Million-Lesson_-Building-a-Culture-of-Quality-Through-SLAs_940x600_Featured-Image.png","datePublished":"2026-09-01T17:26:24+00:00","dateModified":"2026-09-02T17:02:54+00:00","author":{"@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def"},"description":"Learn how a structured approach to SLA management can drive accountability, improve service quality, and prevent costly penalties while aligning teams on key metrics.","breadcrumb":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/the-1-million-lesson-building-a-culture-of-quality-through-slas#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.logicmonitor.com\/fr\/blog\/the-1-million-lesson-building-a-culture-of-quality-through-slas"]}]},{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/the-1-million-lesson-building-a-culture-of-quality-through-slas#primaryimage","url":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Blog_The-1-Million-Lesson_-Building-a-Culture-of-Quality-Through-SLAs_940x600_Featured-Image.png","contentUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Blog_The-1-Million-Lesson_-Building-a-Culture-of-Quality-Through-SLAs_940x600_Featured-Image.png","width":1410,"height":900},{"@type":"BreadcrumbList","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/the-1-million-lesson-building-a-culture-of-quality-through-slas#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.logicmonitor.com\/"},{"@type":"ListItem","position":2,"name":"The $1 Million Lesson: Building a Culture of Quality Through SLAs"}]},{"@type":"WebSite","@id":"https:\/\/www.logicmonitor.com\/fr\/#website","url":"https:\/\/www.logicmonitor.com\/fr\/","name":"LogicMonitor","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.logicmonitor.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Person","@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def","name":"destiny.setzer@logicmonitor.com"}]}},"_links":{"self":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/619142","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/users\/16"}],"replies":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/comments?post=619142"}],"version-history":[{"count":4,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/619142\/revisions"}],"predecessor-version":[{"id":623970,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/619142\/revisions\/623970"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/media\/623735"}],"wp:attachment":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/media?parent=619142"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/categories?post=619142"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/tags?post=619142"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/industry?post=619142"},{"taxonomy":"role","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/role?post=619142"},{"taxonomy":"lm_strategic_tags","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/lm_strategic_tags?post=619142"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/topic?post=619142"},{"taxonomy":"author_attribution","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/author_attribution?post=619142"},{"taxonomy":"lm_product","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/lm_product?post=619142"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":619150,"date":"2026-09-01T12:26:10","date_gmt":"2026-09-01T17:26:10","guid":{"rendered":"https:\/\/www.logicmonitor.com\/?p=619150"},"modified":"2026-09-03T15:20:12","modified_gmt":"2026-09-03T20:20:12","slug":"critical-requirements-for-modern-api-monitoring","status":"publish","type":"post","link":"https:\/\/www.logicmonitor.com\/fr\/blog\/critical-requirements-for-modern-api-monitoring","title":{"rendered":"Exigences critiques pour la surveillance des API modernes"},"content":{"rendered":"<?xml encoding=\"UTF-8\"><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50 rtc-text-content--no-top-pad\">\n      <span class=\"head-icon\"><svg class=\"\" width=\"50px\" height=\"50px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-light-book-open\"><\/use>\n    <\/svg><\/span>\n  \n  <div class=\"rtc-text-content__wrapper\">\n          <h4 class=\"rtc-text-content__headline fs-sm-text-display-xs fs-md-text-display-sm fs-lg-text-display-md font-medium text-core-blue-900\">\n        Le t\u00e9l\u00e9chargement rapide :      <\/h4>\n    \n          <div class=\"rtc-text-content__body fs-sm-text-md fs-md-text-lg fs-lg-text-lg text-core-blue-900 headline-is-quote\">\n        <p>API resilience requires end-to-end visibility across the full Internet path, from the user all the way to the code.<\/p>\n      <\/div>\n    \n                  <ul class=\"rtc-text-content__bullet-list\">\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>Modern systems depend on hundreds of API calls per transaction, and a single misbehaving dependency can degrade or break the entire service.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>Traditional monitoring tools run from cloud servers and miss real-world issues like ISP congestion, geographic routing differences, and last-mile conditions.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>Internet Performance Monitoring surfaces the full Internet stack (DNS, SSL, routing, authentication) so teams can pinpoint root cause, not just detect symptoms.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>Evaluate your current API monitoring against the resilience formula: reachability, availability, performance, and reliability across every dependency.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                  <\/ul>\n      \n      \n            <\/div>\n<\/div><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">Enterprises lose millions each year to API outages and performance degradation. As systems grow more distributed and interconnected, monitoring APIs from the server side alone isn&rsquo;t enough. Real resilience requires visibility across the full Internet path, from the user all the way to the code.<\/p><p class=\"wp-block-paragraph\">Today, nearly every system depends on APIs. Data integration, authentication, payment processing, and dozens of other critical functions rely on multiple APIs working reliably and fast. Banks around the world, for example, have adopted the <a href=\"https:\/\/stripe.com\/resources\/more\/open-banking-apis-explained-what-they-are-and-how-they-work\">Open Banking API<\/a> for payments, credit scoring, lending origination, fraud detection, and more.<\/p><h2 id=\"h-apis-are-everywhere-and-critical-to-everything\" class=\"wp-block-heading\">APIs are everywhere, and critical to everything<\/h2><p class=\"wp-block-paragraph\">APIs are the internal workers of the Internet. Connecting to a single website, using a business application like an ATM, or opening a mobile app likely triggers dozens (if not hundreds or thousands) of API calls. Each one can affect the overall service: if it&rsquo;s slow, the service slows down. If it returns an error, the service may fail entirely.<\/p><p class=\"wp-block-paragraph\">Understanding the interaction between your services and the APIs they consume is critical to making those services resilient.<\/p><p class=\"wp-block-paragraph\">There are different ways to monitor APIs. At minimum, every system should proactively monitor, measure, and test its critical APIs, both internal and third-party. <a href=\"https:\/\/www.logicmonitor.com\/catchpoint\/api-monitoring\">API monitoring systems<\/a> have been around for some time, ranging from basic pings that confirm reachability to advanced multi-step, scripted, proactive monitoring that evaluates response time, functional validation, and more. The most mature approaches incorporate chaos engineering methodologies: blocking or simulating errors on specific APIs and observing the impact on the broader system.<\/p><h2 id=\"h-why-api-resilience-matters\" class=\"wp-block-heading\">Why API resilience matters<\/h2><p class=\"wp-block-paragraph\">Most applications and systems that communicate via APIs are geographically distributed, touching different clouds and traversing multiple points across the Internet. Simple proactive monitoring is no longer sufficient. A traditional approach to API monitoring will miss important incidents and won&rsquo;t help identify root cause.<\/p><p class=\"wp-block-paragraph\">The goal is to have <em>resilient APIs<\/em>. The <a href=\"https:\/\/www.logicmonitor.com\/fr\/internet-performance-monitoring\">formula for resilience<\/a> breaks down into four components:<\/p><ul class=\"wp-block-list\">\n<li><strong>Reachability:<\/strong> Can consumers reach the API from where they are?<\/li>\n\n\n\n<li><strong>Disponibilit\u00e9 :<\/strong> Is the API functional? Does it do what it&rsquo;s supposed to do?<\/li>\n\n\n\n<li><strong>Performance :<\/strong> Does the API respond within expected timeframes?<\/li>\n\n\n\n<li><strong>Fiabilit\u00e9 :<\/strong> Can consumers trust the API will work consistently?<\/li>\n<\/ul><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">Now apply that formula to every API in your system. Your system&rsquo;s overall resilience equals the minimum resilience across all the APIs it depends on.<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"606\" height=\"124\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-63.png\" alt=\"\" class=\"wp-image-619153\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-63.png 606w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-63-18x4.png 18w\" sizes=\"auto, (max-width: 606px) 100vw, 606px\"><\/figure><p class=\"wp-block-paragraph\">Here&rsquo;s what that looks like in practice:<\/p><p class=\"wp-block-paragraph\"><em>A system with 100 API dependencies that requires five nines of availability must achieve five nines from each individual API. Resilient architecture can tolerate individual API failures without degrading the overall service, but that tolerance has to be deliberately designed and verified.<\/em><\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"530\" height=\"490\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-64.png\" alt=\"\" class=\"wp-image-619154\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-64.png 530w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-64-13x12.png 13w\" sizes=\"auto, (max-width: 530px) 100vw, 530px\"><\/figure><p class=\"wp-block-paragraph\"><em>Figure 1: One misbehaving dependency can make your whole system fail<\/em><\/p><p class=\"wp-block-paragraph\">With that goal in mind, let&rsquo;s look at what API monitoring actually requires.<\/p><h2 id=\"h-what-a-foundational-api-monitoring-strategy-should-include\" class=\"wp-block-heading\">What a foundational API monitoring strategy should include<\/h2><p class=\"wp-block-paragraph\">These are the baseline capabilities every API monitoring strategy needs. They help teams detect issues, confirm availability, and validate performance at a basic operational level.<\/p><ul class=\"wp-block-list\">\n<li><strong>Temps de r\u00e9ponse :<\/strong> Measures how long an API takes to respond, helping identify latency issues.<\/li>\n\n\n\n<li><strong>Taux d'erreur :<\/strong> Tracks the percentage of failed requests to detect anomalies or bugs.<\/li>\n\n\n\n<li><strong>D\u00e9bit :<\/strong> Monitors the number of API requests processed over a specific period to confirm scalability.<\/li>\n\n\n\n<li><strong>Uptime and availability:<\/strong> Confirms APIs are consistently reachable and operational.<\/li>\n\n\n\n<li><strong>Logging:<\/strong> Collects detailed logs of API events, including timestamps, event types (errors, warnings), and messages to support troubleshooting and post-incident analysis.<\/li>\n\n\n\n<li><strong>Alerts:<\/strong> Triggers notifications based on predefined thresholds or anomalies (for example, response time exceeding 200ms or error rates surpassing 5%).<\/li>\n\n\n\n<li><strong>Functional testing:<\/strong> Verifies that API endpoints return expected results.<\/li>\n\n\n\n<li><strong>CI\/CD integration:<\/strong> Integrates monitoring into pipelines and tools like <a href=\"https:\/\/www.jenkins.io\/\">Jenkins<\/a> ou <a href=\"https:\/\/www.terraform.io\/\">Terraform<\/a> for automated test creation and updates, also known as &ldquo;monitoring as code.&rdquo;<\/li>\n\n\n\n<li><strong>Proactive monitoring:<\/strong> Uses synthetic mechanisms to continuously observe API performance and detect issues as they occur.<\/li>\n\n\n\n<li><strong>Scripting:<\/strong> Supports scripting standards such as Playwright to test specific customer and API flows.<\/li>\n\n\n\n<li><strong>Historic data:<\/strong> Retains a minimum of 13 months of data to enable year-over-year performance comparisons.<\/li>\n\n\n\n<li><strong>High-cardinality data analysis:<\/strong> Analyzes granular data points such as unique user IDs or session-specific information for detailed insights into performance trends or anomalies.<\/li>\n\n\n\n<li><strong>Chaos engineering:<\/strong> Introduces controlled errors during low-traffic periods or in non-production environments to verify resilience.<\/li>\n<\/ul><h2 id=\"h-modern-api-monitoring-across-the-full-internet-path\" class=\"wp-block-heading\">Modern API monitoring across the full Internet path<\/h2><p class=\"wp-block-paragraph\">Today&rsquo;s systems demand more than basic uptime checks or response metrics. Modern API monitoring must account for real-world complexity: geography, infrastructure, user experience, and external dependencies. These capabilities go beyond the basics to provide deep, actionable insight.<\/p><ul class=\"wp-block-list\">\n<li><strong>Monitor from where it matters:<\/strong> Most monitoring tools run agents on cloud servers, which have different connectivity, resources, and bandwidth than real-world systems. They&rsquo;re blind to geographic differences in routing, ISP congestion, and last-mile conditions. Effective monitoring requires <a href=\"https:\/\/www.logicmonitor.com\/fr\/internet-performance-monitoring\">agents deployed across every location where a system consumes an API<\/a>, using agents with similar characteristics to actual consumers. For example, you might test your full application from customer-facing APIs using last-mile agents, test intermediate microservices from the cloud provider where they&rsquo;re hosted, and test back-end APIs from a backbone agent in the city and ISP where your datacenter is located (or from an enterprise agent inside the datacenter itself).<\/li>\n\n\n\n<li><strong>Visibility into the Internet Stack:<\/strong> Knowing <em>quand<\/em> an API is unresponsive or slow is useful. Understanding <em>pourquoi<\/em> is more powerful. Modern API monitoring provides insight into everything in the internet stack that affects an API, including DNS resolution, SSL, routing, and more. It also surfaces the latency and performance impact introduced by internal networks, SASE implementations, or gateways. Tools like <a href=\"https:\/\/www.logicmonitor.com\/catchpoint\/internet-stack-map\">Carte de la pile Internet<\/a> provide a visual representation of these dependencies, making it faster to pinpoint where degradation originates.<\/li>\n<\/ul><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"2475\" height=\"1370\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/FIGURE-3_-Internet-Stack.png\" alt=\"\" class=\"wp-image-621526\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/FIGURE-3_-Internet-Stack.png 2475w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/FIGURE-3_-Internet-Stack-18x10.png 18w\" sizes=\"auto, (max-width: 2475px) 100vw, 2475px\"><\/figure><p class=\"wp-block-paragraph\">The internet stack is the collection of technologies, systems, and services that make possible and impact every digital user experience, from the core Internet systems like BGP, network technologies like TCP\/IP, security technologies like SASE, protocols like QUIC or POP, cloud services, third-party dependencies including APIs and web services, and SaaS applications. The term refers to all IP-based networks including the public Internet, private networks, and everything in between.<\/p><ul class=\"wp-block-list\">\n<li><strong>Authentication:<\/strong> No modern monitoring system should have hard-coded credentials for a secure API. Monitoring tools must support secrets management, OAuth, tokens, and modern authentication mechanisms.<\/li>\n\n\n\n<li><strong>Synthetic code tracing:<\/strong> As an API is tested, the system collects and analyzes code execution traces to identify server-side issues, including application, connectivity, and database problems.<\/li>\n\n\n\n<li><strong>OpenTelemetry support:<\/strong> Modern observability implementations must support OTel as the standard mechanism for sharing and integrating data from multiple systems, providing flexibility across the telemetry stack.<\/li>\n\n\n\n<li><strong>Focus on user experience:<\/strong> An API is only one component of a broader system. A payment API, for example, is part of an online purchase transaction. You want to confirm the entire transaction performs from the end-user perspective. Tools like Internet Stack Map offer a <a href=\"https:\/\/www.logicmonitor.com\/catchpoint\/internet-stack-map\">visual map of every dependency in the user transaction<\/a>, from the end user across the Internet, network, systems, and APIs, all the way into code tracing.<\/li>\n\n\n\n<li><strong>Broad protocol support:<\/strong> While many APIs use REST over HTTP, your monitoring system should test from both IPv4 and IPv6 agents and support modern protocols like HTTP\/3 and QUIC, MQTT for IoT applications, NTP for time synchronization, or even custom and proprietary protocols your applications use.<\/li>\n<\/ul><h2 id=\"h-traditional-vs-modern-api-monitoring-at-a-glance\" class=\"wp-block-heading\">Traditional vs. modern API monitoring at a glance<\/h2><p class=\"wp-block-paragraph\">The following table summarizes the key differences between legacy API monitoring approaches and modern Internet Performance Monitoring strategies that support resilience and user experience.<\/p><figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>Fonctionnalit\u00e9<\/strong><\/td><td><strong>Traditional API Monitoring<\/strong><\/td><td><strong>Modern API Monitoring (Internet Performance Monitoring)<\/strong><\/td><\/tr><tr><td><strong>Champ d'application<\/strong><\/td><td>Server-centric metrics<\/td><td>End-to-end user experience + infrastructure<\/td><\/tr><tr><td><strong>Protocol Support<\/strong><\/td><td>Limited to HTTP\/S, REST<\/td><td>HTTP\/3, QUIC, MQTT, custom protocols<\/td><\/tr><tr><td><strong>Data Granularity<\/strong><\/td><td>High-cardinality data available but often limited to service boundaries<\/td><td>High-cardinality traces with cross-system correlation (user IDs, sessions)<\/td><\/tr><tr><td><strong>Analyse des causes profondes<\/strong><\/td><td>Limited to app\/server layers<\/td><td>Full Internet Stack (DNS, SSL, routing, etc.)<\/td><\/tr><tr><td><strong>Testing Perspective<\/strong><\/td><td>Cloud datacenters<\/td><td>Last mile, backbone, cloud, wireless, and enterprise intelligent agents<\/td><\/tr><tr><td><strong>Performance Context<\/strong><\/td><td>API performance in the context of code<\/td><td>API performance in the context of user experience<\/td><\/tr><tr><td><strong>Alerting Methodology<\/strong><\/td><td>Alert thresholds based on error rates<\/td><td>Experience scores and XLOs<\/td><\/tr><tr><td><strong>Visualization<\/strong><\/td><td>Code-centric dashboards<\/td><td>Visual representation of everything impacting a system<\/td><\/tr><\/tbody><\/table><\/figure><h2 id=\"h-api-monitoring-has-to-evolve-with-your-architecture\" class=\"wp-block-heading\">API monitoring has to evolve with your architecture<\/h2><p class=\"wp-block-paragraph\">It&rsquo;s somewhat surprising that the cloud is only about 15 years old. As technology and system architecture have evolved, monitoring must evolve with them, including how we approach APIs.<\/p><p class=\"wp-block-paragraph\">What we call &ldquo;owned&rdquo; or &ldquo;on-premises&rdquo; infrastructure today typically lives in a colocation datacenter, relies on a DNS and SSL provider, connects through at least two ISPs, depends on a cloud-based authentication system, routes through a cloud-based security provider, and calls several other APIs along the way.<\/p><p class=\"wp-block-paragraph\">Operations teams hear it constantly: &ldquo;My APM system shows green, but users keep complaining.&rdquo; A monitoring system that only watches your on-premises APIs can&rsquo;t spot, diagnose, or provide useful root-cause information for incidents that originate outside your environment.<\/p><p class=\"wp-block-paragraph\">This is where LogicMonitor&rsquo;s approach to <a href=\"https:\/\/www.logicmonitor.com\/fr\/internet-performance-monitoring\">Supervision des performances Internet<\/a> changes the equation. By combining <a href=\"https:\/\/www.logicmonitor.com\/fr\/infrastructure-monitoring\">LM Envision&rsquo;s<\/a> infrastructure telemetry with Internet path visibility and <a href=\"https:\/\/www.logicmonitor.com\/fr\/edwin-ai\">Edwin AI&rsquo;s<\/a> intelligence layer, teams get a unified view that stretches from user to code. That means faster root cause identification, fewer blind spots, and the ability to move from reactive firefighting toward proactive, governed operations.<\/p><p class=\"wp-block-paragraph\">To ensure API resilience, enterprises need monitoring that provides end-to-end visibility across the full Internet path, proactive alerting based on real user impact, and the intelligence to act on issues before they become outages.<\/p><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50\">\n      <span class=\"head-icon\"><svg class=\"\" width=\"50px\" height=\"50px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-light-calendar-check\"><\/use>\n    <\/svg><\/span>\n  \n  <div class=\"rtc-text-content__wrapper\">\n          <h4 class=\"rtc-text-content__headline fs-sm-text-display-xxs fs-md-text-display-xs fs-lg-text-display-sm font-medium text-core-blue-900\">\n        See how end-to-end Internet Performance Monitoring strengthens your API resilience.      <\/h4>\n    \n          <div class=\"rtc-text-content__body fs-sm-text-md fs-md-text-lg fs-lg-text-lg text-core-blue-900\">\n        <p>LogicMonitor combines infrastructure telemetry with full Internet path visibility and Edwin AI intelligence, giving your team a unified view from user to code. Move from reactive firefighting to proactive, governed operations.<\/p>\n      <\/div>\n    \n          \n      \n              <div>\n            <a href=\"https:\/\/www.logicmonitor.com\/catchpoint-demo\" class=\"btn btn-link\" target=\"_self\">\n        Demander une d\u00e9monstration          <span class=\"icon-end\"><svg class=\"\" width=\"20px\" height=\"20px\" style=\"fill: #060F4B\">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-arrow-right\"><\/use>\n    <\/svg><\/span>\n      <\/a>\n        <\/div>\n            <\/div>\n<\/div><h4 id=\"h-faqs\" class=\"wp-block-heading\">FAQ<\/h4><div class=\"accordion-block accordion-block--light\">\n      <div class=\"accordion-block__items\">\n              <div class=\"accordion-block__item active\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-what-is-the-difference-between-traditional-api-monitoring-and-internet-performance-monitoring\">\n            What is the difference between traditional API monitoring and Internet Performance Monitoring?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer active\">\n            <p> Traditional API monitoring focuses on server-side metrics like response time and error rates from cloud-based agents. Internet Performance Monitoring extends visibility across the full Internet path, including DNS, SSL, routing, and last-mile conditions, providing actionable insight into why an API is slow or unreachable.<\/p>\n                      <\/div>\n        <\/div>\n              <div class=\"accordion-block__item\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-why-do-cloud-based-monitoring-agents-miss-real-world-api-issues\">\n            Why do cloud-based monitoring agents miss real-world API issues?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer\">\n            <p>Cloud agents have different connectivity, resources, and bandwidth than actual end users. They cannot detect geographic routing differences, ISP congestion, or last-mile degradation. Deploying agents across real consumer locations gives a more accurate picture of API performance.<\/p>\n                      <\/div>\n        <\/div>\n              <div class=\"accordion-block__item\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-what-are-the-four-components-of-api-resilience\">\n            What are the four components of API resilience?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer\">\n            <p>API resilience breaks down into reachability (can consumers reach the API), availability (does it function correctly), performance (does it respond within expected timeframes), and reliability (does it work consistently). A system&rsquo;s overall resilience equals the minimum resilience across all its API dependencies.<\/p>\n                      <\/div>\n        <\/div>\n          <\/div>\n  <\/div>","protected":false},"excerpt":{"rendered":"<p>D\u00e9couvrez pourquoi la surveillance des API c\u00f4t\u00e9 serveur s'av\u00e8re insuffisante et comment la surveillance des performances Internet offre la visibilit\u00e9 de bout en bout qu'exigent les syst\u00e8mes modernes.<\/p>","protected":false},"author":16,"featured_media":623756,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"unicorn_plugin_options_block_body_class":"","footnotes":""},"categories":[5035],"tags":[5348,5446,7850,7823,7760,7906,6633,7854,6677,7866,7860],"industry":[6790],"role":[6786],"lm_strategic_tags":[],"topic":[7842],"author_attribution":[7967],"lm_product":[],"class_list":["post-619150","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","industry-all","role-itops","topic-internet-performance-monitoring","author_attribution-denton-chikura"],"acf":{"page_language":"english","translated_pages":"","updated_date":null,"author_section_checkbox":true,"author_image":617027,"author_linkedin":"https:\/\/www.linkedin.com\/in\/denton-chikura-422186201\/","author_name":"Denton Chikura","author_job_title":"Technical Writer","author_dept":"","author_bio":"Denton Chikura is a technical writer and longtime observability advocate focused on helping site reliability engineers and engineering teams discover the tools and capabilities that strengthen internet resilience. He works at the intersection of monitoring, performance, and infrastructure to make complex systems more understandable and usable, bridging the gap between deep technical detail and real\u2011world operations. His goal is to help teams build faster, detect issues earlier, and recover smarter, ultimately making the internet a better, more reliable place for everyone.","reviewer_name":""},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.4 (Yoast SEO v28.4) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Critical Requirements for Modern API Monitoring | LogicMonitor<\/title>\n<meta name=\"description\" content=\"Learn why traditional API monitoring isn&#039;t enough\u2014and how modern, user-focused, Internet Performance Monitoring helps ensure API resilience and performance.\" \/>\n<meta name=\"robots\" content=\"noindex, nofollow\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Critical Requirements for Modern API Monitoring\" \/>\n<meta property=\"og:description\" content=\"Learn why traditional API monitoring isn&#039;t enough\u2014and how modern, user-focused, Internet Performance Monitoring helps ensure API resilience and performance.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.logicmonitor.com\/fr\/blog\/critical-requirements-for-modern-api-monitoring\" \/>\n<meta property=\"og:site_name\" content=\"LogicMonitor\" \/>\n<meta property=\"article:published_time\" content=\"2026-09-01T17:26:10+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-09-03T20:20:12+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/09\/Blog_Critical-Requirements-for-Modern-API-Monitoring_Meta-1600x900px.png\" \/>\n\t<meta property=\"og:image:width\" content=\"2400\" \/>\n\t<meta property=\"og:image:height\" content=\"1350\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"destiny.setzer@logicmonitor.com\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/critical-requirements-for-modern-api-monitoring#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/critical-requirements-for-modern-api-monitoring\"},\"author\":{\"name\":\"destiny.setzer@logicmonitor.com\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\"},\"headline\":\"Critical Requirements for Modern API Monitoring\",\"datePublished\":\"2026-09-01T17:26:10+00:00\",\"dateModified\":\"2026-09-03T20:20:12+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/critical-requirements-for-modern-api-monitoring\"},\"wordCount\":1574,\"image\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/critical-requirements-for-modern-api-monitoring#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Blog_Critical-Requirements-for-Modern-API-Monitoring_940x600_Featured-Image.png\",\"keywords\":[\"api monitoring\",\"business education\",\"Catchpoint\",\"dns-monitoring\",\"Incident Response\",\"Internet Stack Map\",\"opentelemetry\",\"Outage Detection\",\"Performance optimization\",\"Synthetic Monitoring\",\"User Experience\"],\"articleSection\":[\"Blog\"],\"inLanguage\":\"fr-FR\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/critical-requirements-for-modern-api-monitoring\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/critical-requirements-for-modern-api-monitoring\",\"name\":\"Critical Requirements for Modern API Monitoring | LogicMonitor\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/critical-requirements-for-modern-api-monitoring#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/critical-requirements-for-modern-api-monitoring#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Blog_Critical-Requirements-for-Modern-API-Monitoring_940x600_Featured-Image.png\",\"datePublished\":\"2026-09-01T17:26:10+00:00\",\"dateModified\":\"2026-09-03T20:20:12+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\"},\"description\":\"Learn why traditional API monitoring isn't enough\u2014and how modern, user-focused, Internet Performance Monitoring helps ensure API resilience and performance.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/critical-requirements-for-modern-api-monitoring#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/critical-requirements-for-modern-api-monitoring\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/critical-requirements-for-modern-api-monitoring#primaryimage\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Blog_Critical-Requirements-for-Modern-API-Monitoring_940x600_Featured-Image.png\",\"contentUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Blog_Critical-Requirements-for-Modern-API-Monitoring_940x600_Featured-Image.png\",\"width\":1410,\"height\":900},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/critical-requirements-for-modern-api-monitoring#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.logicmonitor.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Critical Requirements for Modern API Monitoring\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#website\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/\",\"name\":\"LogicMonitor\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\",\"name\":\"destiny.setzer@logicmonitor.com\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Critical Requirements for Modern API Monitoring | LogicMonitor","description":"Learn why traditional API monitoring isn't enough\u2014and how modern, user-focused, Internet Performance Monitoring helps ensure API resilience and performance.","robots":{"index":"noindex","follow":"nofollow"},"og_locale":"fr_FR","og_type":"article","og_title":"Critical Requirements for Modern API Monitoring","og_description":"Learn why traditional API monitoring isn't enough\u2014and how modern, user-focused, Internet Performance Monitoring helps ensure API resilience and performance.","og_url":"https:\/\/www.logicmonitor.com\/fr\/blog\/critical-requirements-for-modern-api-monitoring","og_site_name":"LogicMonitor","article_published_time":"2026-09-01T17:26:10+00:00","article_modified_time":"2026-09-03T20:20:12+00:00","og_image":[{"width":2400,"height":1350,"url":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/09\/Blog_Critical-Requirements-for-Modern-API-Monitoring_Meta-1600x900px.png","type":"image\/png"}],"author":"destiny.setzer@logicmonitor.com","twitter_card":"summary_large_image","twitter_misc":{"Written by":"","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/critical-requirements-for-modern-api-monitoring#article","isPartOf":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/critical-requirements-for-modern-api-monitoring"},"author":{"name":"destiny.setzer@logicmonitor.com","@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def"},"headline":"Critical Requirements for Modern API Monitoring","datePublished":"2026-09-01T17:26:10+00:00","dateModified":"2026-09-03T20:20:12+00:00","mainEntityOfPage":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/critical-requirements-for-modern-api-monitoring"},"wordCount":1574,"image":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/critical-requirements-for-modern-api-monitoring#primaryimage"},"thumbnailUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/Blog_Critical-Requirements-for-Modern-API-Monitoring_940x600_Featured-Image.png","keywords":["api monitoring","business education","Catchpoint","dns-monitoring","Incident Response","Internet Stack Map","opentelemetry","Outage Detection","Performance optimization","Synthetic Monitoring","User Experience"],"articleSection":["Blog"],"inLanguage":"fr-FR"},{"@type":"WebPage","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/critical-requirements-for-modern-api-monitoring","url":"https:\/\/www.logicmonitor.com\/fr\/blog\/critical-requirements-for-modern-api-monitoring","name":"Critical Requirements for Modern API Monitoring | LogicMonitor","isPartOf":{"@id":"https:\/\/www.logicmonitor.com\/fr\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/critical-requirements-for-modern-api-monitoring#primaryimage"},"image":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/critical-requirements-for-modern-api-monitoring#primaryimage"},"thumbnailUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/Blog_Critical-Requirements-for-Modern-API-Monitoring_940x600_Featured-Image.png","datePublished":"2026-09-01T17:26:10+00:00","dateModified":"2026-09-03T20:20:12+00:00","author":{"@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def"},"description":"Learn why traditional API monitoring isn't enough\u2014and how modern, user-focused, Internet Performance Monitoring helps ensure API resilience and performance.","breadcrumb":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/critical-requirements-for-modern-api-monitoring#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.logicmonitor.com\/fr\/blog\/critical-requirements-for-modern-api-monitoring"]}]},{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/critical-requirements-for-modern-api-monitoring#primaryimage","url":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/Blog_Critical-Requirements-for-Modern-API-Monitoring_940x600_Featured-Image.png","contentUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/Blog_Critical-Requirements-for-Modern-API-Monitoring_940x600_Featured-Image.png","width":1410,"height":900},{"@type":"BreadcrumbList","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/critical-requirements-for-modern-api-monitoring#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.logicmonitor.com\/"},{"@type":"ListItem","position":2,"name":"Critical Requirements for Modern API Monitoring"}]},{"@type":"WebSite","@id":"https:\/\/www.logicmonitor.com\/fr\/#website","url":"https:\/\/www.logicmonitor.com\/fr\/","name":"LogicMonitor","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.logicmonitor.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Person","@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def","name":"destiny.setzer@logicmonitor.com"}]}},"_links":{"self":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/619150","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/users\/16"}],"replies":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/comments?post=619150"}],"version-history":[{"count":3,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/619150\/revisions"}],"predecessor-version":[{"id":623972,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/619150\/revisions\/623972"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/media\/623756"}],"wp:attachment":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/media?parent=619150"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/categories?post=619150"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/tags?post=619150"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/industry?post=619150"},{"taxonomy":"role","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/role?post=619150"},{"taxonomy":"lm_strategic_tags","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/lm_strategic_tags?post=619150"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/topic?post=619150"},{"taxonomy":"author_attribution","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/author_attribution?post=619150"},{"taxonomy":"lm_product","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/lm_product?post=619150"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":619195,"date":"2026-09-01T12:24:24","date_gmt":"2026-09-01T17:24:24","guid":{"rendered":"https:\/\/www.logicmonitor.com\/?p=619195"},"modified":"2026-09-02T12:02:55","modified_gmt":"2026-09-02T17:02:55","slug":"zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response","status":"publish","type":"post","link":"https:\/\/www.logicmonitor.com\/fr\/blog\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response","title":{"rendered":"Panne Zendesk : Un plaidoyer pour une surveillance proactive et une r\u00e9solution d'incidents plus rapide"},"content":{"rendered":"<?xml encoding=\"UTF-8\"><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50\">\n      <span class=\"head-icon\"><svg class=\"\" width=\"50px\" height=\"50px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-light-book-open\"><\/use>\n    <\/svg><\/span>\n  \n  <div class=\"rtc-text-content__wrapper\">\n          <h4 class=\"rtc-text-content__headline fs-sm-text-display-xs fs-md-text-display-sm fs-lg-text-display-md font-medium text-core-blue-900\">\n        Le t\u00e9l\u00e9chargement rapide :      <\/h4>\n    \n          <div class=\"rtc-text-content__body fs-sm-text-md fs-md-text-lg fs-lg-text-lg text-core-blue-900 headline-is-quote\">\n        <p>Independent, proactive monitoring is what separates teams that catch third-party outages early from teams that scramble to explain them.<\/p>\n      <\/div>\n    \n                  <ul class=\"rtc-text-content__bullet-list\">\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>Internet Sonar flagged the Zendesk outage 21 minutes before Zendesk&rsquo;s own internal alerts fired.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>Delayed root cause analysis cost businesses lost revenue, frustrated customers, and hours of manual workarounds as intermittent errors dragged on past 24 hours.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>Multi-pod architectures add scalability but also hidden dependencies that can turn one failure into a cascading, cross-region disruption.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>Give your team independent visibility into your internet stack so you can act on third-party incidents before they escalate.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                  <\/ul>\n      \n      \n            <\/div>\n<\/div><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">On <strong>March 20, 2025<\/strong>, starting at <strong>15:43 AM UTC<\/strong>, Zendesk users globally encountered 503 &ldquo;Service Unavailable&rdquo; errors and 5xx server-side issues, disrupting access to critical support tools and communication channels. While immediate mitigations stabilized core services, intermittent issues continued for over 24 hours, underscoring the complexity of multi-pod infrastructure failures.<\/p><p class=\"wp-block-paragraph\"><strong>Timeline of Events<\/strong><\/p><ul class=\"wp-block-list\">\n<li><strong>15:29 AM UTC<\/strong>: Zendesk&rsquo;s internal team confirmed user reports of access issues.<\/li>\n\n\n\n<li><strong>15:50 AM UTC<\/strong>: Root cause identified as widespread 503 errors impacting multiple service pods.<\/li>\n\n\n\n<li><strong>March 21, 2025, 10:59 PM UTC<\/strong> (06:29 AM EDT): Zendesk&rsquo;s status page confirmed recovery of &ldquo;majority of issues,&rdquo; with ongoing efforts to resolve lingering intermittent failures.<\/li>\n<\/ul><p class=\"wp-block-paragraph\"><\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1118\" height=\"666\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-82.png\" alt=\"\" class=\"wp-image-619198\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-82.png 1118w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-82-18x12.png 18w\" sizes=\"auto, (max-width: 1118px) 100vw, 1118px\"><\/figure><p class=\"wp-block-paragraph\">Error message on accessing Zendesk services<\/p><p class=\"wp-block-paragraph\">The 503 Service Unavailable responses were not immediately recognized as the root cause of the disruption. This delay hindered Zendesk&rsquo;s ability to fully understand the scope and impact of the outage in a timely manner and slowed the process of restoring service and assisting customers.<\/p><h2 id=\"h-when-zendesk-went-down-businesses-felt-the-impact\" class=\"wp-block-heading\">When Zendesk went down, businesses felt the impact<\/h2><p class=\"wp-block-paragraph\">The Zendesk outage disrupted workflows for thousands of businesses relying on the platform for customer support, sales, and internal collaboration. With critical processes offline, teams struggled to deliver timely and effective customer service. Here are some of the key consequences.<\/p><h3 id=\"h-1-access-issues-across-multiple-pods\" class=\"wp-block-heading\">#1 Access issues across multiple pods<\/h3><p class=\"wp-block-paragraph\">Many users encountered 5xx errors, which indicated problems on the server side. Users across industries (from retail to healthcare) were abruptly locked out of Zendesk portals. Support teams couldn&rsquo;t view tickets, update cases, or access customer history.<\/p><h3 id=\"h-2-service-degradation\" class=\"wp-block-heading\">#2 Service degradation<\/h3><p class=\"wp-block-paragraph\">Some services needed additional time to restart, leading to intermittent errors, often at the worst possible moments for businesses trying to handle customer inquiries. Support agents wrestled with inconsistent access and were forced to pause or redo tasks.<\/p><h3 id=\"h-3-impact-on-communication-channels\" class=\"wp-block-heading\">#3 Impact on communication channels<\/h3><p class=\"wp-block-paragraph\">Zendesk&rsquo;s core support tools went offline for large sections of the outage, limiting response times and workflow coordination. Web widgets used on company websites for direct customer engagement also went down, frustrating users who expected immediate assistance or quick self-service options.<\/p><h3 id=\"h-4-prolonged-resolution-window\" class=\"wp-block-heading\">#4 Prolonged resolution window<\/h3><p class=\"wp-block-paragraph\">Even though Zendesk reported &ldquo;majority of services&rdquo; were restored by March 21, intermittent errors lingered for more than 24 hours. This likely forced businesses to switch to manual processes.<\/p><h2 id=\"h-how-internet-performance-monitoring-identified-the-outage-before-zendesk-did\" class=\"wp-block-heading\">How Internet Performance Monitoring identified the outage before Zendesk did<\/h2><p class=\"wp-block-paragraph\"><a href=\"https:\/\/www.logicmonitor.com\/catchpoint\/internet-health\">Internet Sonar<\/a>, an Internet Performance Monitoring tool, flagged the outage at 15:22 AM UTC, 21 minutes before Zendesk&rsquo;s internal alerts.<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1429\" height=\"564\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-84.png\" alt=\"\" class=\"wp-image-619201\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-84.png 1429w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-84-18x7.png 18w\" sizes=\"auto, (max-width: 1429px) 100vw, 1429px\"><\/figure><p class=\"wp-block-paragraph\">Internet Sonar dashboard<\/p><p class=\"wp-block-paragraph\">The Internet Sonar dashboard shows Zendesk&rsquo;s outage affecting multiple global locations, with 100% downtime reported across several cities.<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1429\" height=\"564\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-84.png\" alt=\"\" class=\"wp-image-619200\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-84.png 1429w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-84-18x7.png 18w\" sizes=\"auto, (max-width: 1429px) 100vw, 1429px\"><\/figure><p class=\"wp-block-paragraph\">Scatterplot showing multiple tests run against Zendesk domain failing<\/p><p class=\"wp-block-paragraph\">The scatterplot above from Internet Sonar visualizes the Zendesk outage, showing a surge in failed tests (red markers) starting around 15:22 AM UTC. The concentration of failures indicates a widespread service disruption.<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1376\" height=\"366\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-81.png\" alt=\"\" class=\"wp-image-619197\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-81.png 1376w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-81-18x5.png 18w\" sizes=\"auto, (max-width: 1376px) 100vw, 1376px\"><\/figure><p class=\"wp-block-paragraph\">503 Service Unavailable errors affecting Zendesk<\/p><h3 id=\"h-the-cost-of-delayed-root-cause-analysis\" class=\"wp-block-heading\">The cost of delayed root cause analysis<\/h3><p class=\"wp-block-paragraph\">Zendesk&rsquo;s internal team took 21 minutes to correlate user reports with the 503 errors that Internet Sonar had already flagged. While this might not seem like a long time, every minute of downtime means lost revenue, frustrated customers, and operational disruptions. The longer it takes to pinpoint the issue, the longer it takes to fix it.<\/p><p class=\"wp-block-paragraph\">Without immediate visibility into where and why a problem is occurring, IT teams waste precious time in war rooms trying to determine if the issue is internal or caused by a third-party provider.<\/p><h3 id=\"h-independent-proactive-monitoring-of-your-internet-stack-is-essential\" class=\"wp-block-heading\">Independent proactive monitoring of your Internet Stack is essential<\/h3><p class=\"wp-block-paragraph\">No organization can afford to operate without independent, proactive visibility into their digital ecosystem. That&rsquo;s where <a href=\"https:\/\/www.logicmonitor.com\/fr\/internet-performance-monitoring\">Supervision des performances Internet<\/a> comes in.<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"868\" height=\"633\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-85.png\" alt=\"\" class=\"wp-image-619202\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-85.png 868w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-85-16x12.png 16w\" sizes=\"auto, (max-width: 868px) 100vw, 868px\"><\/figure><p class=\"wp-block-paragraph\">Internet Sonar dashboard<\/p><p class=\"wp-block-paragraph\"><a href=\"https:\/\/www.logicmonitor.com\/catchpoint\/internet-health\">Internet Sonar<\/a> eliminates guesswork by providing real-time, independent Internet health data. With Internet Sonar, you&rsquo;ll know whenever a third party has an outage, where it&rsquo;s happening, how long it&rsquo;s been going on, and whether it&rsquo;s likely to affect you.<\/p><h3 id=\"h-the-hidden-challenges-of-multi-pod-infrastructure\" class=\"wp-block-heading\">The hidden challenges of multi-pod infrastructure<\/h3><p class=\"wp-block-paragraph\">The Zendesk outage also exposed vulnerabilities of multi-pod architectures, where failures in one pod cascaded into issues across multiple regions. While these architectures are designed for scalability and redundancy, they introduce complexities that can extend downtime when something goes wrong.<\/p><p class=\"wp-block-paragraph\">In this case, even after initial recovery, intermittent failures continued for over 24 hours, preventing full service restoration. For companies reliant on cloud-based applications like Zendesk, this reinforces the need for deep visibility into third-party infrastructure dependencies to understand:<\/p><ul class=\"wp-block-list\">\n<li>Where failures are occurring<\/li>\n\n\n\n<li>How they impact interconnected systems<\/li>\n\n\n\n<li>How long the recovery process might take<\/li>\n<\/ul><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\"><a href=\"https:\/\/www.logicmonitor.com\/catchpoint\/internet-stack-map\">Carte de la pile Internet<\/a> can help with this by showing a live view of the health of your digital service and the services it depends on.<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"897\" height=\"597\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-83.png\" alt=\"\" class=\"wp-image-619199\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-83.png 897w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-83-18x12.png 18w\" sizes=\"auto, (max-width: 897px) 100vw, 897px\"><\/figure><p class=\"wp-block-paragraph\">Internet Stack Map dashboard<\/p><p class=\"wp-block-paragraph\">By automatically discovering third-party dependencies, Internet Stack Map helps organizations understand the health of their digital ecosystem at a glance. When one component fails, it&rsquo;s clearly highlighted, making root-cause analysis seamless.<\/p><h2 id=\"h-full-visibility-starts-here\" class=\"wp-block-heading\">Full visibility starts here<\/h2><p class=\"wp-block-paragraph\">Outages like Zendesk&rsquo;s reinforce a fundamental reality: you can&rsquo;t protect what you can&rsquo;t see. LogicMonitor brings together <a href=\"https:\/\/www.logicmonitor.com\/fr\/internet-performance-monitoring\">internet visibility<\/a>,<a href=\"https:\/\/www.logicmonitor.com\/fr\/infrastructure-monitoring\"> infrastructure monitoring<\/a>, et <a href=\"https:\/\/www.logicmonitor.com\/fr\/edwin-ai\">AI orchestration<\/a> into one platform, giving teams unified visibility from user to code. That means faster detection, clearer context, and confident action, whether the issue sits inside your environment or with a third-party provider.<\/p><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50\">\n      <span class=\"head-icon\"><svg class=\"\" width=\"50px\" height=\"50px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-light-calendar-check\"><\/use>\n    <\/svg><\/span>\n  \n  <div class=\"rtc-text-content__wrapper\">\n          <h4 class=\"rtc-text-content__headline fs-sm-text-display-xxs fs-md-text-display-xs fs-lg-text-display-sm font-medium text-core-blue-900\">\n        Catch third-party outages before they impact your users.      <\/h4>\n    \n          <div class=\"rtc-text-content__body fs-sm-text-md fs-md-text-lg fs-lg-text-lg text-core-blue-900\">\n        <p>LogicMonitor Synthetics and Internet Performance Monitoring deliver independent, real-time visibility into every dependency in your internet stack, so you can detect, diagnose, and resolve incidents faster. See how it works in your environment.<\/p>\n      <\/div>\n    \n          \n      \n              <div>\n            <a href=\"https:\/\/www.logicmonitor.com\/catchpoint-demo\" class=\"btn btn-link\" target=\"_self\">\n        Demander une d\u00e9monstration          <span class=\"icon-end\"><svg class=\"\" width=\"20px\" height=\"20px\" style=\"fill: #060F4B\">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-arrow-right\"><\/use>\n    <\/svg><\/span>\n      <\/a>\n        <\/div>\n            <\/div>\n<\/div><h4 id=\"h-faqs\" class=\"wp-block-heading\">FAQ<\/h4><div class=\"accordion-block accordion-block--light\">\n      <div class=\"accordion-block__items\">\n              <div class=\"accordion-block__item active\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-how-did-internet-sonar-detect-the-zendesk-outage-before-zendesks-own-team\">\n            How did Internet Sonar detect the Zendesk outage before Zendesk's own team?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer active\">\n            <p>Internet Sonar continuously runs independent tests against services from global locations, so it flagged widespread 503 failures at 15:22 AM UTC. That was 21 minutes before Zendesk&rsquo;s internal alerts confirmed the issue, giving affected teams an earlier warning of a third-party problem.<\/p>\n                      <\/div>\n        <\/div>\n              <div class=\"accordion-block__item\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-why-did-the-zendesk-outage-take-so-long-to-fully-resolve\">\n            Why did the Zendesk outage take so long to fully resolve?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer\">\n            <p>Zendesk runs on a multi-pod architecture, where a failure in one pod can cascade across regions. Even after core services stabilized, intermittent errors persisted for more than 24 hours, which delayed full restoration and pushed some businesses to manual processes.<\/p>\n                      <\/div>\n        <\/div>\n              <div class=\"accordion-block__item\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-how-can-businesses-reduce-the-impact-of-third-party-outages-like-this-one\">\n            How can businesses reduce the impact of third-party outages like this one?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer\">\n            <p>Independent, proactive monitoring gives teams visibility into services they depend on but do not control. Tools like Internet Sonar and Internet Stack Map show where a failure is happening, how it affects connected systems, and how long it has been ongoing, which speeds up root cause analysis and incident response.<\/p>\n                      <\/div>\n        <\/div>\n          <\/div>\n  <\/div>","protected":false},"excerpt":{"rendered":"<p>D\u00e9couvrez comment la surveillance des performances Internet a d\u00e9tect\u00e9 la panne de Zendesk 21 minutes \u00e0 l'avance et ce que cela enseigne aux \u00e9quipes sur la surveillance proactive et la r\u00e9solution plus rapide des incidents.<\/p>","protected":false},"author":16,"featured_media":624047,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"unicorn_plugin_options_block_body_class":"","footnotes":""},"categories":[5035],"tags":[7850,7777,7760,7864,7906,7752,7854,6677,7862,7860],"industry":[6790],"role":[6786],"lm_strategic_tags":[],"topic":[7842],"author_attribution":[7967],"lm_product":[],"class_list":["post-619195","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","industry-all","role-itops","topic-internet-performance-monitoring","author_attribution-denton-chikura"],"acf":{"page_language":"english","translated_pages":"","updated_date":null,"author_section_checkbox":true,"author_image":617027,"author_linkedin":"https:\/\/www.linkedin.com\/in\/denton-chikura-422186201\/","author_name":"Denton Chikura","author_job_title":"Technical Writer","author_dept":"","author_bio":"Denton Chikura is a technical writer and longtime observability advocate focused on helping site reliability engineers and engineering teams discover the tools and capabilities that strengthen internet resilience. He works at the intersection of monitoring, performance, and infrastructure to make complex systems more understandable and usable, bridging the gap between deep technical detail and real\u2011world operations. His goal is to help teams build faster, detect issues earlier, and recover smarter, ultimately making the internet a better, more reliable place for everyone.","reviewer_name":""},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.4 (Yoast SEO v28.4) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Zendesk Outage: Why Proactive Monitoring Matters | LogicMonitor<\/title>\n<meta name=\"description\" content=\"Zendesk&#039;s recent outage is a reminder of the importance of proactive monitoring. Learn what happened, how it was detected, and key takeaways for better incident response.\" \/>\n<meta name=\"robots\" content=\"noindex, nofollow\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Zendesk Outage: A Case for Proactive Monitoring and Faster Incident Response\" \/>\n<meta property=\"og:description\" content=\"Zendesk&#039;s recent outage is a reminder of the importance of proactive monitoring. Learn what happened, how it was detected, and key takeaways for better incident response.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.logicmonitor.com\/fr\/blog\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response\" \/>\n<meta property=\"og:site_name\" content=\"LogicMonitor\" \/>\n<meta property=\"article:published_time\" content=\"2026-09-01T17:24:24+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-09-02T17:02:55+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Blog_Zendesk-Outage_-A-Case-for-Proactive-Monitoring-and-Faster-Incident-Response_Meta-1600x900px.png\" \/>\n\t<meta property=\"og:image:width\" content=\"2400\" \/>\n\t<meta property=\"og:image:height\" content=\"1350\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"destiny.setzer@logicmonitor.com\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response\"},\"author\":{\"name\":\"destiny.setzer@logicmonitor.com\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\"},\"headline\":\"Zendesk Outage: A Case for Proactive Monitoring and Faster Incident Response\",\"datePublished\":\"2026-09-01T17:24:24+00:00\",\"dateModified\":\"2026-09-02T17:02:55+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response\"},\"wordCount\":856,\"image\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Blog_Zendesk-Outage_-A-Case-for-Proactive-Monitoring-and-Faster-Incident-Response_940x600_Featured-Image.png\",\"keywords\":[\"Catchpoint\",\"Edwin\",\"Incident Response\",\"Internet Sonar\",\"Internet Stack Map\",\"LM Envision\",\"Outage Detection\",\"Performance optimization\",\"SLA Monitoring\",\"User Experience\"],\"articleSection\":[\"Blog\"],\"inLanguage\":\"fr-FR\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response\",\"name\":\"Zendesk Outage: Why Proactive Monitoring Matters | LogicMonitor\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Blog_Zendesk-Outage_-A-Case-for-Proactive-Monitoring-and-Faster-Incident-Response_940x600_Featured-Image.png\",\"datePublished\":\"2026-09-01T17:24:24+00:00\",\"dateModified\":\"2026-09-02T17:02:55+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\"},\"description\":\"Zendesk's recent outage is a reminder of the importance of proactive monitoring. Learn what happened, how it was detected, and key takeaways for better incident response.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response#primaryimage\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Blog_Zendesk-Outage_-A-Case-for-Proactive-Monitoring-and-Faster-Incident-Response_940x600_Featured-Image.png\",\"contentUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Blog_Zendesk-Outage_-A-Case-for-Proactive-Monitoring-and-Faster-Incident-Response_940x600_Featured-Image.png\",\"width\":1410,\"height\":900},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.logicmonitor.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Zendesk Outage: A Case for Proactive Monitoring and Faster Incident Response\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#website\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/\",\"name\":\"LogicMonitor\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\",\"name\":\"destiny.setzer@logicmonitor.com\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Zendesk Outage: Why Proactive Monitoring Matters | LogicMonitor","description":"Zendesk's recent outage is a reminder of the importance of proactive monitoring. Learn what happened, how it was detected, and key takeaways for better incident response.","robots":{"index":"noindex","follow":"nofollow"},"og_locale":"fr_FR","og_type":"article","og_title":"Zendesk Outage: A Case for Proactive Monitoring and Faster Incident Response","og_description":"Zendesk's recent outage is a reminder of the importance of proactive monitoring. Learn what happened, how it was detected, and key takeaways for better incident response.","og_url":"https:\/\/www.logicmonitor.com\/fr\/blog\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response","og_site_name":"LogicMonitor","article_published_time":"2026-09-01T17:24:24+00:00","article_modified_time":"2026-09-02T17:02:55+00:00","og_image":[{"url":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Blog_Zendesk-Outage_-A-Case-for-Proactive-Monitoring-and-Faster-Incident-Response_Meta-1600x900px.png","width":2400,"height":1350,"type":"image\/png"}],"author":"destiny.setzer@logicmonitor.com","twitter_card":"summary_large_image","twitter_misc":{"Written by":"","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response#article","isPartOf":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response"},"author":{"name":"destiny.setzer@logicmonitor.com","@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def"},"headline":"Zendesk Outage: A Case for Proactive Monitoring and Faster Incident Response","datePublished":"2026-09-01T17:24:24+00:00","dateModified":"2026-09-02T17:02:55+00:00","mainEntityOfPage":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response"},"wordCount":856,"image":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response#primaryimage"},"thumbnailUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/Blog_Zendesk-Outage_-A-Case-for-Proactive-Monitoring-and-Faster-Incident-Response_940x600_Featured-Image.png","keywords":["Catchpoint","Edwin","Incident Response","Internet Sonar","Internet Stack Map","LM Envision","Outage Detection","Performance optimization","SLA Monitoring","User Experience"],"articleSection":["Blog"],"inLanguage":"fr-FR"},{"@type":"WebPage","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response","url":"https:\/\/www.logicmonitor.com\/fr\/blog\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response","name":"Zendesk Outage: Why Proactive Monitoring Matters | LogicMonitor","isPartOf":{"@id":"https:\/\/www.logicmonitor.com\/fr\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response#primaryimage"},"image":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response#primaryimage"},"thumbnailUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/Blog_Zendesk-Outage_-A-Case-for-Proactive-Monitoring-and-Faster-Incident-Response_940x600_Featured-Image.png","datePublished":"2026-09-01T17:24:24+00:00","dateModified":"2026-09-02T17:02:55+00:00","author":{"@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def"},"description":"Zendesk's recent outage is a reminder of the importance of proactive monitoring. Learn what happened, how it was detected, and key takeaways for better incident response.","breadcrumb":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.logicmonitor.com\/fr\/blog\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response"]}]},{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response#primaryimage","url":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/Blog_Zendesk-Outage_-A-Case-for-Proactive-Monitoring-and-Faster-Incident-Response_940x600_Featured-Image.png","contentUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/Blog_Zendesk-Outage_-A-Case-for-Proactive-Monitoring-and-Faster-Incident-Response_940x600_Featured-Image.png","width":1410,"height":900},{"@type":"BreadcrumbList","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/zendesk-outage-a-case-for-proactive-monitoring-and-faster-incident-response#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.logicmonitor.com\/"},{"@type":"ListItem","position":2,"name":"Zendesk Outage: A Case for Proactive Monitoring and Faster Incident Response"}]},{"@type":"WebSite","@id":"https:\/\/www.logicmonitor.com\/fr\/#website","url":"https:\/\/www.logicmonitor.com\/fr\/","name":"LogicMonitor","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.logicmonitor.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Person","@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def","name":"destiny.setzer@logicmonitor.com"}]}},"_links":{"self":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/619195","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/users\/16"}],"replies":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/comments?post=619195"}],"version-history":[{"count":6,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/619195\/revisions"}],"predecessor-version":[{"id":626161,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/619195\/revisions\/626161"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/media\/624047"}],"wp:attachment":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/media?parent=619195"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/categories?post=619195"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/tags?post=619195"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/industry?post=619195"},{"taxonomy":"role","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/role?post=619195"},{"taxonomy":"lm_strategic_tags","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/lm_strategic_tags?post=619195"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/topic?post=619195"},{"taxonomy":"author_attribution","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/author_attribution?post=619195"},{"taxonomy":"lm_product","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/lm_product?post=619195"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":619183,"date":"2026-09-01T12:24:11","date_gmt":"2026-09-01T17:24:11","guid":{"rendered":"https:\/\/www.logicmonitor.com\/?p=619183"},"modified":"2026-09-02T12:02:56","modified_gmt":"2026-09-02T17:02:56","slug":"silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring","status":"publish","type":"post","link":"https:\/\/www.logicmonitor.com\/fr\/blog\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring","title":{"rendered":"R\u00e9trospective de panne : pourquoi la panne de X a rendu la surveillance ind\u00e9pendante essentielle"},"content":{"rendered":"<?xml encoding=\"UTF-8\"><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50 rtc-text-content--no-top-pad\">\n      <span class=\"head-icon\"><svg class=\"\" width=\"50px\" height=\"50px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-light-book-open\"><\/use>\n    <\/svg><\/span>\n  \n  <div class=\"rtc-text-content__wrapper\">\n          <h4 class=\"rtc-text-content__headline fs-sm-text-display-xs fs-md-text-display-sm fs-lg-text-display-md font-medium text-core-blue-900\">\n        Le t\u00e9l\u00e9chargement rapide :      <\/h4>\n    \n          <div class=\"rtc-text-content__body fs-sm-text-md fs-md-text-lg fs-lg-text-lg text-core-blue-900 headline-is-quote\">\n        <p>When a platform you don&rsquo;t control fails, independent monitoring is the difference between confirming impact in minutes and troubleshooting blind for hours.<\/p>\n      <\/div>\n    \n                  <ul class=\"rtc-text-content__bullet-list\">\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>X went down repeatedly over 24 hours across more than 30 countries, and vendor communication stayed sparse throughout the disruption.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>Catchpoint&rsquo;s Internet Sonar detected each outage wave in real time, mapped the global spread, and confirmed the problem sat outside internal infrastructure.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>Traceroute and wait-time data showed heavy packet loss and degraded response times, patterns consistent with the DDoS attack X later cited.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>Check whether your monitoring extends past your own infrastructure to the Internet path your users actually traverse, before your next critical vendor goes dark.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                  <\/ul>\n      \n      \n            <\/div>\n<\/div><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">Your business depends on platforms you don&rsquo;t control. When one of those platforms fails, the only question that matters is how quickly your team can confirm impact, communicate clearly, and avoid wasting time troubleshooting the wrong system. On March 10, 2025, the X (formerly Twitter) global outage gave IT teams everywhere a case study in that exact challenge.<\/p><p class=\"wp-block-paragraph\"><a href=\"https:\/\/www.logicmonitor.com\/fr\/logicmonitor-catchpoint\">Catchpoint, a LogicMonitor company<\/a>, detected the crisis in real time through <a href=\"https:\/\/www.logicmonitor.com\/catchpoint\/internet-health\">Internet Sonar<\/a>, providing independent visibility while the platform&rsquo;s own communications remained sparse. For IT teams, the lesson extends well beyond this single incident: any organization relying on opaque third-party platforms without independent monitoring is operating with a significant blind spot.<\/p><p class=\"wp-block-paragraph\">Here&rsquo;s what happened, what the monitoring data revealed, and what IT teams should take away from an incident that reinforced why outside-in visibility matters.<\/p><h2 id=\"h-x-outage-explained-what-happened\" class=\"wp-block-heading\">X Outage Explained: What Happened<\/h2><p class=\"wp-block-paragraph\">On March 10, 2025, starting at 5:30 AM EDT, users worldwide were abruptly disconnected from X. Over the next 24 hours, waves of outages (punctuated by brief recoveries) left users stranded, unable to access feeds, send messages, or engage with content. The disruption spanned more than 30 countries, from Argentina to the UAE, underscoring the platform&rsquo;s global reach and the scale of its failure.<\/p><p class=\"wp-block-paragraph\">The outage unfolded in several distinct stages due to connection timeouts.<\/p><h3 id=\"h-tracking-the-x-outage-in-real-time\" class=\"wp-block-heading\">Tracking the X Outage in Real Time<\/h3><p class=\"wp-block-paragraph\"><strong>March 10<\/strong><\/p><ul class=\"wp-block-list\">\n<li><strong>First wave:<\/strong><\/li>\n\n\n\n<li><strong>5:30 AM EDT:<\/strong> First reports of X being down surface.<\/li>\n\n\n\n<li><strong>6:30 AM EDT:<\/strong> X comes back for most users.<\/li>\n\n\n\n<li><strong>Second wave:<\/strong><\/li>\n\n\n\n<li><strong>9:30 AM EDT:<\/strong> A second wave of outage reports indicates that X is down again.<\/li>\n\n\n\n<li><strong>Third wave:<\/strong><\/li>\n\n\n\n<li><strong>11:15 AM EDT:<\/strong> A third wave of outage reports emerges, with X down once again.<\/li>\n\n\n\n<li><strong>Recovery phase:<\/strong><\/li>\n\n\n\n<li><strong>1:15 PM EDT:<\/strong> X recovers for many users.<\/li>\n\n\n\n<li><strong>2:15 PM EDT:<\/strong> X is working for some, but many continue to report issues.<\/li>\n\n\n\n<li><strong>3:25 PM EDT:<\/strong> X recovers for most people.<\/li>\n<\/ul><p class=\"wp-block-paragraph\"><strong>March 11<\/strong><\/p><ul class=\"wp-block-list\">\n<li><strong>Additional reports:<\/strong><\/li>\n\n\n\n<li><strong>5:00 AM EDT:<\/strong> A small spike in outage reports appears.<\/li>\n<\/ul><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">Outages appeared to have subsided as of reporting, though this could change as investigations into the root cause continued.<\/p><p class=\"wp-block-paragraph\">When a third-party platform fails this visibly, the first challenge for IT teams is determining whether the problem is internal, external, or somewhere in the dependency chain. Independent Internet monitoring answers that question in minutes rather than hours. It confirms whether your own infrastructure is healthy, identifies which external dependencies are affected, and gives your team the evidence they need to brief stakeholders and update customers with confidence.<\/p><h2 id=\"h-how-internet-sonar-revealed-the-disruption\" class=\"wp-block-heading\">How Internet Sonar Revealed the Disruption<\/h2><p class=\"wp-block-paragraph\">Internet Sonar detected multiple outages for X in real time as the disruptions unfolded. Multiple X-related domains were unable to deliver content. These domains are often used to load content on other websites (known as &ldquo;child requests&rdquo;). The widespread failures seen across many locations demonstrate how extensively the outage disrupted X and other websites relying on X&rsquo;s infrastructure.<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"800\" height=\"409\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-11.jpeg\" alt=\"\" class=\"wp-image-619188\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-11.jpeg 800w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-11-18x9.jpeg 18w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\"><\/figure><p class=\"wp-block-paragraph\">Scatterplot of X&rsquo;s service disruption<\/p><p class=\"wp-block-paragraph\">The scatterplot above shows multiple tests run against X Corp&rsquo;s domains throughout the outage period. The clusters of red dots highlight moments when tests consistently failed or timed out. Each cluster corresponds with one of the outage waves, clearly illustrating the recurring and widespread nature of X&rsquo;s connection issues during this incident.<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1379\" height=\"195\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-76.png\" alt=\"\" class=\"wp-image-619187\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-76.png 1379w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-76-18x3.png 18w\" sizes=\"auto, (max-width: 1379px) 100vw, 1379px\"><\/figure><p class=\"wp-block-paragraph\">Waterfall chart from Catchpoint&rsquo;s portal<\/p><p class=\"wp-block-paragraph\">The waterfall chart above shows that X&rsquo;s servers could initially be reached, but response times were severely degraded. Eventually, these requests timed out completely, meaning the servers failed to deliver the requested content. This illustrates the delays users experienced during the outage.<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1296\" height=\"664\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-78.png\" alt=\"\" class=\"wp-image-619190\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-78.png 1296w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-78-18x9.png 18w\" sizes=\"auto, (max-width: 1296px) 100vw, 1296px\"><\/figure><p class=\"wp-block-paragraph\">Traceroute data from Catchpoint&rsquo;s portal<\/p><p class=\"wp-block-paragraph\">The traceroute data above shows significant issues during the outage, particularly large packet losses and high round-trip times (RTT). High packet loss means that data sent to X&rsquo;s servers was frequently lost along the way, while increased RTT indicates that responses from X&rsquo;s servers were severely delayed. Both clearly illustrate why users experienced sluggish performance during the outage.<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"574\" height=\"377\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-75.png\" alt=\"\" class=\"wp-image-619186\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-75.png 574w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-75-18x12.png 18w\" sizes=\"auto, (max-width: 574px) 100vw, 574px\"><\/figure><p class=\"wp-block-paragraph\">Screenshot showing a typical user experience during the outage on x.com<\/p><h2 id=\"h-what-the-data-suggested\" class=\"wp-block-heading\">What the Data Suggested<\/h2><p class=\"wp-block-paragraph\">CEO Elon Musk attributed the outage to a <a href=\"https:\/\/news.sky.com\/story\/elon-musk-says-x-hit-by-massive-cyber-attack-as-users-unable-to-log-in-13325939\">DDoS (Denial of Service) attack<\/a>. Independent monitoring data showed patterns consistent with that explanation, though monitoring alone can&rsquo;t confirm the root cause definitively.<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1376\" height=\"861\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-77.png\" alt=\"\" class=\"wp-image-619189\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-77.png 1376w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-77-18x12.png 18w\" sizes=\"auto, (max-width: 1376px) 100vw, 1376px\"><\/figure><p class=\"wp-block-paragraph\">Wait time data over three-day period<\/p><p class=\"wp-block-paragraph\">Data collected over an extended baseline for X Corp&rsquo;s domains shows that during the outage there was a notable spike in mean wait time. This suggests the servers were slower to respond, an effect that aligns with what typically occurs during a DDoS attack. The elevated wait times, combined with significant packet loss and degraded response patterns observed across multiple geographies, are consistent with a volumetric attack. However, similar symptoms can also result from infrastructure misconfigurations or capacity failures under unexpected load.<\/p><p class=\"wp-block-paragraph\">Monitoring doesn&rsquo;t replace mitigation. Organizations should also evaluate DDoS protection and WAF configurations as part of their overall resilience strategy.<\/p><h2 id=\"h-lessons-from-the-x-outage\" class=\"wp-block-heading\">Lessons From the X Outage<\/h2><p class=\"wp-block-paragraph\">The X outage exposed real vulnerabilities in how businesses depend on platforms they don&rsquo;t control, and how limited their visibility can be when things go wrong.<\/p><h3 id=\"h-the-internet-is-interconnected-and-that-creates-risk\" class=\"wp-block-heading\">The Internet Is Interconnected, and That Creates Risk<\/h3><p class=\"wp-block-paragraph\">The outage reinforced something that&rsquo;s easy to overlook: the Internet is a web of interdependent systems, and a failure in one platform can cascade quickly. X didn&rsquo;t just go down once. It failed repeatedly over 24 hours, leaving millions unable to access the service.<\/p><p class=\"wp-block-paragraph\">Modern applications rely on the internet stack, which includes layers of third-party services, APIs, cloud providers, and DNS resolvers. Each layer is a potential point of failure. When one breaks, the effects ripple outward.<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"2475\" height=\"1370\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/06\/FIGURE-1_-The-Internet-Stack.png\" alt=\"\" class=\"wp-image-614721\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/06\/FIGURE-1_-The-Internet-Stack.png 2475w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/06\/FIGURE-1_-The-Internet-Stack-300x166.png 300w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/06\/FIGURE-1_-The-Internet-Stack-1024x567.png 1024w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/06\/FIGURE-1_-The-Internet-Stack-768x425.png 768w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/06\/FIGURE-1_-The-Internet-Stack-1536x850.png 1536w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/06\/FIGURE-1_-The-Internet-Stack-2048x1134.png 2048w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/06\/FIGURE-1_-The-Internet-Stack-18x10.png 18w\" sizes=\"auto, (max-width: 2475px) 100vw, 2475px\"><\/figure><p class=\"wp-block-paragraph\">The layers of the internet stack<\/p><p class=\"wp-block-paragraph\">Consider the ripple effects: small businesses lost real-time customer engagement, journalists couldn&rsquo;t share breaking news, and organizations relying on the platform for time-sensitive communication faced potential delays in reaching their audiences. No platform, regardless of scale, is immune to disruption. Preparedness begins with acknowledging that risk.<\/p><h3 id=\"h-vendor-updates-arent-enough-independent-visibility-matters\" class=\"wp-block-heading\">Vendor Updates Aren&rsquo;t Enough: Independent Visibility Matters<\/h3><p class=\"wp-block-paragraph\">During the outage, users received limited information beyond a brief statement from X&rsquo;s CEO. This situation isn&rsquo;t uncommon. Vendor status pages often struggle to keep pace with rapidly evolving incidents, and delays in communication lead to confusion and slower response times for impacted businesses.<\/p><p class=\"wp-block-paragraph\">Independent, proactive monitoring tools give your organization clear, real-time insights. That enables faster responses and smoother operations, regardless of vendor communication timelines.<\/p><h3 id=\"h-independent-monitoring-in-action\" class=\"wp-block-heading\">Independent Monitoring in Action<\/h3><p class=\"wp-block-paragraph\">The X outage demonstrated exactly why proactive, independent monitoring matters. Teams using <a href=\"https:\/\/www.logicmonitor.com\/catchpoint\/internet-health\">Internet Sonar<\/a> et <a href=\"https:\/\/www.logicmonitor.com\/catchpoint\/internet-stack-map\">Carte de la pile Internet<\/a> had two capabilities that proved especially valuable during the event.<\/p><p class=\"wp-block-paragraph\">Internet Sonar provided real-time, vendor-agnostic detection. It caught the outage&rsquo;s first ripple, mapped its global spread, and quantified its impact. For IT teams, this translated into actionable time. Instead of reacting to user complaints or waiting for a vendor status page update, teams could confirm the issue independently and begin communicating with stakeholders within minutes of the first disruption.<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1433\" height=\"492\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-79.png\" alt=\"\" class=\"wp-image-619191\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-79.png 1433w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-79-18x6.png 18w\" sizes=\"auto, (max-width: 1433px) 100vw, 1433px\"><\/figure><p class=\"wp-block-paragraph\">Internet Sonar<\/p><p class=\"wp-block-paragraph\">Internet Sonar&rsquo;s map view above shows how widespread the disruption was, with outages reported across multiple locations around the globe.<\/p><p class=\"wp-block-paragraph\">During incidents like this, independent monitoring helps teams in several concrete ways:<\/p><ul class=\"wp-block-list\">\n<li><strong>Confirming impact scope:<\/strong> Instead of relying on social media chatter or vendor acknowledgments, teams can verify the geographic and functional scope of a disruption directly.<\/li>\n\n\n\n<li><strong>Briefing internal stakeholders:<\/strong> With real data showing which services are affected and how severely, teams can provide leadership with specific, credible updates rather than &ldquo;we&rsquo;re looking into it.&rdquo;<\/li>\n\n\n\n<li><strong>Updating customers:<\/strong> External-facing communications become faster and more accurate when backed by independent telemetry.<\/li>\n\n\n\n<li><strong>Avoiding wasted troubleshooting:<\/strong> When monitoring confirms the problem is external, teams can stop investigating their own infrastructure and focus on workarounds or contingency plans.<\/li>\n<\/ul><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">Internet Stack Map complemented this by visualizing X&rsquo;s dependencies. When the platform went down, teams could see exactly how interconnected services (APIs, authentication layers, and content delivery networks) were affected. This dependency visibility turned a vague public outage into an actionable map of affected services. Root-cause analysis, often a process that takes days when you&rsquo;re waiting for vendor post-mortems, became a matter of minutes with independent data.<\/p><h3 id=\"h-what-to-monitor-when-critical-third-party-platforms-fail\" class=\"wp-block-heading\">What to Monitor When Critical Third-Party Platforms Fail<\/h3><p class=\"wp-block-paragraph\">When a major platform goes down, your monitoring should cover the full path between your users and the affected service:<\/p><ul class=\"wp-block-list\">\n<li>DNS resolution and propagation<\/li>\n\n\n\n<li>CDN and edge delivery<\/li>\n\n\n\n<li>BGP routing and path changes<\/li>\n\n\n\n<li>API dependencies and response times<\/li>\n\n\n\n<li>Synthetic test performance from multiple geographies<\/li>\n\n\n\n<li>Real user impact signals (error rates, page load failures)<\/li>\n<\/ul><h2 id=\"h-why-outside-in-visibility-belongs-in-your-monitoring-strategy\" class=\"wp-block-heading\">Why Outside-In Visibility Belongs in Your Monitoring Strategy<\/h2><p class=\"wp-block-paragraph\">The X outage was a clear reminder that traditional infrastructure monitoring alone can&rsquo;t catch what happens outside the firewall. When a platform like X goes down, the cause may sit in DNS, BGP routing, CDN layers, or third-party services that are invisible to internal tools.<\/p><p class=\"wp-block-paragraph\">This is where <a href=\"https:\/\/www.logicmonitor.com\/fr\/internet-performance-monitoring\">Supervision des performances Internet<\/a> fits in. By monitoring the external Internet path independently, from the perspective of real users across the globe, IT teams get visibility into the dependencies they rely on but don&rsquo;t control.<\/p><p class=\"wp-block-paragraph\">LogicMonitor&rsquo;s platform brings this outside-in visibility together with <a href=\"https:\/\/www.logicmonitor.com\/fr\/infrastructure-monitoring\">infrastructure monitoring<\/a> et <a href=\"https:\/\/www.logicmonitor.com\/fr\/edwin-ai\">Edwin AI<\/a> in a single system. That means teams can correlate external Internet disruptions with internal service impact, reduce investigation time, and respond with confidence, whether the problem is inside their environment, outside it, or somewhere in between.<\/p><p class=\"wp-block-paragraph\">For IT teams managing complex, distributed systems, the next step is concrete: evaluate whether your current monitoring extends beyond your own infrastructure to the Internet path your users actually traverse. Review your coverage of third-party dependencies. Confirm that when your next critical vendor goes dark, your team has independent data to act on, not just a status page to refresh.<\/p><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50\">\n      <span class=\"head-icon\"><svg class=\"\" width=\"50px\" height=\"50px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-light-calendar-check\"><\/use>\n    <\/svg><\/span>\n  \n  <div class=\"rtc-text-content__wrapper\">\n          <h4 class=\"rtc-text-content__headline fs-sm-text-display-xxs fs-md-text-display-xs fs-lg-text-display-sm font-medium text-core-blue-900\">\n        See how outside-in visibility protects your team when critical vendors fail.      <\/h4>\n    \n          <div class=\"rtc-text-content__body fs-sm-text-md fs-md-text-lg fs-lg-text-lg text-core-blue-900\">\n        <p>LogicMonitor combines external Internet monitoring with infrastructure insight, so you can pinpoint impact and act with confidence during any disruption.<\/p>\n      <\/div>\n    \n          \n      \n              <div>\n            <a href=\"https:\/\/www.logicmonitor.com\/catchpoint-demo\" class=\"btn btn-link\" target=\"_self\">\n        Demander une d\u00e9monstration          <span class=\"icon-end\"><svg class=\"\" width=\"20px\" height=\"20px\" style=\"fill: #060F4B\">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-arrow-right\"><\/use>\n    <\/svg><\/span>\n      <\/a>\n        <\/div>\n            <\/div>\n<\/div><h4 id=\"h-faqs\" class=\"wp-block-heading\">FAQ<\/h4><div class=\"accordion-block accordion-block--light\">\n      <div class=\"accordion-block__items\">\n              <div class=\"accordion-block__item active\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-how-long-does-a-dns-cache-entry-last\">\n            How long does a DNS cache entry last?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer active\">\n            <p>Each DNS record includes a TTL (time-to-live) value set in seconds by the authoritative name server. Once cached, the record counts down from that TTL. When it reaches zero, the entry is removed and the next query triggers a fresh lookup.<\/p>\n                      <\/div>\n        <\/div>\n              <div class=\"accordion-block__item\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-what-is-the-ns-cache-trap-and-how-do-you-avoid-it\">\n            What is the NS cache trap and how do you avoid it?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer\">\n            <p>The NS cache trap occurs when NS records and the corresponding A\/AAAA records for a name server have mismatched TTLs. One expires before the other, forcing extra lookups or full recursion. To avoid it, ensure NS and A\/AAAA TTLs are aligned in your DNS zone configuration.<\/p>\n                      <\/div>\n        <\/div>\n              <div class=\"accordion-block__item\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-how-do-browsers-cache-dns-differently-from-dns-servers\">\n            How do browsers cache DNS differently from DNS servers?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer\">\n            <p>Browsers and applications use the OS &ldquo;getaddrinfo()&rdquo; function, which returns IP addresses but no TTL data. Because no TTL is passed to the application, each browser sets its own cache duration and record limit. These values vary widely across browsers and versions, so check your browser&rsquo;s developer tools or internals page (e.g., chrome:\/\/net-internals\/#dns) for current behavior.<\/p>\n                      <\/div>\n        <\/div>\n          <\/div>\n  <\/div>","protected":false},"excerpt":{"rendered":"<p>Quand X a cess\u00e9 d'\u00e9mettre pendant 24 heures, une surveillance ind\u00e9pendante a confirm\u00e9 l'impact en quelques minutes. D\u00e9couvrez comment la visibilit\u00e9 externe permet aux \u00e9quipes informatiques d'anticiper les mises \u00e0 jour des fournisseurs.<\/p>","protected":false},"author":16,"featured_media":624037,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"unicorn_plugin_options_block_body_class":"","footnotes":""},"categories":[5035],"tags":[7865,7850,7867,7823,7760,7864,7906,7854,7917,7871],"industry":[6790],"role":[6786],"lm_strategic_tags":[],"topic":[7842],"author_attribution":[7967],"lm_product":[],"class_list":["post-619183","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","industry-all","role-itops","topic-internet-performance-monitoring","author_attribution-denton-chikura"],"acf":{"page_language":"english","translated_pages":"","updated_date":null,"author_section_checkbox":true,"author_image":617027,"author_linkedin":"https:\/\/www.linkedin.com\/in\/denton-chikura-422186201\/","author_name":"Denton Chikura","author_job_title":"Technical Writer","author_dept":"","author_bio":"Denton Chikura is a technical writer and longtime observability advocate focused on helping site reliability engineers and engineering teams discover the tools and capabilities that strengthen internet resilience. He works at the intersection of monitoring, performance, and infrastructure to make complex systems more understandable and usable, bridging the gap between deep technical detail and real\u2011world operations. His goal is to help teams build faster, detect issues earlier, and recover smarter, ultimately making the internet a better, more reliable place for everyone.","reviewer_name":""},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.4 (Yoast SEO v28.4) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>What the X Outage Reveals About Independent Monitoring | LogicMonitor<\/title>\n<meta name=\"description\" content=\"X&#039;s series of global outages highlight why proactive monitoring is essential during major disruptions. Here&#039;s what happened.\" \/>\n<meta name=\"robots\" content=\"noindex, nofollow\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Outage Retrospective: Why the X Outage Made Independent Monitoring Essential\" \/>\n<meta property=\"og:description\" content=\"X&#039;s series of global outages highlight why proactive monitoring is essential during major disruptions. Here&#039;s what happened.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.logicmonitor.com\/fr\/blog\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring\" \/>\n<meta property=\"og:site_name\" content=\"LogicMonitor\" \/>\n<meta property=\"article:published_time\" content=\"2026-09-01T17:24:11+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-09-02T17:02:56+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Blog_Outage-Retrospective_-Why-the-X-Outage-Made-Independent-Monitoring-Essential_Meta-1600x900px.png\" \/>\n\t<meta property=\"og:image:width\" content=\"2400\" \/>\n\t<meta property=\"og:image:height\" content=\"1350\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"destiny.setzer@logicmonitor.com\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring\"},\"author\":{\"name\":\"destiny.setzer@logicmonitor.com\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\"},\"headline\":\"Outage Retrospective: Why the X Outage Made Independent Monitoring Essential\",\"datePublished\":\"2026-09-01T17:24:11+00:00\",\"dateModified\":\"2026-09-02T17:02:56+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring\"},\"wordCount\":1605,\"image\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/Blog_Outage-Retrospective_-Why-the-X-Outage-Made-Independent-Monitoring-Essential_940x600_Featured-Image.png\",\"keywords\":[\"BGP Monitoring\",\"Catchpoint\",\"CDN Monitoring\",\"dns-monitoring\",\"Incident Response\",\"Internet Sonar\",\"Internet Stack Map\",\"Outage Detection\",\"Packet Loss\",\"Traceroute\"],\"articleSection\":[\"Blog\"],\"inLanguage\":\"fr-FR\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring\",\"name\":\"What the X Outage Reveals About Independent Monitoring | LogicMonitor\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/Blog_Outage-Retrospective_-Why-the-X-Outage-Made-Independent-Monitoring-Essential_940x600_Featured-Image.png\",\"datePublished\":\"2026-09-01T17:24:11+00:00\",\"dateModified\":\"2026-09-02T17:02:56+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\"},\"description\":\"X's series of global outages highlight why proactive monitoring is essential during major disruptions. Here's what happened.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring#primaryimage\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/Blog_Outage-Retrospective_-Why-the-X-Outage-Made-Independent-Monitoring-Essential_940x600_Featured-Image.png\",\"contentUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/Blog_Outage-Retrospective_-Why-the-X-Outage-Made-Independent-Monitoring-Essential_940x600_Featured-Image.png\",\"width\":1410,\"height\":900},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.logicmonitor.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Outage Retrospective: Why the X Outage Made Independent Monitoring Essential\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#website\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/\",\"name\":\"LogicMonitor\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\",\"name\":\"destiny.setzer@logicmonitor.com\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"What the X Outage Reveals About Independent Monitoring | LogicMonitor","description":"X's series of global outages highlight why proactive monitoring is essential during major disruptions. Here's what happened.","robots":{"index":"noindex","follow":"nofollow"},"og_locale":"fr_FR","og_type":"article","og_title":"Outage Retrospective: Why the X Outage Made Independent Monitoring Essential","og_description":"X's series of global outages highlight why proactive monitoring is essential during major disruptions. Here's what happened.","og_url":"https:\/\/www.logicmonitor.com\/fr\/blog\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring","og_site_name":"LogicMonitor","article_published_time":"2026-09-01T17:24:11+00:00","article_modified_time":"2026-09-02T17:02:56+00:00","og_image":[{"url":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Blog_Outage-Retrospective_-Why-the-X-Outage-Made-Independent-Monitoring-Essential_Meta-1600x900px.png","width":2400,"height":1350,"type":"image\/png"}],"author":"destiny.setzer@logicmonitor.com","twitter_card":"summary_large_image","twitter_misc":{"Written by":"","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring#article","isPartOf":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring"},"author":{"name":"destiny.setzer@logicmonitor.com","@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def"},"headline":"Outage Retrospective: Why the X Outage Made Independent Monitoring Essential","datePublished":"2026-09-01T17:24:11+00:00","dateModified":"2026-09-02T17:02:56+00:00","mainEntityOfPage":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring"},"wordCount":1605,"image":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring#primaryimage"},"thumbnailUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Blog_Outage-Retrospective_-Why-the-X-Outage-Made-Independent-Monitoring-Essential_940x600_Featured-Image.png","keywords":["BGP Monitoring","Catchpoint","CDN Monitoring","dns-monitoring","Incident Response","Internet Sonar","Internet Stack Map","Outage Detection","Packet Loss","Traceroute"],"articleSection":["Blog"],"inLanguage":"fr-FR"},{"@type":"WebPage","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring","url":"https:\/\/www.logicmonitor.com\/fr\/blog\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring","name":"What the X Outage Reveals About Independent Monitoring | LogicMonitor","isPartOf":{"@id":"https:\/\/www.logicmonitor.com\/fr\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring#primaryimage"},"image":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring#primaryimage"},"thumbnailUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Blog_Outage-Retrospective_-Why-the-X-Outage-Made-Independent-Monitoring-Essential_940x600_Featured-Image.png","datePublished":"2026-09-01T17:24:11+00:00","dateModified":"2026-09-02T17:02:56+00:00","author":{"@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def"},"description":"X's series of global outages highlight why proactive monitoring is essential during major disruptions. Here's what happened.","breadcrumb":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.logicmonitor.com\/fr\/blog\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring"]}]},{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring#primaryimage","url":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Blog_Outage-Retrospective_-Why-the-X-Outage-Made-Independent-Monitoring-Essential_940x600_Featured-Image.png","contentUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Blog_Outage-Retrospective_-Why-the-X-Outage-Made-Independent-Monitoring-Essential_940x600_Featured-Image.png","width":1410,"height":900},{"@type":"BreadcrumbList","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/silence-during-chaos-why-the-x-outage-is-a-call-to-arms-for-independent-monitoring#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.logicmonitor.com\/"},{"@type":"ListItem","position":2,"name":"Outage Retrospective: Why the X Outage Made Independent Monitoring Essential"}]},{"@type":"WebSite","@id":"https:\/\/www.logicmonitor.com\/fr\/#website","url":"https:\/\/www.logicmonitor.com\/fr\/","name":"LogicMonitor","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.logicmonitor.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Person","@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def","name":"destiny.setzer@logicmonitor.com"}]}},"_links":{"self":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/619183","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/users\/16"}],"replies":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/comments?post=619183"}],"version-history":[{"count":4,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/619183\/revisions"}],"predecessor-version":[{"id":624063,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/619183\/revisions\/624063"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/media\/624037"}],"wp:attachment":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/media?parent=619183"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/categories?post=619183"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/tags?post=619183"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/industry?post=619183"},{"taxonomy":"role","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/role?post=619183"},{"taxonomy":"lm_strategic_tags","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/lm_strategic_tags?post=619183"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/topic?post=619183"},{"taxonomy":"author_attribution","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/author_attribution?post=619183"},{"taxonomy":"lm_product","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/lm_product?post=619183"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":619163,"date":"2026-09-01T12:24:01","date_gmt":"2026-09-01T17:24:01","guid":{"rendered":"https:\/\/www.logicmonitor.com\/?p=619163"},"modified":"2026-09-02T12:02:56","modified_gmt":"2026-09-02T17:02:56","slug":"traceroute-insession-a-traceroute-tool-for-modern-networks","status":"publish","type":"post","link":"https:\/\/www.logicmonitor.com\/fr\/blog\/traceroute-insession-a-traceroute-tool-for-modern-networks","title":{"rendered":"Traceroute InSession : un outil de traceroute pour les r\u00e9seaux modernes"},"content":{"rendered":"<?xml encoding=\"UTF-8\"><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50 rtc-text-content--no-top-pad\">\n      <span class=\"head-icon\"><svg class=\"\" width=\"50px\" height=\"50px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-light-book-open\"><\/use>\n    <\/svg><\/span>\n  \n  <div class=\"rtc-text-content__wrapper\">\n          <h4 class=\"rtc-text-content__headline fs-sm-text-display-xs fs-md-text-display-sm fs-lg-text-display-md font-medium text-core-blue-900\">\n        The quick download:      <\/h4>\n    \n          <div class=\"rtc-text-content__body fs-sm-text-md fs-md-text-lg fs-lg-text-lg text-core-blue-900 headline-is-quote\">\n        <p>Traceroute InSession fixes the two problems that make traditional traceroute misleading on modern networks.<\/p>\n      <\/div>\n    \n                  <ul class=\"rtc-text-content__bullet-list\">\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>Firewalls often block standard traceroute packets and show them as packet loss that isn&rsquo;t really there.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>Standard traceroute reports how far each router is from the source, not whether those routers actually connect.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>By mimicking a TCP session, InSession slips past firewalls and holds one consistent path through per-flow load balancers, with low load on the destination server.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>Try the open-source code on GitHub, then run it at scale across many vantage points with LogicMonitor Synthetics and Internet Performance Monitoring.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                  <\/ul>\n      \n      \n            <\/div>\n<\/div><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">Traceroute has been a trusted network diagnostic tool for decades. When applications slow down or users experience connectivity issues, it&rsquo;s often the first tool engineers use to determine whether the problem lies within their own infrastructure, somewhere on the Internet, or at the destination. But today&rsquo;s Internet is far more complex than the one traceroute was originally designed for. Firewalls, load balancers, CDNs, and dynamic routing can all make traditional traceroute results incomplete&mdash;or even misleading.<\/p><p class=\"wp-block-paragraph\">Years of analyzing billions of traceroutes across backbone networks, cloud regions, enterprise environments, wireless providers, and endpoint devices have revealed both the strengths and limitations of traditional traceroute. This article explores those limitations, explains why they occur, and shows how Traceroute InSession addresses them.<\/p><h2 id=\"h-understanding-the-limitations-of-traditional-traceroute\" class=\"wp-block-heading\">Understanding the limitations of traditional traceroute<\/h2><p class=\"wp-block-paragraph\">With standard traceroute, the results all too often look something like this:<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1429\" height=\"449\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-67.png\" alt=\"\" class=\"wp-image-619167\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-67.png 1429w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-67-18x6.png 18w\" sizes=\"auto, (max-width: 1429px) 100vw, 1429px\"><\/figure><p class=\"wp-block-paragraph\">This example shows a TCP traceroute from one of our backbone nodes in New York connected to Cogent Communications, to Amazon. As expected, Amazon uses a CDN to serve traffic from different edge locations, so the traceroute reaches five different destinations across repeated runs. This behavior is anticipated and normal.<\/p><h3 id=\"h-why-firewalls-interfere-with-traceroute\" class=\"wp-block-heading\">Why firewalls interfere with traceroute<\/h3><p class=\"wp-block-paragraph\">So what&rsquo;s not expected? The red dots and all the crossed lines. The red dots show packet loss, but in reality the Internet isn&rsquo;t <em>that<\/em> broken. Rather than packet loss, this is likely the result of firewalls blocking some of the traceroute packets. We&rsquo;ll call this <strong><em>the firewalls problem<\/em><\/strong>.<\/p><h3 id=\"h-why-traceroute-cant-accurately-reveal-network-paths\" class=\"wp-block-heading\">Why traceroute can&rsquo;t accurately reveal network paths<\/h3><p class=\"wp-block-paragraph\">All the crossed lines suggest a very complex router topology, except that&rsquo;s not true either. We&rsquo;ll call this <strong><em>the paths problem<\/em><\/strong>. In fact, standard traceroute cannot reveal the path that a packet takes. That&rsquo;s deeply counter-intuitive: traceroute is meant to trace the route, yet what it actually tells you is that it encountered one router X hops away and another router Y hops away. It has no way to prove whether the routers are connected or what&rsquo;s between them.<\/p><p class=\"wp-block-paragraph\">To explain the paths problem further, let&rsquo;s look at an individual traceroute run:<\/p><pre class=\"wp-block-code\"><code>Traceroute to www.amazon.com (18.164.107.218), 30 hops max\n 1  gateway (38.101.106.65) [AS174]  0 ms  0 ms  0 ms\n 2  * * *\n 3  te0-0-0-1.ccr31.jfk04.atlas.cogentco.com (154.54.5.177) [AS174]  1 ms  1 ms  1 ms\n 4  be3363.ccr42.jfk02.atlas.cogentco.com (154.54.3.125) [AS174]  2 ms  1 ms  1 ms\n 5  be3201.rcr52.ewr01.atlas.cogentco.com (154.54.90.62) [AS174]  2 ms  2 ms  2 ms\n 6  38.142.215.210 (38.142.215.210) [AS174]  2 ms  2 ms  2 ms\n 7  * * *\n 8  * * *\n 9  * * *\n10  * * *\n11  15.230.208.23 (15.230.208.23)  2 ms  2 ms  2 ms\n12  15.230.208.23 (15.230.208.23)  2 ms  2 ms  2 ms\n13  server-18-164-107-218.jfk50.r.cloudfront.net (18.164.107.218) [AS16509]  2 ms  2 ms  2 ms<\/code><\/pre><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">This output indicates that the traceroute went to the gateway, then to the jfk04 Cogent router, then the jfk02 router, and so on, right?<\/p><p class=\"wp-block-paragraph\"><strong>WRONG!<\/strong><\/p><p class=\"wp-block-paragraph\">What it actually shows is that one packet from the traceroute took a path through the gateway and found that it was one hop away from the source. Another packet took a path through jfk04 and found that it was three hops away from the source. A third took a path through jfk02 and found that it was four hops away from the source, and so forth. Each packet in a traditional traceroute operates independently. The traceroute output reveals only the distance of each router from the source, not whether they are interconnected.<\/p><p class=\"wp-block-paragraph\">Another limitation is that a single traceroute cannot determine whether all possible routers have been identified. <a href=\"https:\/\/www.logicmonitor.com\/logicmonitor-catchpoint\">Catchpoint, now part of LogicMonitor<\/a>, and others addressed this challenge long ago by running repeated traceroutes. Since each traceroute may discover a different subset of routers, combining the results from many runs provides a more complete view of the network path. That&rsquo;s how the diagram at the top was generated. Each traceroute identified one router at each hop, and repeated runs made it possible to identify the full set of observed routers with a high degree of confidence.<\/p><h2 id=\"h-how-traceroute-insession-overcomes-firewall-and-path-limitations\" class=\"wp-block-heading\">How Traceroute InSession overcomes firewall and path limitations<\/h2><p class=\"wp-block-paragraph\">Traceroute InSession was designed to address the two remaining challenges: firewalls causing so-called &ldquo;packet loss&rdquo; and the incorrect assumption that routers are adjacent when they might not be.<\/p><p class=\"wp-block-paragraph\">The result is a diagram that looks like this for the example above:<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1600\" height=\"570\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-70.png\" alt=\"\" class=\"wp-image-619171\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-70.png 1600w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-70-18x6.png 18w\" sizes=\"auto, (max-width: 1600px) 100vw, 1600px\"><\/figure><p class=\"wp-block-paragraph\">Far fewer red dots (none in this example) and much cleaner lines that provide a much higher degree of confidence that adjacent routers are actually connected.<\/p><p class=\"wp-block-paragraph\">How does it work? The following sections explain the approach and include a link to the open-source implementation. For readers interested in the technical background, the next section revisits the fundamentals of traceroute.<\/p><p class=\"wp-block-paragraph\">Those who prefer to skip ahead can jump directly to the solution.<\/p><h2 id=\"h-a-brief-history-of-traceroute\" class=\"wp-block-heading\">A brief history of traceroute<\/h2><p class=\"wp-block-paragraph\">Traceroute was developed as a diagnostic tool to identify the journey of a packet through an IP network and to assess the pathway&rsquo;s performance. Before IP networks, traceroute didn&rsquo;t need to exist. Maybe it could have, but the Internet&rsquo;s simplicity at the time didn&rsquo;t demand such a tool. To illustrate, this is what the Internet looked like in 1984:<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1438\" height=\"866\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-73.png\" alt=\"\" class=\"wp-image-619174\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-73.png 1438w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-73-18x12.png 18w\" sizes=\"auto, (max-width: 1438px) 100vw, 1438px\"><\/figure><p class=\"wp-block-paragraph\">Compare that to what the Internet looks like nowadays:<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"864\" height=\"916\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-74.png\" alt=\"\" class=\"wp-image-619175\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-74.png 864w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-74-11x12.png 11w\" sizes=\"auto, (max-width: 864px) 100vw, 864px\"><\/figure><p class=\"wp-block-paragraph\">There&rsquo;s a lot of complexity, and complexity calls for tools to decipher it. This principle is a recurring theme in our discussion.<\/p><p class=\"wp-block-paragraph\">In the 1980s, the Internet Protocol (IP), created in 1974 by Vint Cerf and Bob Kahn, was still a novel concept. <em>Ping<\/em> was introduced in 1983 to measure the latency between a client and a destination. Following this, in 1988, Van Jacobson wrote the now-famous &ldquo;traceroute email&rdquo;:<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"440\" height=\"302\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-69.png\" alt=\"\" class=\"wp-image-619170\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-69.png 440w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-69-18x12.png 18w\" sizes=\"auto, (max-width: 440px) 100vw, 440px\"><\/figure><p class=\"wp-block-paragraph\">The level of complexity had reached a point where a specialized tool became necessary.<\/p><h2 id=\"h-how-does-traceroute-work\" class=\"wp-block-heading\">How does traceroute work?<\/h2><p class=\"wp-block-paragraph\">Van Jacobson created the original traceroute in 1987 using the IP Time To Live (TTL) field. This field specifies the maximum number of routers a packet can pass through. Each time it&rsquo;s routed, the field is decremented. When it reaches 0, an error message (ICMP TTL Exceeded for IPv4 or Hop Limit Exceeded for IPv6) is sent back.<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1426\" height=\"542\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-72.png\" alt=\"\" class=\"wp-image-619173\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-72.png 1426w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-72-18x7.png 18w\" sizes=\"auto, (max-width: 1426px) 100vw, 1426px\"><\/figure><h3 id=\"h-why-modern-networks-challenge-traditional-traceroute\" class=\"wp-block-heading\">Why modern networks challenge traditional traceroute<\/h3><p class=\"wp-block-paragraph\">The original algorithm implemented by Van Jacobson works for a lot of scenarios today, but the complexities of modern networks mean the algorithm has to be enhanced to work properly. Specifically, traceroute struggles with firewalls and load balancers.<\/p><h3 id=\"h-how-firewalls-affect-traceroute-accuracy\" class=\"wp-block-heading\">How firewalls affect traceroute accuracy<\/h3><p class=\"wp-block-paragraph\">Security is a perpetual cat-and-mouse game. Each technological advance is met with exploitation by malicious actors, which leads to further innovations designed to close those loopholes. This is exactly what happened with traceroute.<\/p><p class=\"wp-block-paragraph\">ICMP traceroute often fails in modern networks because ICMP messages are generally used for diagnostic purposes and rarely carry application data. Many firewalls block them entirely.<\/p><p class=\"wp-block-paragraph\">Similarly, with UDP traceroute, firewalls often block it because it doesn&rsquo;t <em>look<\/em> like application traffic. There isn&rsquo;t a common UDP application that traceroute imitates, so firewalls block the packets.<\/p><p class=\"wp-block-paragraph\">For a while, TCP traceroute was the preferred approach. Because every TCP connection begins with a three-way handshake, firewalls couldn&rsquo;t inspect application data at that stage, so SYN packets were generally allowed through. That changed as attackers began exploiting SYN-based denial-of-service attacks. As firewalls evolved to detect and mitigate this traffic, TCP traceroute became less reliable. (The extent of the impact depends on how SYN attack detection is implemented and where rate thresholds are configured.)<\/p><h3 id=\"h-how-load-balancers-complicate-traceroute\" class=\"wp-block-heading\">How load balancers complicate traceroute<\/h3><p class=\"wp-block-paragraph\">The Internet is fragile. One of the technologies that helps improve its resilience is load balancers, specifically link load balancers.<\/p><p class=\"wp-block-paragraph\">In this context, a load balancer can be considered a specialized router that decides where to send a packet, not by the packet&rsquo;s destination network (that&rsquo;s what every router does) but by various other criteria. For example, cost-related policies might direct important application traffic over more expensive links for reliability, or resilience considerations might reroute traffic via a backup link if the primary route is too slow. These decisions lead to scenarios such as the following:<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1430\" height=\"441\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-71.png\" alt=\"\" class=\"wp-image-619172\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-71.png 1430w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-71-18x6.png 18w\" sizes=\"auto, (max-width: 1430px) 100vw, 1430px\"><\/figure><p class=\"wp-block-paragraph\">Looking at this diagram without any outside knowledge, it&rsquo;s impossible to know which path a particular packet might take to reach the server. Maybe 1-2-5? Or 1-3-4? Or 1-2-4?<\/p><p class=\"wp-block-paragraph\">Load balancers are generally configured to balance <em>flow<\/em> traffic. If a TCP connection is established using a particular path, the load balancer will try to keep the same path for every packet in that connection. The same principles apply to UDP flows.<\/p><p class=\"wp-block-paragraph\">With traceroute, though, a &ldquo;flow&rdquo; is a single packet and response. Each probe sent out has different characteristics and may get load balanced to a different path.<\/p><p class=\"wp-block-paragraph\">This variability can lead to some very strange traceroute responses. For example, in the diagram above, Hop 1 will always be router 1. Hop 2 could be Router 2 or Router 3. Hop 3 could be Router 4 or Router 5. Hop 4 is the Server. So if you ran a traceroute and saw output like this:<\/p><pre class=\"wp-block-code\"><code>1 (Router 1)\n\n2 (Router 2)\n\n(Router 3)\n\n3 (Router 4)\n\n(Router 5)\n\n4 (Server)<\/code><\/pre><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">How do you know what the actual path is? You could assume, for example, that a possible flow is 1-2-4, but that isn&rsquo;t a path that exists.<\/p><h2 id=\"h-navigating-complexity-introducing-traceroute-insession\" class=\"wp-block-heading\">Navigating complexity: Introducing Traceroute InSession<\/h2><p class=\"wp-block-paragraph\">The complexities introduced by firewalls and load balancers have made the original traceroute less useful than it once was. To address these challenges, Catchpoint developed and open-sourced Traceroute InSession.<\/p><p class=\"wp-block-paragraph\">You can read our original blog post for a detailed explanation of <a href=\"https:\/\/www.logicmonitor.com\/blog\/traceroute-insession-catchpoints-effort-towards-a-more-reliable-network-diagnostic-tool\">how Traceroute InSession works<\/a>. Below is a brief overview.<\/p><p class=\"wp-block-paragraph\">InSession imitates TCP connections by establishing a TCP connection to the destination server, so a firewall lets it through. Also, by using a single TCP connection, load balancers use a consistent path for every probe because each is treated as the same flow.<\/p><p class=\"wp-block-paragraph\">Here&rsquo;s the result:<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1267\" height=\"295\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-68.png\" alt=\"\" class=\"wp-image-619169\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-68.png 1267w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-68-18x4.png 18w\" sizes=\"auto, (max-width: 1267px) 100vw, 1267px\"><\/figure><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"606\" height=\"241\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-10.jpeg\" alt=\"\" class=\"wp-image-619168\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-10.jpeg 606w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-10-18x7.jpeg 18w\" sizes=\"auto, (max-width: 606px) 100vw, 606px\"><\/figure><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">The first image shows many missing hops, with multiple routers returned for hops 5 to 9 and just one of three probes successfully reaching the destination (hop 13) because a firewall blocked the others.<\/p><p class=\"wp-block-paragraph\">The InSession version in the second image shows a marked improvement: most hops return data, the path is consistent with only one response per path, and all three probes succeed in reaching their destination.<\/p><h2 id=\"h-comparing-traceroute-insession-with-sidecar\" class=\"wp-block-heading\">Comparing Traceroute InSession with SideCar<\/h2><p class=\"wp-block-paragraph\">Sidecar is the algorithm that inspired InSession. It essentially sets up an actual TCP connection or sends data over an existing one. By doing this, it also bypasses firewall detection and causes load balancers to use a consistent path.<\/p><p class=\"wp-block-paragraph\">The problem with Sidecar is that it sends actual data over a connection to a real server application, which means the destination server has to process that data. The data has to look real enough for the server to reply. With InSession, we use two useful TCP options to prevent this additional load from being added to the server: congestion control and SACK.<\/p><p class=\"wp-block-paragraph\">Congestion control means that if there&rsquo;s a gap in the sequence numbers received by the server, the packets won&rsquo;t be delivered to the application until the gap is filled, a gap that remains unfilled because we put it there deliberately.<\/p><p class=\"wp-block-paragraph\">SACK, or selective acknowledgment, lets the server respond to the client and tell us which sequence numbers made it and which didn&rsquo;t. Without it, ACK packets wouldn&rsquo;t be generated until the gap in sequence numbers is filled.<\/p><h2 id=\"h-comparing-traceroute-insession-with-paris-traceroute\" class=\"wp-block-heading\">Comparing Traceroute InSession with Paris traceroute<\/h2><p class=\"wp-block-paragraph\">Catchpoint offered Paris traceroute as an option for about ten years and found that customers generally didn&rsquo;t use it, and when they did, it caused traceroute failures from locations that had previously operated successfully, more often than not. So the company decided to replace the Paris traceroute option with InSession.<\/p><p class=\"wp-block-paragraph\">Paris traceroute shares a common objective with InSession: to let traceroutes work amid routers that employ load balancing on packet header fields. This means that in our earlier New York to Amazon TCP traceroute scenario, the adjacent routers would be correctly identified.<\/p><p class=\"wp-block-paragraph\">However, <a href=\"https:\/\/paris-traceroute.net\/about\/\">Paris traceroute<\/a> runs into two significant issues. First, it relies on a stream of SYN packets similar to traditional TCP traceroute, so firewalls often block it. In our New York to Amazon TCP traceroute scenario, the red dots would still be there. Second, the algorithm is fairly complex because it manipulates different fields inside the packet header:<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"472\" height=\"335\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-9.jpeg\" alt=\"\" class=\"wp-image-619166\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-9.jpeg 472w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-9-18x12.jpeg 18w\" sizes=\"auto, (max-width: 472px) 100vw, 472px\"><\/figure><p class=\"wp-block-paragraph\">Imagine explaining to your security team how this application works and why it isn&rsquo;t malicious. In contrast, InSession simply transmits standard, unmanipulated TCP packets, albeit intentionally skipping one to create a sequence number gap.<\/p><p class=\"wp-block-paragraph\">While Paris traceroute is available for ICMP, UDP, and TCP protocols, InSession operates solely on TCP. Based on our observations, if firewalls block standard traceroute, they&rsquo;ll block Paris ICMP and UDP as well. Since InSession runs over a mimicked TCP session, it has proven more reliable in environments where firewalls may drop packets due to SYN flooding, a vulnerability in regular TCP traceroute implementations, including Paris traceroute.<\/p><h2 id=\"h-other-traceroute-variants-and-where-they-fit\" class=\"wp-block-heading\">Other traceroute variants and where they fit<\/h2><p class=\"wp-block-paragraph\">There are several other variants of traceroute. Dublin Traceroute is an add-on to Paris for NAT detection. Pamplona Traceroute attempts to identify IP responses that belong to the same router, also known as aliases.<\/p><p class=\"wp-block-paragraph\">Ultimately, you should use the tool that solves your problem and lets you navigate the complexity of your environment. We&rsquo;re convinced that for most people, Traceroute InSession is the best choice.<\/p><h3 id=\"h-comparing-traceroute-variants-at-a-glance\" class=\"wp-block-heading\">Comparing traceroute variants at a glance<\/h3><figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>Approach<\/strong><\/td><td><strong>Gets past firewalls<\/strong><\/td><td><strong>Consistent path through load balancers<\/strong><\/td><td><strong>Load on destination server<\/strong><\/td><td><strong>Protocols<\/strong><\/td><\/tr><tr><td>Standard traceroute<\/td><td>Often blocked<\/td><td>No, each probe can take a different path<\/td><td>Minimal<\/td><td>ICMP, UDP, TCP<\/td><\/tr><tr><td>Paris traceroute<\/td><td>Often blocked, still relies on SYN packets<\/td><td>Yes, for per-flow load balancers<\/td><td>Minimal<\/td><td>ICMP, UDP, TCP<\/td><\/tr><tr><td>SideCar<\/td><td>Yes, rides a real TCP connection<\/td><td>Yes, for per-flow load balancers<\/td><td>Higher, the server processes real application data<\/td><td>TCP<\/td><\/tr><tr><td>Traceroute InSession<\/td><td>Yes, mimics a TCP session<\/td><td>Yes, for per-flow load balancers<\/td><td>Low, congestion control and SACK avoid extra processing<\/td><td>TCP<\/td><\/tr><\/tbody><\/table><\/figure><h2 id=\"h-important-considerations-when-using-traceroute-insession\" class=\"wp-block-heading\">Important considerations when using Traceroute InSession<\/h2><p class=\"wp-block-paragraph\">While Traceroute InSession addresses many of the limitations of traditional traceroute, it&rsquo;s important to keep two considerations in mind:<\/p><ul class=\"wp-block-list\">\n<li><strong>It handles per-flow load balancers, not per-packet ones.<\/strong> Per-packet load balancers are rare in our experience, so InSession still solves most users&rsquo; issues. As far as we know, no algorithm has solved the per-packet load balancer problem.<\/li>\n\n\n\n<li><strong>It reports paths, it doesn&rsquo;t discover them.<\/strong> Like all traceroute implementations, InSession only <em>reports<\/em> the paths it finds, so a single output can&rsquo;t tell you whether every possible path has been found.<\/li>\n<\/ul><p class=\"wp-block-paragraph\"><a href=\"https:\/\/github.com\/catchpoint\/Pietrasanta-traceroute\"><strong>Access the code on GitHub<\/strong><\/a>, along with some<a href=\"https:\/\/github.com\/catchpoint\/Pietrasanta-traceroute\/tree\/main\/binaries\"> <strong>pre-built binaries<\/strong><\/a> to explore further.<\/p><h2 id=\"h-extending-traceroute-with-internet-performance-monitoring\" class=\"wp-block-heading\">Extending traceroute with Internet Performance Monitoring<\/h2><p class=\"wp-block-paragraph\">The way to get a complete picture of Internet routing is to run many traceroutes from multiple vantage points and across repeated runs, then view all of the paths in a single network graph. <a href=\"https:\/\/www.logicmonitor.com\/internet-performance-monitoring\">LogicMonitor Synthetics and Internet Performance Monitoring<\/a> enable you to do just that. That path-level view becomes more useful inside the broader LogicMonitor platform, which unifies<a href=\"https:\/\/www.logicmonitor.com\/infrastructure-monitoring\"> LM Envision<\/a>, LM Internet Performance Monitoring, and<a href=\"https:\/\/www.logicmonitor.com\/edwin-ai\"> Edwin AI<\/a>, so teams can connect what&rsquo;s happening on the Internet path to the health of their own infrastructure.<\/p><p class=\"wp-block-paragraph\"><\/p><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50\">\n      <span class=\"head-icon\"><svg class=\"\" width=\"50px\" height=\"50px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-light-calendar-check\"><\/use>\n    <\/svg><\/span>\n  \n  <div class=\"rtc-text-content__wrapper\">\n          <h4 class=\"rtc-text-content__headline fs-sm-text-display-xxs fs-md-text-display-xs fs-lg-text-display-sm font-medium text-core-blue-900\">\n        Map your real Internet paths across every vantage point.      <\/h4>\n    \n          <div class=\"rtc-text-content__body fs-sm-text-md fs-md-text-lg fs-lg-text-lg text-core-blue-900 \">\n        <p>Run Traceroute InSession from locations worldwide and combines the results into a single clear network graph, enabling you to connect what happens on the Internet path to the health of your own infrastructure on a single platform.<\/p>\n      <\/div>\n    \n          \n      \n              <div>\n            <a href=\"https:\/\/www.logicmonitor.com\/catchpoint-demo\" class=\"btn btn-link\" target=\"_self\">\n        Request a Demo          <span class=\"icon-end\"><svg class=\"\" width=\"20px\" height=\"20px\" style=\"fill: #060F4B\">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-arrow-right\"><\/use>\n    <\/svg><\/span>\n      <\/a>\n        <\/div>\n            <\/div>\n<\/div><h4 id=\"h-faqs\" class=\"wp-block-heading\">FAQs<\/h4><div class=\"accordion-block accordion-block--light\">\n      <div class=\"accordion-block__items\">\n              <div class=\"accordion-block__item active\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-why-does-traditional-traceroute-show-packet-loss-that-isnt-real\">\n            Why does traditional traceroute show packet loss that isn't real?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer active\">\n            <p>Many firewalls block ICMP and UDP traceroute packets because they don&rsquo;t look like application traffic. TCP traceroute used to get through on SYN packets, but firewalls now drop those to defend against SYN-based attacks. The blocked probes appear as packet loss even when the network is healthy.<\/p>\n                      <\/div>\n        <\/div>\n              <div class=\"accordion-block__item \">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-how-does-traceroute-insession-get-more-accurate-results\">\n            How does Traceroute InSession get more accurate results?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer \">\n            <p>InSession imitates a real TCP connection to the destination, so firewalls let it through. Because every probe belongs to the same flow, per-flow load balancers keep it on one consistent path. It also uses congestion control and SACK to keep the load on the destination server low.<\/p>\n                      <\/div>\n        <\/div>\n              <div class=\"accordion-block__item \">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-how-is-insession-different-from-sidecar-and-paris-traceroute\">\n            How is InSession different from SideCar and Paris traceroute?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer \">\n            <p>SideCar rides a real TCP connection and gets past firewalls, but the server has to process real application data, which adds load. Paris traceroute keeps a consistent path through load balancers, yet it still relies on SYN packets that firewalls often block. InSession mimics a TCP session to clear firewalls and holds a consistent path while keeping server load low.<\/p>\n                      <\/div>\n        <\/div>\n          <\/div>\n  <\/div>\n","protected":false},"excerpt":{"rendered":"<p>D\u00e9couvrez pourquoi le traceroute traditionnel interpr\u00e8te mal les r\u00e9seaux d'aujourd'hui et comment Traceroute InSession contourne les pare-feu et les r\u00e9partiteurs de charge pour r\u00e9v\u00e9ler le v\u00e9ritable chemin.<\/p>","protected":false},"author":16,"featured_media":624035,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"unicorn_plugin_options_block_body_class":"","footnotes":""},"categories":[5035],"tags":[7850,7800,7907,7863,7917,6677,7797,7798,7871,7084],"industry":[6790],"role":[6786],"lm_strategic_tags":[],"topic":[7842],"author_attribution":[7967],"lm_product":[],"class_list":["post-619163","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","industry-all","role-itops","topic-internet-performance-monitoring","author_attribution-denton-chikura"],"acf":{"page_language":"english","translated_pages":"","updated_date":null,"author_section_checkbox":true,"author_image":617027,"author_linkedin":"https:\/\/www.linkedin.com\/in\/denton-chikura-422186201\/","author_name":"Denton Chikura","author_job_title":"Technical Writer","author_dept":"","author_bio":"Denton Chikura is a technical writer and longtime observability advocate focused on helping site reliability engineers and engineering teams discover the tools and capabilities that strengthen internet resilience. He works at the intersection of monitoring, performance, and infrastructure to make complex systems more understandable and usable, bridging the gap between deep technical detail and real\u2011world operations. His goal is to help teams build faster, detect issues earlier, and recover smarter, ultimately making the internet a better, more reliable place for everyone.","reviewer_name":""},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.4 (Yoast SEO v28.4) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Traceroute InSession: Modern Network Diagnostics | LogicMonitor<\/title>\n<meta name=\"description\" content=\"Traceroute InSession by Catchpoint improves network diagnostics by addressing firewall-induced &quot;packet loss&quot; and misconceptions about router adjacency.\" \/>\n<meta name=\"robots\" content=\"noindex, nofollow\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Traceroute InSession: A Traceroute Tool for Modern Networks\" \/>\n<meta property=\"og:description\" content=\"Traceroute InSession by Catchpoint improves network diagnostics by addressing firewall-induced &quot;packet loss&quot; and misconceptions about router adjacency.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.logicmonitor.com\/fr\/blog\/traceroute-insession-a-traceroute-tool-for-modern-networks\" \/>\n<meta property=\"og:site_name\" content=\"LogicMonitor\" \/>\n<meta property=\"article:published_time\" content=\"2026-09-01T17:24:01+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-09-02T17:02:56+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/Blog_Traceroute-InSession_-A-Traceroute-Tool-for-Modern-Networks_Meta-1600x900px.png\" \/>\n\t<meta property=\"og:image:width\" content=\"2400\" \/>\n\t<meta property=\"og:image:height\" content=\"1350\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"destiny.setzer@logicmonitor.com\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"13 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/traceroute-insession-a-traceroute-tool-for-modern-networks#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/traceroute-insession-a-traceroute-tool-for-modern-networks\"},\"author\":{\"name\":\"destiny.setzer@logicmonitor.com\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\"},\"headline\":\"Traceroute InSession: A Traceroute Tool for Modern Networks\",\"datePublished\":\"2026-09-01T17:24:01+00:00\",\"dateModified\":\"2026-09-02T17:02:56+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/traceroute-insession-a-traceroute-tool-for-modern-networks\"},\"wordCount\":2394,\"image\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/traceroute-insession-a-traceroute-tool-for-modern-networks#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Blog_Traceroute-InSession_-A-Traceroute-Tool-for-Modern-Networks_940x600_Featured-Image.png\",\"keywords\":[\"Catchpoint\",\"Firewalls\",\"ISP Performance\",\"Network Path Analysis\",\"Packet Loss\",\"Performance optimization\",\"Routers\",\"Switches\",\"Traceroute\",\"Troubleshooting\"],\"articleSection\":[\"Blog\"],\"inLanguage\":\"fr-FR\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/traceroute-insession-a-traceroute-tool-for-modern-networks\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/traceroute-insession-a-traceroute-tool-for-modern-networks\",\"name\":\"Traceroute InSession: Modern Network Diagnostics | LogicMonitor\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/traceroute-insession-a-traceroute-tool-for-modern-networks#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/traceroute-insession-a-traceroute-tool-for-modern-networks#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Blog_Traceroute-InSession_-A-Traceroute-Tool-for-Modern-Networks_940x600_Featured-Image.png\",\"datePublished\":\"2026-09-01T17:24:01+00:00\",\"dateModified\":\"2026-09-02T17:02:56+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\"},\"description\":\"Traceroute InSession by Catchpoint improves network diagnostics by addressing firewall-induced \\\"packet loss\\\" and misconceptions about router adjacency.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/traceroute-insession-a-traceroute-tool-for-modern-networks#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/traceroute-insession-a-traceroute-tool-for-modern-networks\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/traceroute-insession-a-traceroute-tool-for-modern-networks#primaryimage\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Blog_Traceroute-InSession_-A-Traceroute-Tool-for-Modern-Networks_940x600_Featured-Image.png\",\"contentUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Blog_Traceroute-InSession_-A-Traceroute-Tool-for-Modern-Networks_940x600_Featured-Image.png\",\"width\":1410,\"height\":900},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/traceroute-insession-a-traceroute-tool-for-modern-networks#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.logicmonitor.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Traceroute InSession: A Traceroute Tool for Modern Networks\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#website\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/\",\"name\":\"LogicMonitor\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\",\"name\":\"destiny.setzer@logicmonitor.com\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Traceroute InSession: Modern Network Diagnostics | LogicMonitor","description":"Traceroute InSession by Catchpoint improves network diagnostics by addressing firewall-induced \"packet loss\" and misconceptions about router adjacency.","robots":{"index":"noindex","follow":"nofollow"},"og_locale":"fr_FR","og_type":"article","og_title":"Traceroute InSession: A Traceroute Tool for Modern Networks","og_description":"Traceroute InSession by Catchpoint improves network diagnostics by addressing firewall-induced \"packet loss\" and misconceptions about router adjacency.","og_url":"https:\/\/www.logicmonitor.com\/fr\/blog\/traceroute-insession-a-traceroute-tool-for-modern-networks","og_site_name":"LogicMonitor","article_published_time":"2026-09-01T17:24:01+00:00","article_modified_time":"2026-09-02T17:02:56+00:00","og_image":[{"url":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/Blog_Traceroute-InSession_-A-Traceroute-Tool-for-Modern-Networks_Meta-1600x900px.png","width":2400,"height":1350,"type":"image\/png"}],"author":"destiny.setzer@logicmonitor.com","twitter_card":"summary_large_image","twitter_misc":{"Written by":"","Est. reading time":"13 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/traceroute-insession-a-traceroute-tool-for-modern-networks#article","isPartOf":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/traceroute-insession-a-traceroute-tool-for-modern-networks"},"author":{"name":"destiny.setzer@logicmonitor.com","@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def"},"headline":"Traceroute InSession: A Traceroute Tool for Modern Networks","datePublished":"2026-09-01T17:24:01+00:00","dateModified":"2026-09-02T17:02:56+00:00","mainEntityOfPage":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/traceroute-insession-a-traceroute-tool-for-modern-networks"},"wordCount":2394,"image":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/traceroute-insession-a-traceroute-tool-for-modern-networks#primaryimage"},"thumbnailUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/Blog_Traceroute-InSession_-A-Traceroute-Tool-for-Modern-Networks_940x600_Featured-Image.png","keywords":["Catchpoint","Firewalls","ISP Performance","Network Path Analysis","Packet Loss","Performance optimization","Routers","Switches","Traceroute","Troubleshooting"],"articleSection":["Blog"],"inLanguage":"fr-FR"},{"@type":"WebPage","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/traceroute-insession-a-traceroute-tool-for-modern-networks","url":"https:\/\/www.logicmonitor.com\/fr\/blog\/traceroute-insession-a-traceroute-tool-for-modern-networks","name":"Traceroute InSession: Modern Network Diagnostics | LogicMonitor","isPartOf":{"@id":"https:\/\/www.logicmonitor.com\/fr\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/traceroute-insession-a-traceroute-tool-for-modern-networks#primaryimage"},"image":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/traceroute-insession-a-traceroute-tool-for-modern-networks#primaryimage"},"thumbnailUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/Blog_Traceroute-InSession_-A-Traceroute-Tool-for-Modern-Networks_940x600_Featured-Image.png","datePublished":"2026-09-01T17:24:01+00:00","dateModified":"2026-09-02T17:02:56+00:00","author":{"@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def"},"description":"Traceroute InSession by Catchpoint improves network diagnostics by addressing firewall-induced \"packet loss\" and misconceptions about router adjacency.","breadcrumb":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/traceroute-insession-a-traceroute-tool-for-modern-networks#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.logicmonitor.com\/fr\/blog\/traceroute-insession-a-traceroute-tool-for-modern-networks"]}]},{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/traceroute-insession-a-traceroute-tool-for-modern-networks#primaryimage","url":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/Blog_Traceroute-InSession_-A-Traceroute-Tool-for-Modern-Networks_940x600_Featured-Image.png","contentUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/Blog_Traceroute-InSession_-A-Traceroute-Tool-for-Modern-Networks_940x600_Featured-Image.png","width":1410,"height":900},{"@type":"BreadcrumbList","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/traceroute-insession-a-traceroute-tool-for-modern-networks#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.logicmonitor.com\/"},{"@type":"ListItem","position":2,"name":"Traceroute InSession: A Traceroute Tool for Modern Networks"}]},{"@type":"WebSite","@id":"https:\/\/www.logicmonitor.com\/fr\/#website","url":"https:\/\/www.logicmonitor.com\/fr\/","name":"LogicMonitor","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.logicmonitor.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Person","@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def","name":"destiny.setzer@logicmonitor.com"}]}},"_links":{"self":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/619163","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/users\/16"}],"replies":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/comments?post=619163"}],"version-history":[{"count":5,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/619163\/revisions"}],"predecessor-version":[{"id":625778,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/619163\/revisions\/625778"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/media\/624035"}],"wp:attachment":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/media?parent=619163"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/categories?post=619163"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/tags?post=619163"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/industry?post=619163"},{"taxonomy":"role","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/role?post=619163"},{"taxonomy":"lm_strategic_tags","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/lm_strategic_tags?post=619163"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/topic?post=619163"},{"taxonomy":"author_attribution","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/author_attribution?post=619163"},{"taxonomy":"lm_product","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/lm_product?post=619163"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":619157,"date":"2026-09-01T12:23:47","date_gmt":"2026-09-01T17:23:47","guid":{"rendered":"https:\/\/www.logicmonitor.com\/?p=619157"},"modified":"2026-09-02T12:03:36","modified_gmt":"2026-09-02T17:03:36","slug":"mastering-ipm-the-essential-customer-experience-monitoring-framework","status":"publish","type":"post","link":"https:\/\/www.logicmonitor.com\/fr\/blog\/mastering-ipm-the-essential-customer-experience-monitoring-framework","title":{"rendered":"Mastering IPM: The Essential Customer Experience Monitoring Framework"},"content":{"rendered":"<?xml encoding=\"UTF-8\"><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50\">\n      <span class=\"head-icon\"><svg class=\"\" width=\"50px\" height=\"50px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-light-book-open\"><\/use>\n    <\/svg><\/span>\n  \n  <div class=\"rtc-text-content__wrapper\">\n          <h4 class=\"rtc-text-content__headline fs-sm-text-display-xs fs-md-text-display-sm fs-lg-text-display-md font-medium text-core-blue-900\">\n        Le t\u00e9l\u00e9chargement rapide :      <\/h4>\n    \n          <div class=\"rtc-text-content__body fs-sm-text-md fs-md-text-lg fs-lg-text-lg text-core-blue-900 headline-is-quote\">\n        <p>Internet Performance Monitoring lets you see outages the way your customers do, and catch them first.<\/p>\n      <\/div>\n    \n                  <ul class=\"rtc-text-content__bullet-list\">\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>Customer experience rests on four pillars: availability, performance, reachability, and reliability, each building on the one below it.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>Internal metrics can look healthy while DNS, CDN, certificates, or routing quietly break the user experience.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>In a December 2023 file-sharing outage, outside-in monitoring flagged critical API failures at 4:37 a.m. Pacific, before public reporting.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>Build a CX monitoring suite around your critical user journeys to shrink MTTD and protect revenue.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                  <\/ul>\n      \n      \n            <\/div>\n<\/div><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">Customer experience strongly influences whether users stay or switch. When an application feels slow, breaks partway through a transaction, or fails to load in certain regions, people move on to alternatives. That reality adds pressure on IT and operations teams to see problems the way users see them, from outside the data center and across the Internet path.<\/p><p class=\"wp-block-paragraph\">This article examines how outside-in <a href=\"https:\/\/www.logicmonitor.com\/blog\/internet-performance-monitoring-overview\">Supervision des performances Internet<\/a> can reduce Mean Time to Detect (MTTD) and give responders the evidence they need to diagnose incidents more quickly.<\/p><p class=\"wp-block-paragraph\">This work matters most to ITOps, SRE, network operations, and digital-experience teams responsible for customer-facing services. We&rsquo;ll start with the foundational elements that any digital service depends on: <strong>availability, performance, reachability, and reliability<\/strong>.<\/p><h2 id=\"h-the-four-pillars-of-monitoring-for-customer-experience\" class=\"wp-block-heading\">The four pillars of monitoring for customer experience<\/h2><p class=\"wp-block-paragraph\">Delivering a consistent customer experience (CX) takes consistency in content delivery, availability, and performance across every market you serve. Users expect applications to respond quickly, and they switch to competitors when those expectations aren&rsquo;t met.<\/p><p class=\"wp-block-paragraph\">Maslow&rsquo;s Hierarchy of Needs describes requirements that build from the basic toward the advanced. Digital services follow a similar layered order: each level depends on the one beneath it.<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1000\" height=\"667\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-66.png\" alt=\"\" class=\"wp-image-619159\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-66.png 1000w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/image-66-18x12.png 18w\" sizes=\"auto, (max-width: 1000px) 100vw, 1000px\"><\/figure><p class=\"wp-block-paragraph\">The 4 Pillars of Internet Resilience<\/p><p class=\"wp-block-paragraph\">Internet Performance Monitoring is built on four core pillars that support a strong customer experience (CX):<\/p><ul class=\"wp-block-list\">\n<li><strong>Disponibilit\u00e9 :<\/strong> True availability goes beyond an &ldquo;HTTP 200 OK&rdquo; response. It means every function of an application works as intended. A useful measure is functional transaction success: on an eCommerce site, the images and product descriptions actually load, not just the status code.<\/li>\n\n\n\n<li><strong>Performance :<\/strong> The speed and responsiveness of your application. Measure latency or user-journey duration against user expectations and your internal service objectives first. Competitive benchmarks are optional context, not the definition of performance.<\/li>\n\n\n\n<li><strong>Reachability:<\/strong> Connection success. User requests reach your server without a hitch, which sets the tone for everything that follows.<\/li>\n\n\n\n<li><strong>Fiabilit\u00e9 :<\/strong> The consistency of availability, performance, and reachability across time and geography, so users get a uniform experience across circumstances.<\/li>\n<\/ul><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">The pillars build on each other. Your service has to be up and running before anything else matters, so availability comes first. Once it&rsquo;s available, users expect it to be fast. Then they expect to reach it from anywhere in the world, or at least from every region in your target market. Finally, your service needs to stay consistent in its availability, performance, and reachability over time.<\/p><p class=\"wp-block-paragraph\">Each pillar plays an important role in the overall customer experience. Monitoring them closely helps teams identify potential incidents earlier and improve how users interact with a service.<\/p><h2 id=\"h-outside-in-versus-inside-out-visibility\" class=\"wp-block-heading\">Outside-in versus inside-out visibility<\/h2><p class=\"wp-block-paragraph\">A service can report healthy internal metrics while users still hit trouble. DNS resolution, CDN delivery, expired certificates, routing changes, or a failing third-party dependency can all break the experience even when your own servers look fine. Inside-out telemetry describes what&rsquo;s happening within your environment. Outside-in monitoring runs from the user&rsquo;s vantage point across the Internet, so you see what real users see. Together they give teams a complete view.<\/p><p class=\"wp-block-paragraph\">Outside-in monitoring is most effective when it&rsquo;s centered on critical user journeys: login, search, checkout, upload, and API calls. These are the paths that matter to the business, and they&rsquo;re the ones you want to monitor continuously.<\/p><h2 id=\"h-implementing-a-customer-experience-suite-with-ipm\" class=\"wp-block-heading\">Implementing a customer experience suite with IPM<\/h2><p class=\"wp-block-paragraph\">Here&rsquo;s a practical example of an IPM customer experience suite. It gives teams continuous visibility into the user experience and detects potential issues, such as slow website performance or security certificate errors, so they can be addressed before they affect the customer journey.<\/p><p class=\"wp-block-paragraph\">A well-designed IPM program combines outside-in testing across multiple Internet layers and locations, using established monitoring practices to identify issues before they disrupt critical user journeys.<\/p><p class=\"wp-block-paragraph\">Here&rsquo;s what a robust CX monitoring setup might include:<\/p><ul class=\"wp-block-list\">\n<li><strong>Single Object Test:<\/strong> Monitors individual elements like images or scripts to confirm they load correctly.<\/li>\n\n\n\n<li><strong>DNS Experience Test:<\/strong> Checks that the DNS resolution process works efficiently, connecting users to your website without delay.<\/li>\n\n\n\n<li><strong>Trace Route Test:<\/strong> Shows the path network traffic takes to reach your server, which helps pinpoint potential delays.<\/li>\n\n\n\n<li><strong>SSL Test:<\/strong> Checks the validity and expiration of security certificates to prevent warnings that could deter users.<\/li>\n\n\n\n<li><strong>Chrome Transaction Test:<\/strong> Simulates user interactions to test complex transactions and application flows.<\/li>\n<\/ul><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">The frequencies below are illustrative defaults, not universal recommendations. Set test frequency based on business criticality, expected rate of change, your detection objectives, geographic exposure, and how much alert noise a team can tolerate.<\/p><figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>Test Type<\/strong><\/td><td><strong>Node Type<\/strong><\/td><td><strong>Frequency (in minutes)<\/strong><\/td><td><strong>What it tells you<\/strong><\/td><\/tr><tr><td>Single Object<\/td><td>Backbone<\/td><td>5<\/td><td>Detects failure or slowdown of a critical dependency.<\/td><\/tr><tr><td>DNS Experience<\/td><td>Backbone<\/td><td>5<\/td><td>Separates name-resolution problems from application problems.<\/td><\/tr><tr><td>Trace Route<\/td><td>Backbone<\/td><td>5<\/td><td>Provides path context; should not be treated as definitive proof of packet loss.<\/td><\/tr><tr><td>SSL<\/td><td>Backbone<\/td><td>1,440 (once a day)<\/td><td>Identifies certificate expiration and validation risk.<\/td><\/tr><tr><td>Chrome Transaction<\/td><td>Backbone<\/td><td>60<\/td><td>Validates complete business journeys such as login or checkout.<\/td><\/tr><\/tbody><\/table><\/figure><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">Integrating a suite like this into your monitoring strategy gives you visibility into application performance and availability, DNS resolution, TCP layer connectivity, certificate health, and user transaction functionality, all of which support a strong customer experience.<\/p><p class=\"wp-block-paragraph\">With an ideal CX setup in mind, let&rsquo;s look at an incident involving a well-known file-sharing company, and how a similar setup supported rapid detection and a faster MTTD.<\/p><h2 id=\"h-outage-case-study-what-happened\" class=\"wp-block-heading\">Outage case study: what happened<\/h2><p class=\"wp-block-paragraph\">A significant outage struck a prominent file-sharing company on December 15, 2023, lasting from 6:00 AM to 9:11 AM Pacific Time. It affected numerous critical services, including the files tool, APIs, and user logins, and compromised the core functions of uploading and downloading. Many users couldn&rsquo;t share files or access their accounts, which disrupted both business and personal operations. This is a dated historical example rather than a recent event.<\/p><h3 id=\"h-early-detection-the-role-of-ipm\" class=\"wp-block-heading\">Early detection: the role of IPM<\/h3><p class=\"wp-block-paragraph\">One key factor in how long an outage lasts is how early you detect it.<\/p><p class=\"wp-block-paragraph\">In this case, proactive Internet Performance Monitoring played an important role. <a href=\"https:\/\/www.logicmonitor.com\/fr\/logicmonitor-catchpoint\">Catchpoint, a LogicMonitor company,<\/a> was running outside-in monitoring that detected the first signs of critical API failures at 4:37 a.m. Pacific Time, before the outage was publicly reported.<br><\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"2475\" height=\"1121\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/FIGURE-1_Mastering-IPM-The-Essential-Customer-Experience-Monitoring-Framework.png\" alt=\"\" class=\"wp-image-623974\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/FIGURE-1_Mastering-IPM-The-Essential-Customer-Experience-Monitoring-Framework.png 2475w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/FIGURE-1_Mastering-IPM-The-Essential-Customer-Experience-Monitoring-Framework-18x8.png 18w\" sizes=\"auto, (max-width: 2475px) 100vw, 2475px\"><\/figure><p class=\"wp-block-paragraph\">Historical monitoring screenshot.<\/p><h3 id=\"h-assessing-the-alert-distinguishing-false-alarms-from-genuine-threats\" class=\"wp-block-heading\">Assessing the alert: distinguishing false alarms from genuine threats<\/h3><p class=\"wp-block-paragraph\">Once an alert arrives, the next question for any team is whether it&rsquo;s worth waking someone up or whether it&rsquo;s a false positive, and whether it points to a network error or an application error.<\/p><p class=\"wp-block-paragraph\">In this case, a consistent pattern of 5XX responses was surfaced. Repeated 5XX responses indicate a server-side or upstream application failure, which signaled a genuine and substantial issue that needed urgent attention.<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"2475\" height=\"477\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/FIGURE-2_Mastering-IPM-The-Essential-Customer-Experience-Monitoring-Framework.png\" alt=\"\" class=\"wp-image-623975\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/FIGURE-2_Mastering-IPM-The-Essential-Customer-Experience-Monitoring-Framework.png 2475w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/FIGURE-2_Mastering-IPM-The-Essential-Customer-Experience-Monitoring-Framework-18x3.png 18w\" sizes=\"auto, (max-width: 2475px) 100vw, 2475px\"><\/figure><p class=\"wp-block-paragraph\">Historical monitoring screenshot.<\/p><h3 id=\"h-determining-the-scope-of-the-outage\" class=\"wp-block-heading\">Determining the scope of the outage<\/h3><p class=\"wp-block-paragraph\">A critical step for any response team is determining the outage&rsquo;s extent. Was it only the API, or were other services also affected? The answer determines the response strategy.<\/p><p class=\"wp-block-paragraph\">In this scenario, concurrent alerts from multiple services, including APIs, uploads, downloads, and logins, pointed to a far-reaching outage. That context guided the response and recovery efforts.<\/p><figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"2475\" height=\"1523\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/FIGURE-3_Mastering-IPM-The-Essential-Customer-Experience-Monitoring-Framework.png\" alt=\"\" class=\"wp-image-623976\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/FIGURE-3_Mastering-IPM-The-Essential-Customer-Experience-Monitoring-Framework.png 2475w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/FIGURE-3_Mastering-IPM-The-Essential-Customer-Experience-Monitoring-Framework-18x12.png 18w\" sizes=\"auto, (max-width: 2475px) 100vw, 2475px\"><\/figure><p class=\"wp-block-paragraph\">Historical monitoring screenshot.<\/p><h3 id=\"h-analyzing-the-potential-impact\" class=\"wp-block-heading\">Analyzing the potential impact<\/h3><p class=\"wp-block-paragraph\">Outages like this can disrupt operations and carry serious financial consequences. A study by <a href=\"https:\/\/www.logicmonitor.com\/asset\/forrester-opportunity-snapshot-increase-revenue-with-internet-performance-monitoring\">Forrester Consulting<\/a> found that eCommerce companies can lose significant sums each year because of Internet disruptions.<\/p><p class=\"wp-block-paragraph\">In that study, 88% of respondents estimated their companies lost over $100,000 due to disruptions in the month before the survey, which, annualized as a simple illustration, points to roughly $1.2 million. And 51% reported losing over $500,000 in the prior month alone.<\/p><p class=\"wp-block-paragraph\">A robust IPM strategy for CX matters for exactly these reasons.<\/p><p class=\"wp-block-paragraph\">The outage lasted just over three hours. Earlier detection widens the response window and can reduce the operational and business impact of an outage.<\/p><h2 id=\"h-bringing-internet-visibility-into-your-operations\" class=\"wp-block-heading\">Bringing internet visibility into your operations<\/h2><p class=\"wp-block-paragraph\">Internet Performance Monitoring enables you to determine whether users can reach and use a service. Infrastructure and cloud telemetry explain what&rsquo;s happening inside the environments that support it. Bringing those perspectives together helps teams move from detecting customer-impacting issues to identifying likely causes and coordinating a faster response.<\/p><p class=\"wp-block-paragraph\">LogicMonitor brings these perspectives together in a single <a href=\"https:\/\/www.logicmonitor.com\/blog\/autonomous-operations-without-blind-spots\">IT autonome<\/a> platform. <a href=\"https:\/\/www.logicmonitor.com\/fr\/internet-performance-monitoring\">LogicMonitor Synthetics and Internet Performance Monitoring<\/a> provide continuous outside-in visibility into Internet paths and digital experiences, while <a href=\"https:\/\/www.logicmonitor.com\/fr\/platform\">LM Envision<\/a> delivers <a href=\"https:\/\/www.logicmonitor.com\/fr\/infrastructure-monitoring\">infrastructure and cloud observability<\/a> by correlating those insights with application and log telemetry. Together with <a href=\"https:\/\/www.logicmonitor.com\/fr\/edwin-ai\">Edwin AI<\/a>, teams gain the context to investigate incidents faster and understand how Internet-facing issues affect the services behind them.<\/p><p class=\"wp-block-paragraph\">Building this kind of visibility is also an important step toward <a href=\"https:\/\/www.logicmonitor.com\/blog\/internet-performance-monitoring-safeguard-revenue\">safeguarding revenue<\/a>. By continuously validating critical user journeys and understanding how Internet conditions affect service delivery, teams are better equipped to meet service level agreements, reduce customer impact, and protect the business from the cost of outages.<\/p><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50\">\n      <span class=\"head-icon\"><svg class=\"\" width=\"50px\" height=\"50px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-light-calendar-check\"><\/use>\n    <\/svg><\/span>\n  \n  <div class=\"rtc-text-content__wrapper\">\n          <h4 class=\"rtc-text-content__headline fs-sm-text-display-xxs fs-md-text-display-xs fs-lg-text-display-sm font-medium text-core-blue-900\">\n        Give your team outside-in visibility into every critical user journey.      <\/h4>\n    \n          <div class=\"rtc-text-content__body fs-sm-text-md fs-md-text-lg fs-lg-text-lg text-core-blue-900\">\n        <p>LogicMonitor combines outside-in Internet Performance Monitoring with infrastructure observability, so you can detect customer-impacting issues sooner and resolve them faster.<\/p>\n      <\/div>\n    \n          \n      \n              <div>\n            <a href=\"https:\/\/www.logicmonitor.com\/catchpoint-demo\" class=\"btn btn-link\" target=\"_self\">\n        Demander une d\u00e9monstration          <span class=\"icon-end\"><svg class=\"\" width=\"20px\" height=\"20px\" style=\"fill: #060F4B\">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-arrow-right\"><\/use>\n    <\/svg><\/span>\n      <\/a>\n        <\/div>\n            <\/div>\n<\/div><h4 id=\"h-faqs\" class=\"wp-block-heading\">FAQ<\/h4><div class=\"accordion-block accordion-block--light\">\n      <div class=\"accordion-block__items\">\n              <div class=\"accordion-block__item active\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-what-is-the-difference-between-outside-in-and-inside-out-monitoring\">\n            What is the difference between outside-in and inside-out monitoring?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer active\">\n            <p>Inside-out telemetry reports what is happening within your own environment, such as server and application health. Outside-in monitoring runs from the user&rsquo;s vantage point across the Internet, capturing issues like DNS, CDN, and certificate failures that internal metrics miss. Used together, they give teams a complete view of the customer experience.<\/p>\n                      <\/div>\n        <\/div>\n              <div class=\"accordion-block__item\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-what-are-the-four-pillars-of-internet-resilience\">\n            What are the four pillars of Internet Resilience?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer\">\n            <p>The four pillars are availability, performance, reachability, and reliability. Availability confirms every function works, performance measures speed against user expectations, reachability confirms users can connect, and reliability keeps all three consistent across time and geography. Each pillar depends on the one beneath it.<\/p>\n                      <\/div>\n        <\/div>\n              <div class=\"accordion-block__item\">\n          \n          <h3 class=\"accordion-block__question\" id=\"h-how-does-ipm-reduce-mean-time-to-detect-mttd\">\n            How does IPM reduce Mean Time to Detect (MTTD)?            <span class=\"accordion-block__icon\">\n              <svg width=\"24\" height=\"24\" viewbox=\"0 0 24 24\" fill=\"none\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\">\n<path d=\"M6 9L12 15L18 9\" stroke=\"currentColor\" stroke-width=\"2\" stroke-linecap=\"round\" stroke-linejoin=\"round\"><\/path>\n<\/svg>\n            <\/span>\n          <\/h3>\n          <div class=\"accordion-block__answer\">\n            <p>IPM runs continuous outside-in tests across Internet layers and locations, so it surfaces failures before they are publicly reported. In the December 2023 file-sharing outage, monitoring caught critical API errors at 4:37 a.m. Pacific, ahead of public reports. Earlier detection widens the response window and limits business impact.<\/p>\n                      <\/div>\n        <\/div>\n          <\/div>\n  <\/div>","protected":false},"excerpt":{"rendered":"<p>See how Internet Performance Monitoring cuts detection time, the four pillars of Internet Resilience, and a real outage caught before it went public.<\/p>","protected":false},"author":16,"featured_media":623848,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"unicorn_plugin_options_block_body_class":"","footnotes":""},"categories":[5035],"tags":[7850,7823,7760,7863,7854,7862,7871,7868,7860,7883],"industry":[6790],"role":[6786],"lm_strategic_tags":[],"topic":[7842],"author_attribution":[7967],"lm_product":[],"class_list":["post-619157","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","industry-all","role-itops","topic-internet-performance-monitoring","author_attribution-denton-chikura"],"acf":{"page_language":"english","translated_pages":"","updated_date":null,"author_section_checkbox":true,"author_image":617027,"author_linkedin":"https:\/\/www.linkedin.com\/in\/denton-chikura-422186201\/","author_name":"Denton Chikura","author_job_title":"Technical Writer","author_dept":"","author_bio":"Denton Chikura is a technical writer and longtime observability advocate focused on helping site reliability engineers and engineering teams discover the tools and capabilities that strengthen internet resilience. He works at the intersection of monitoring, performance, and infrastructure to make complex systems more understandable and usable, bridging the gap between deep technical detail and real\u2011world operations. His goal is to help teams build faster, detect issues earlier, and recover smarter, ultimately making the internet a better, more reliable place for everyone.","reviewer_name":""},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.4 (Yoast SEO v28.4) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>IPM: A Customer Experience Monitoring Framework | LogicMonitor<\/title>\n<meta name=\"description\" content=\"How can you ensure a great customer experience? We cover the pillars of Internet Resilience, what your test setup should include, and a case study to see the framework in action.\" \/>\n<meta name=\"robots\" content=\"noindex, nofollow\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Mastering IPM: The Essential Customer Experience Monitoring Framework\" \/>\n<meta property=\"og:description\" content=\"How can you ensure a great customer experience? We cover the pillars of Internet Resilience, what your test setup should include, and a case study to see the framework in action.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.logicmonitor.com\/fr\/blog\/mastering-ipm-the-essential-customer-experience-monitoring-framework\" \/>\n<meta property=\"og:site_name\" content=\"LogicMonitor\" \/>\n<meta property=\"article:published_time\" content=\"2026-09-01T17:23:47+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-09-02T17:03:36+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/Blog_Mastering-IPM-The-Essential-Customer-Experience-Monitoring-Framework_Meta-1600x900px.png\" \/>\n\t<meta property=\"og:image:width\" content=\"2400\" \/>\n\t<meta property=\"og:image:height\" content=\"1350\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"destiny.setzer@logicmonitor.com\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/mastering-ipm-the-essential-customer-experience-monitoring-framework#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/mastering-ipm-the-essential-customer-experience-monitoring-framework\"},\"author\":{\"name\":\"destiny.setzer@logicmonitor.com\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\"},\"headline\":\"Mastering IPM: The Essential Customer Experience Monitoring Framework\",\"datePublished\":\"2026-09-01T17:23:47+00:00\",\"dateModified\":\"2026-09-02T17:03:36+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/mastering-ipm-the-essential-customer-experience-monitoring-framework\"},\"wordCount\":1443,\"image\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/mastering-ipm-the-essential-customer-experience-monitoring-framework#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Blog_Mastering-IPM-The-Essential-Customer-Experience-Monitoring-Framework_940x600_Featured-Image.png\",\"keywords\":[\"Catchpoint\",\"dns-monitoring\",\"Incident Response\",\"Network Path Analysis\",\"Outage Detection\",\"SLA Monitoring\",\"Traceroute\",\"Transaction Monitoring\",\"User Experience\",\"Web Performance\"],\"articleSection\":[\"Blog\"],\"inLanguage\":\"fr-FR\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/mastering-ipm-the-essential-customer-experience-monitoring-framework\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/mastering-ipm-the-essential-customer-experience-monitoring-framework\",\"name\":\"IPM: A Customer Experience Monitoring Framework | LogicMonitor\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/mastering-ipm-the-essential-customer-experience-monitoring-framework#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/mastering-ipm-the-essential-customer-experience-monitoring-framework#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Blog_Mastering-IPM-The-Essential-Customer-Experience-Monitoring-Framework_940x600_Featured-Image.png\",\"datePublished\":\"2026-09-01T17:23:47+00:00\",\"dateModified\":\"2026-09-02T17:03:36+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\"},\"description\":\"How can you ensure a great customer experience? We cover the pillars of Internet Resilience, what your test setup should include, and a case study to see the framework in action.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/mastering-ipm-the-essential-customer-experience-monitoring-framework#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/mastering-ipm-the-essential-customer-experience-monitoring-framework\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/mastering-ipm-the-essential-customer-experience-monitoring-framework#primaryimage\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Blog_Mastering-IPM-The-Essential-Customer-Experience-Monitoring-Framework_940x600_Featured-Image.png\",\"contentUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Blog_Mastering-IPM-The-Essential-Customer-Experience-Monitoring-Framework_940x600_Featured-Image.png\",\"width\":1410,\"height\":900},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/mastering-ipm-the-essential-customer-experience-monitoring-framework#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.logicmonitor.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Mastering IPM: The Essential Customer Experience Monitoring Framework\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#website\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/\",\"name\":\"LogicMonitor\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\",\"name\":\"destiny.setzer@logicmonitor.com\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"IPM: A Customer Experience Monitoring Framework | LogicMonitor","description":"How can you ensure a great customer experience? We cover the pillars of Internet Resilience, what your test setup should include, and a case study to see the framework in action.","robots":{"index":"noindex","follow":"nofollow"},"og_locale":"fr_FR","og_type":"article","og_title":"Mastering IPM: The Essential Customer Experience Monitoring Framework","og_description":"How can you ensure a great customer experience? We cover the pillars of Internet Resilience, what your test setup should include, and a case study to see the framework in action.","og_url":"https:\/\/www.logicmonitor.com\/fr\/blog\/mastering-ipm-the-essential-customer-experience-monitoring-framework","og_site_name":"LogicMonitor","article_published_time":"2026-09-01T17:23:47+00:00","article_modified_time":"2026-09-02T17:03:36+00:00","og_image":[{"width":2400,"height":1350,"url":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/Blog_Mastering-IPM-The-Essential-Customer-Experience-Monitoring-Framework_Meta-1600x900px.png","type":"image\/png"}],"author":"destiny.setzer@logicmonitor.com","twitter_card":"summary_large_image","twitter_misc":{"Written by":"","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/mastering-ipm-the-essential-customer-experience-monitoring-framework#article","isPartOf":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/mastering-ipm-the-essential-customer-experience-monitoring-framework"},"author":{"name":"destiny.setzer@logicmonitor.com","@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def"},"headline":"Mastering IPM: The Essential Customer Experience Monitoring Framework","datePublished":"2026-09-01T17:23:47+00:00","dateModified":"2026-09-02T17:03:36+00:00","mainEntityOfPage":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/mastering-ipm-the-essential-customer-experience-monitoring-framework"},"wordCount":1443,"image":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/mastering-ipm-the-essential-customer-experience-monitoring-framework#primaryimage"},"thumbnailUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/Blog_Mastering-IPM-The-Essential-Customer-Experience-Monitoring-Framework_940x600_Featured-Image.png","keywords":["Catchpoint","dns-monitoring","Incident Response","Network Path Analysis","Outage Detection","SLA Monitoring","Traceroute","Transaction Monitoring","User Experience","Web Performance"],"articleSection":["Blog"],"inLanguage":"fr-FR"},{"@type":"WebPage","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/mastering-ipm-the-essential-customer-experience-monitoring-framework","url":"https:\/\/www.logicmonitor.com\/fr\/blog\/mastering-ipm-the-essential-customer-experience-monitoring-framework","name":"IPM: A Customer Experience Monitoring Framework | LogicMonitor","isPartOf":{"@id":"https:\/\/www.logicmonitor.com\/fr\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/mastering-ipm-the-essential-customer-experience-monitoring-framework#primaryimage"},"image":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/mastering-ipm-the-essential-customer-experience-monitoring-framework#primaryimage"},"thumbnailUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/Blog_Mastering-IPM-The-Essential-Customer-Experience-Monitoring-Framework_940x600_Featured-Image.png","datePublished":"2026-09-01T17:23:47+00:00","dateModified":"2026-09-02T17:03:36+00:00","author":{"@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def"},"description":"How can you ensure a great customer experience? We cover the pillars of Internet Resilience, what your test setup should include, and a case study to see the framework in action.","breadcrumb":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/mastering-ipm-the-essential-customer-experience-monitoring-framework#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.logicmonitor.com\/fr\/blog\/mastering-ipm-the-essential-customer-experience-monitoring-framework"]}]},{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/mastering-ipm-the-essential-customer-experience-monitoring-framework#primaryimage","url":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/Blog_Mastering-IPM-The-Essential-Customer-Experience-Monitoring-Framework_940x600_Featured-Image.png","contentUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/07\/Blog_Mastering-IPM-The-Essential-Customer-Experience-Monitoring-Framework_940x600_Featured-Image.png","width":1410,"height":900},{"@type":"BreadcrumbList","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/mastering-ipm-the-essential-customer-experience-monitoring-framework#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.logicmonitor.com\/"},{"@type":"ListItem","position":2,"name":"Mastering IPM: The Essential Customer Experience Monitoring Framework"}]},{"@type":"WebSite","@id":"https:\/\/www.logicmonitor.com\/fr\/#website","url":"https:\/\/www.logicmonitor.com\/fr\/","name":"LogicMonitor","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.logicmonitor.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Person","@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def","name":"destiny.setzer@logicmonitor.com"}]}},"_links":{"self":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/619157","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/users\/16"}],"replies":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/comments?post=619157"}],"version-history":[{"count":4,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/619157\/revisions"}],"predecessor-version":[{"id":624058,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/619157\/revisions\/624058"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/media\/623848"}],"wp:attachment":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/media?parent=619157"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/categories?post=619157"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/tags?post=619157"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/industry?post=619157"},{"taxonomy":"role","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/role?post=619157"},{"taxonomy":"lm_strategic_tags","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/lm_strategic_tags?post=619157"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/topic?post=619157"},{"taxonomy":"author_attribution","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/author_attribution?post=619157"},{"taxonomy":"lm_product","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/lm_product?post=619157"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":624143,"date":"2026-09-01T11:28:10","date_gmt":"2026-09-01T16:28:10","guid":{"rendered":"https:\/\/www.logicmonitor.com\/?p=624143"},"modified":"2026-09-02T13:51:39","modified_gmt":"2026-09-02T18:51:39","slug":"internal-external-monitoring-incident-response","status":"publish","type":"post","link":"https:\/\/www.logicmonitor.com\/fr\/blog\/internal-external-monitoring-incident-response","title":{"rendered":"Au c\u0153ur d'une panne de paiement : comment la surveillance interne et externe a r\u00e9solu ce qu'aucune des deux ne pouvait r\u00e9v\u00e9ler seule"},"content":{"rendered":"<?xml encoding=\"UTF-8\"><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50\">\n      <span class=\"head-icon\"><svg class=\"\" width=\"50px\" height=\"50px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-light-book-open\"><\/use>\n    <\/svg><\/span>\n  \n  <div class=\"rtc-text-content__wrapper\">\n          <h4 class=\"rtc-text-content__headline fs-sm-text-display-xs fs-md-text-display-sm fs-lg-text-display-md font-medium text-core-blue-900\">\n        Le t\u00e9l\u00e9chargement rapide :      <\/h4>\n    \n          <div class=\"rtc-text-content__body fs-sm-text-md fs-md-text-lg fs-lg-text-lg text-core-blue-900 headline-is-quote\">\n        <p>The infrastructure looked healthy at first, but synthetic tests showed the public API slowing and failing from several regions. Putting both data sets on the same timeline revealed the backend problem behind it.<\/p>\n      <\/div>\n    \n                  <ul class=\"rtc-text-content__bullet-list\">\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p><span style=\"font-weight: 400\">Internal network telemetry from LogicMonitor Envision identified traffic drops and routing instability across backbone links, but could not confirm customer impact on its own.<\/span><\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p><span style=\"font-weight: 400\">Synthetic tests confirmed response time spikes of several seconds, with server errors across three global regions, before hard downtime occurred.<\/span><\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p><span style=\"font-weight: 400\">Aligning both signals showed that backend queuing, caused by internal network instability, was producing the elevated API latency customers were experiencing.<\/span><\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p><span style=\"font-weight: 400\">Monitor your most important customer-facing services from inside and outside the environment, so teams can quickly distinguish an infrastructure issue from a business-impacting customer problem.<\/span><\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                  <\/ul>\n      \n      \n            <\/div>\n<\/div><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">When a customer-facing service degrades, infrastructure teams need answers to two questions: what changed inside the environment, and what are customers experiencing outside it?<\/p><p class=\"wp-block-paragraph\">LogicMonitor&rsquo;s acquisition of Catchpoint <a href=\"https:\/\/www.logicmonitor.com\/fr\/logicmonitor-catchpoint\">brought these two perspectives together<\/a>, extending its infrastructure monitoring capabilities with Internet Performance Monitoring, including synthetic testing. The world&rsquo;s largest global payments platform relied on both LogicMonitor and Catchpoint to monitor its environment. When its internal dashboards did not initially show an obvious service failure, external testing told a different story. Its public authentication API was slowing down and intermittently returning errors across multiple regions as customer complaints rose.<\/p><p class=\"wp-block-paragraph\">For a payments business, issues like this can disrupt authentication and transaction journeys, increase support demand, and put customer trust at risk. By comparing internal network telemetry with external synthetic monitoring, the team identified the source of the degradation, confirmed that users were affected, and focused its response on the right problem. Here&rsquo;s how they did it.&nbsp;<\/p><h2 id=\"h-reading-the-internal-and-external-signals-together\" class=\"wp-block-heading\"><strong>Reading the Internal and External Signals Together<\/strong><\/h2><p class=\"wp-block-paragraph\"><a href=\"https:\/\/www.logicmonitor.com\/fr\/infrastructure-monitoring\">LogicMonitor Envision&rsquo;s<\/a> network data showed abrupt drops and rebounds across core and backbone links. The pattern looked like instability rather than normal congestion.<\/p><p class=\"wp-block-paragraph\">That data made it clear something was wrong with the network. On its own, it did not confirm whether the issue was reaching customers or whether it required escalation beyond routine network remediation.<\/p><figure class=\"wp-block-image size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"2079\" height=\"931\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-1-LogicMonitor-Envisions-backbone-utilization-view.png\" alt=\"\" class=\"wp-image-624151\" style=\"aspect-ratio:2.337078651685393;width:1505px;height:auto\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-1-LogicMonitor-Envisions-backbone-utilization-view.png 2079w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-1-LogicMonitor-Envisions-backbone-utilization-view-18x8.png 18w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-1-LogicMonitor-Envisions-backbone-utilization-view-766x343.png 766w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-1-LogicMonitor-Envisions-backbone-utilization-view-2048x917.png 2048w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-1-LogicMonitor-Envisions-backbone-utilization-view-1536x688.png 1536w\" sizes=\"auto, (max-width: 2079px) 100vw, 2079px\"><\/figure><p class=\"wp-block-paragraph\"><em>LogicMonitor Envision&rsquo;s backbone utilization view during the incident window. The shift from steady congestion to sudden drops and rebounds, visible across most links at once, is what flagged instability rather than a routine traffic pattern.<\/em><\/p><p class=\"wp-block-paragraph\"><a href=\"https:\/\/www.logicmonitor.com\/fr\/internet-performance-monitoring\">Supervision des performances Internet<\/a> data told a different part of the story. Tests against the public OAuth endpoint recorded server wait times and total response times several seconds above baseline, followed by intermittent server errors.<\/p><figure class=\"wp-block-image size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"2079\" height=\"1077\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-2-Internet-Performance-Monitoring-view.png\" alt=\"\" class=\"wp-image-624153\" style=\"aspect-ratio:1.9936102236421724;width:1496px;height:auto\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-2-Internet-Performance-Monitoring-view.png 2079w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-2-Internet-Performance-Monitoring-view-766x397.png 766w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-2-Internet-Performance-Monitoring-view-1536x796.png 1536w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-2-Internet-Performance-Monitoring-view-18x9.png 18w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-2-Internet-Performance-Monitoring-view-2048x1061.png 2048w\" sizes=\"auto, (max-width: 2079px) 100vw, 2079px\"><\/figure><p class=\"wp-block-paragraph\"><em>Internet Performance Monitoring view of the same window: response time and wait time climbing well above baseline, an Experience Score drop to 63, and downtime confirmed from three global test locations, independent evidence that real users were affected.<\/em><\/p><p class=\"wp-block-paragraph\">The external test also ruled things out. DNS, connect, and SSL timings stayed normal throughout the incident, which meant the delay wasn&rsquo;t a client-side or ISP problem. That single detail narrowed the investigation considerably. Whatever was happening, it was happening on the backend, not in the delivery path to the user.<\/p><p class=\"wp-block-paragraph\">The network data explained where to look. The OAuth tests established that the disruption had reached a public-facing service. Once the two incident windows were compared, the investigation narrowed quickly to the backend.<\/p><h2 id=\"h-a-practical-triage-workflow\" class=\"wp-block-heading\"><strong>A Practical Triage Workflow<\/strong><\/h2><p class=\"wp-block-paragraph\">The path from first alert to root cause followed a workflow that applies well beyond this one incident:<\/p><p class=\"wp-block-paragraph\"><strong>1. Establish the internal baseline.<\/strong> Confirm whether infrastructure and network telemetry show anomalous behavior, and characterize it: sudden shifts, gradual degradation, or isolated spikes.<\/p><p class=\"wp-block-paragraph\"><strong>2. Check external experience independently.<\/strong> Run or review synthetic tests against the customer-facing service to see whether real users are affected, and how severely.<\/p><p class=\"wp-block-paragraph\"><strong>3. Rule out the delivery path.<\/strong> Use DNS, connect, and SSL timing data to determine whether the problem originates outside the organization&rsquo;s infrastructure, such as with an ISP or CDN, or inside it.<\/p><p class=\"wp-block-paragraph\"><strong>4. Compare the timelines.<\/strong> Look for overlap between the infrastructure event and the change in API or transaction performance.<\/p><p class=\"wp-block-paragraph\"><strong>5. Use the combined evidence to narrow the investigation<\/strong> and decide how seriously to treat the incident.<\/p><figure class=\"wp-block-image size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"2079\" height=\"1181\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-3-Every-individual-test-result.png\" alt=\"\" class=\"wp-image-624154\" style=\"aspect-ratio:1.813953488372093;width:1477px;height:auto\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-3-Every-individual-test-result.png 2079w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-3-Every-individual-test-result-18x10.png 18w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-3-Every-individual-test-result-768x436.png 768w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-3-Every-individual-test-result-1536x873.png 1536w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-3-Every-individual-test-result-2048x1163.png 2048w\" sizes=\"auto, (max-width: 2079px) 100vw, 2079px\"><\/figure><p class=\"wp-block-paragraph\"><em>Every individual test result, plotted by timestamp across the test window. The cluster of failed tests (red) inside the highlighted window is what separates a genuine incident from ordinary test-to-test noise.<\/em><\/p><p class=\"wp-block-paragraph\">For the payments platform, step five was the turning point. Aligning the network instability window against the API latency window, roughly 90 minutes of overlapping activity, showed that backend queuing, caused by internal network instability, was producing delayed service-to-service calls, which reached customers as elevated latency and intermittent server errors.<\/p><figure class=\"wp-block-image size-full is-resized\"><img loading=\"lazy\" decoding=\"async\" width=\"2079\" height=\"1121\" src=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-4-One-representative-test-run.png\" alt=\"\" class=\"wp-image-624156\" style=\"aspect-ratio:1.908256880733945;width:1473px;height:auto\" srcset=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-4-One-representative-test-run.png 2079w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-4-One-representative-test-run-768x414.png 768w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-4-One-representative-test-run-1536x828.png 1536w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-4-One-representative-test-run-18x10.png 18w, https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Image-4-One-representative-test-run-2048x1104.png 2048w\" sizes=\"auto, (max-width: 2079px) 100vw, 2079px\"><\/figure><p class=\"wp-block-paragraph\"><em>One representative test run from inside the incident window. The wait-time breakdown is what ruled out DNS, connect, and SSL as the cause, and pointed the investigation straight at the backend.<\/em><\/p><p class=\"wp-block-paragraph\">One representative test endpoint was enough to confirm platform-level degradation. The team could understand the incident without instrumenting every API. A representative endpoint, paired with the network telemetry, was enough to show that the infrastructure instability and customer-facing degradation were occurring at the same time.<\/p><h2 id=\"h-how-the-monitoring-pieces-fit-together\" class=\"wp-block-heading\"><strong>How the Monitoring Pieces Fit Together<\/strong><\/h2><p class=\"wp-block-paragraph\"><a href=\"https:\/\/www.logicmonitor.com\/fr\/infrastructure-monitoring\">Supervision des infrastructures<\/a> gave the team the network context behind the incident. <a href=\"https:\/\/www.logicmonitor.com\/fr\/internet-performance-monitoring\">Supervision des performances Internet<\/a> showed what was happening at the public OAuth endpoint from outside the company&rsquo;s environment, including the response-time increase, server errors, and geographic spread. Taken together, the two capabilities connected an unstable network condition to a degraded customer-facing service.<\/p><p class=\"wp-block-paragraph\">Today, these capabilities are becoming <a href=\"https:\/\/www.logicmonitor.com\/blog\/internet-performance-monitoring-innovation\">easier to use together<\/a>. Customers can now move between the two platforms with a more seamless authentication experience. Synthetics and Internet Performance Monitoring alert data can be routed to Edwin AI through REST APIs and webhooks. Further integration work is under way, with the aim of making this kind of correlation easier to do in one place.<\/p><h2 id=\"h-apply-the-same-approach-to-your-own-services\" class=\"wp-block-heading\"><strong>Apply the Same Approach to Your Own Services<\/strong><\/h2><p class=\"wp-block-paragraph\">Internal telemetry can tell you that the environment has changed. Internet Performance Monitoring can show whether that change is degrading the experience customers receive. By correlating both views on one incident timeline, teams can eliminate false leads, prioritize the right escalation, and reduce the time it takes to move from alert to action.<\/p><p class=\"wp-block-paragraph\">Start with one API or transaction that customers rely on. If it slows down or fails, can your team see the infrastructure event behind it and the effect on the service at the same time?<\/p><p class=\"wp-block-paragraph\">If not, your investigation will begin with only part of the picture.<\/p><p class=\"wp-block-paragraph\"><\/p><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50\">\n      <span class=\"head-icon\"><svg class=\"\" width=\"50px\" height=\"50px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-light-calendar-check\"><\/use>\n    <\/svg><\/span>\n  \n  <div class=\"rtc-text-content__wrapper\">\n          <h4 class=\"rtc-text-content__headline fs-sm-text-display-xxs fs-md-text-display-xs fs-lg-text-display-sm font-medium text-core-blue-900\">\n        See the full picture, inside and out      <\/h4>\n    \n          <div class=\"rtc-text-content__body fs-sm-text-md fs-md-text-lg fs-lg-text-lg text-core-blue-900\">\n        <p><span style=\"font-weight: 400\">Connect infrastructure and digital experience monitoring to detect issues sooner, troubleshoot faster, and reduce their impact on customers.<\/span><\/p>\n      <\/div>\n    \n          \n      \n              <div>\n            <a href=\"https:\/\/www.logicmonitor.com\/catchpoint-demo\" class=\"btn btn-link\" target=\"_self\">\n        Demandez une d\u00e9mo          <span class=\"icon-end\"><svg class=\"\" width=\"20px\" height=\"20px\" style=\"fill: #060F4B\">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-arrow-right\"><\/use>\n    <\/svg><\/span>\n      <\/a>\n        <\/div>\n            <\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Lorsque la surveillance interne semble normale et que les clients signalent des pannes, la r\u00e9ponse se trouve dans un second ensemble de signaux. D\u00e9couvrez comment une plateforme de paiement a utilis\u00e9 conjointement l'infrastructure et la surveillance des performances Internet pour trouver ce qu'aucune des deux ne pouvait montrer seule.<\/p>","protected":false},"author":16,"featured_media":624161,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"unicorn_plugin_options_block_body_class":"","footnotes":""},"categories":[5035],"tags":[5348,7888,7850,7823,7760,7752,7854,7018,7868,7860],"industry":[7513],"role":[6786],"lm_strategic_tags":[],"topic":[7842],"author_attribution":[7967],"lm_product":[],"class_list":["post-624143","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","industry-financial-services","role-itops","topic-internet-performance-monitoring","author_attribution-denton-chikura"],"acf":{"page_language":"english","translated_pages":"","updated_date":null,"author_section_checkbox":true,"author_image":617027,"author_linkedin":"https:\/\/www.linkedin.com\/in\/denton-chikura-422186201\/","author_name":"Denton Chikura","author_job_title":"Technical Writer","author_dept":"","author_bio":"Denton Chikura is a technical writer and longtime observability advocate focused on helping site reliability engineers and engineering teams discover the tools and capabilities that strengthen internet resilience. He works at the intersection of monitoring, performance, and infrastructure to make complex systems more understandable and usable, bridging the gap between deep technical detail and real\u2011world operations. His goal is to help teams build faster, detect issues earlier, and recover smarter, ultimately making the internet a better, more reliable place for everyone.","reviewer_name":""},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.4 (Yoast SEO v28.4) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Inside a Payments Outage: How Internal and External Monitoring Solved What Neither Could Alone | LogicMonitor<\/title>\n<meta name=\"description\" content=\"A payments platform&#039;s infrastructure dashboards showed green. Their API was actively degrading. See how LogicMonitor Envision and Internet Performance Monitoring connected the internal and external signals to identify root cause.\" \/>\n<meta name=\"robots\" content=\"noindex, nofollow\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Inside a Payments Outage: How Internal and External Monitoring Solved What Neither Could Reveal Alone\" \/>\n<meta property=\"og:description\" content=\"A payments platform&#039;s infrastructure dashboards showed green. Their API was actively degrading. See how LogicMonitor Envision and Internet Performance Monitoring connected the internal and external signals to identify root cause.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.logicmonitor.com\/fr\/blog\/internal-external-monitoring-incident-response\" \/>\n<meta property=\"og:site_name\" content=\"LogicMonitor\" \/>\n<meta property=\"article:published_time\" content=\"2026-09-01T16:28:10+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-09-02T18:51:39+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Blog_Inside-a-Payments-Outage_940x600_Featured-Image.png\" \/>\n\t<meta property=\"og:image:width\" content=\"940\" \/>\n\t<meta property=\"og:image:height\" content=\"600\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"destiny.setzer@logicmonitor.com\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/internal-external-monitoring-incident-response#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/internal-external-monitoring-incident-response\"},\"author\":{\"name\":\"destiny.setzer@logicmonitor.com\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\"},\"headline\":\"Inside a Payments Outage: How Internal and External Monitoring Solved What Neither Could Reveal Alone\",\"datePublished\":\"2026-09-01T16:28:10+00:00\",\"dateModified\":\"2026-09-02T18:51:39+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/internal-external-monitoring-incident-response\"},\"wordCount\":949,\"image\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/internal-external-monitoring-incident-response#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/Blog_Inside-a-Payments-Outage_940x600_Featured-Image.png\",\"keywords\":[\"api monitoring\",\"Backbone Monitoring\",\"Catchpoint\",\"dns-monitoring\",\"Incident Response\",\"LM Envision\",\"Outage Detection\",\"synthetics\",\"Transaction Monitoring\",\"User Experience\"],\"articleSection\":[\"Blog\"],\"inLanguage\":\"fr-FR\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/internal-external-monitoring-incident-response\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/internal-external-monitoring-incident-response\",\"name\":\"Inside a Payments Outage: How Internal and External Monitoring Solved What Neither Could Alone | LogicMonitor\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/internal-external-monitoring-incident-response#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/internal-external-monitoring-incident-response#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/Blog_Inside-a-Payments-Outage_940x600_Featured-Image.png\",\"datePublished\":\"2026-09-01T16:28:10+00:00\",\"dateModified\":\"2026-09-02T18:51:39+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\"},\"description\":\"A payments platform's infrastructure dashboards showed green. Their API was actively degrading. See how LogicMonitor Envision and Internet Performance Monitoring connected the internal and external signals to identify root cause.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/internal-external-monitoring-incident-response#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/internal-external-monitoring-incident-response\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/internal-external-monitoring-incident-response#primaryimage\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/Blog_Inside-a-Payments-Outage_940x600_Featured-Image.png\",\"contentUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/Blog_Inside-a-Payments-Outage_940x600_Featured-Image.png\",\"width\":940,\"height\":600},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/internal-external-monitoring-incident-response#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.logicmonitor.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Inside a Payments Outage: How Internal and External Monitoring Solved What Neither Could Reveal Alone\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#website\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/\",\"name\":\"LogicMonitor\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/bfbb8cb00c9595482098c66aa78b9def\",\"name\":\"destiny.setzer@logicmonitor.com\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Inside a Payments Outage: How Internal and External Monitoring Solved What Neither Could Alone | LogicMonitor","description":"A payments platform's infrastructure dashboards showed green. Their API was actively degrading. See how LogicMonitor Envision and Internet Performance Monitoring connected the internal and external signals to identify root cause.","robots":{"index":"noindex","follow":"nofollow"},"og_locale":"fr_FR","og_type":"article","og_title":"Inside a Payments Outage: How Internal and External Monitoring Solved What Neither Could Reveal Alone","og_description":"A payments platform's infrastructure dashboards showed green. Their API was actively degrading. See how LogicMonitor Envision and Internet Performance Monitoring connected the internal and external signals to identify root cause.","og_url":"https:\/\/www.logicmonitor.com\/fr\/blog\/internal-external-monitoring-incident-response","og_site_name":"LogicMonitor","article_published_time":"2026-09-01T16:28:10+00:00","article_modified_time":"2026-09-02T18:51:39+00:00","og_image":[{"width":940,"height":600,"url":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Blog_Inside-a-Payments-Outage_940x600_Featured-Image.png","type":"image\/png"}],"author":"destiny.setzer@logicmonitor.com","twitter_card":"summary_large_image","twitter_misc":{"Written by":"","Est. reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/internal-external-monitoring-incident-response#article","isPartOf":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/internal-external-monitoring-incident-response"},"author":{"name":"destiny.setzer@logicmonitor.com","@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def"},"headline":"Inside a Payments Outage: How Internal and External Monitoring Solved What Neither Could Reveal Alone","datePublished":"2026-09-01T16:28:10+00:00","dateModified":"2026-09-02T18:51:39+00:00","mainEntityOfPage":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/internal-external-monitoring-incident-response"},"wordCount":949,"image":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/internal-external-monitoring-incident-response#primaryimage"},"thumbnailUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Blog_Inside-a-Payments-Outage_940x600_Featured-Image.png","keywords":["api monitoring","Backbone Monitoring","Catchpoint","dns-monitoring","Incident Response","LM Envision","Outage Detection","synthetics","Transaction Monitoring","User Experience"],"articleSection":["Blog"],"inLanguage":"fr-FR"},{"@type":"WebPage","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/internal-external-monitoring-incident-response","url":"https:\/\/www.logicmonitor.com\/fr\/blog\/internal-external-monitoring-incident-response","name":"Inside a Payments Outage: How Internal and External Monitoring Solved What Neither Could Alone | LogicMonitor","isPartOf":{"@id":"https:\/\/www.logicmonitor.com\/fr\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/internal-external-monitoring-incident-response#primaryimage"},"image":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/internal-external-monitoring-incident-response#primaryimage"},"thumbnailUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Blog_Inside-a-Payments-Outage_940x600_Featured-Image.png","datePublished":"2026-09-01T16:28:10+00:00","dateModified":"2026-09-02T18:51:39+00:00","author":{"@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def"},"description":"A payments platform's infrastructure dashboards showed green. Their API was actively degrading. See how LogicMonitor Envision and Internet Performance Monitoring connected the internal and external signals to identify root cause.","breadcrumb":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/internal-external-monitoring-incident-response#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.logicmonitor.com\/fr\/blog\/internal-external-monitoring-incident-response"]}]},{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/internal-external-monitoring-incident-response#primaryimage","url":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Blog_Inside-a-Payments-Outage_940x600_Featured-Image.png","contentUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2026\/08\/Blog_Inside-a-Payments-Outage_940x600_Featured-Image.png","width":940,"height":600},{"@type":"BreadcrumbList","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/internal-external-monitoring-incident-response#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.logicmonitor.com\/"},{"@type":"ListItem","position":2,"name":"Inside a Payments Outage: How Internal and External Monitoring Solved What Neither Could Reveal Alone"}]},{"@type":"WebSite","@id":"https:\/\/www.logicmonitor.com\/fr\/#website","url":"https:\/\/www.logicmonitor.com\/fr\/","name":"LogicMonitor","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.logicmonitor.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Person","@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/bfbb8cb00c9595482098c66aa78b9def","name":"destiny.setzer@logicmonitor.com"}]}},"_links":{"self":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/624143","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/users\/16"}],"replies":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/comments?post=624143"}],"version-history":[{"count":5,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/624143\/revisions"}],"predecessor-version":[{"id":624164,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/624143\/revisions\/624164"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/media\/624161"}],"wp:attachment":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/media?parent=624143"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/categories?post=624143"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/tags?post=624143"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/industry?post=624143"},{"taxonomy":"role","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/role?post=624143"},{"taxonomy":"lm_strategic_tags","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/lm_strategic_tags?post=624143"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/topic?post=624143"},{"taxonomy":"author_attribution","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/author_attribution?post=624143"},{"taxonomy":"lm_product","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/lm_product?post=624143"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}},{"id":609790,"date":"2026-09-01T10:27:43","date_gmt":"2026-09-01T15:27:43","guid":{"rendered":"https:\/\/www.logicmonitor.com\/?p=609790"},"modified":"2026-09-03T17:13:35","modified_gmt":"2026-09-03T22:13:35","slug":"solarwinds-alternative-evaluation-guide","status":"publish","type":"post","link":"https:\/\/www.logicmonitor.com\/fr\/blog\/solarwinds-alternative-evaluation-guide","title":{"rendered":"Comment \u00e9valuer une alternative \u00e0 SolarWinds"},"content":{"rendered":"<?xml encoding=\"UTF-8\"><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50 rtc-text-content--no-top-pad\">\n      <span class=\"head-icon\"><svg class=\"\" width=\"50px\" height=\"50px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-light-book-open\"><\/use>\n    <\/svg><\/span>\n  \n  <div class=\"rtc-text-content__wrapper\">\n          <h4 class=\"rtc-text-content__headline fs-sm-text-display-xs fs-md-text-display-sm fs-lg-text-display-md font-medium text-core-blue-900\">\n        Le t\u00e9l\u00e9chargement rapide :      <\/h4>\n    \n          <div class=\"rtc-text-content__body fs-sm-text-md fs-md-text-lg fs-lg-text-lg text-core-blue-900 headline-is-quote\">\n        <p>Choisir une alternative \u00e0 SolarWinds est une occasion de r\u00e9duire la complexit\u00e9 op\u00e9rationnelle de la surveillance h\u00e9rit\u00e9e bas\u00e9e sur des modules.<\/p>\n      <\/div>\n    \n                  <ul class=\"rtc-text-content__bullet-list\">\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>\u00c9valuez les plateformes en fonction de leur capacit\u00e9 \u00e0 connecter la surveillance, les informations et l'automatisation s\u00e9curis\u00e9e dans des environnements hybrides.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>Prioriser un pipeline de t\u00e9l\u00e9m\u00e9trie unique qui corr\u00e8le nativement les m\u00e9triques, les journaux et les traces pour acc\u00e9l\u00e9rer l'analyse des causes profondes<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>Consid\u00e9rez le co\u00fbt total de possession \u00e0 long terme, y compris les frais g\u00e9n\u00e9raux de maintenance et le fardeau de \u201c soin et entretien \u201d de la plateforme.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                      <li class=\"bullet-list-item\">\n              <span class=\"bullet-list-item__icon\">\n                <svg class=\"\" width=\"24px\" height=\"24px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-check-mark\"><\/use>\n    <\/svg>              <\/span>\n              <div class=\"bullet-list-item__content\">\n                                  <span class=\"bullet-list-item__content-heading fs-sm-text-sm fs-md-text-md fs-lg-text-md text-midnight-blue-500\">\n                    <p>Recherchez une architecture native SaaS qui offre une visibilit\u00e9 sur l'ensemble du parcours num\u00e9rique, y compris les d\u00e9pendances Internet, afin d'\u00e9liminer les angles morts.<\/p>\n                  <\/span>\n                              <\/div>\n            <\/li>\n                  <\/ul>\n      \n      \n            <\/div>\n<\/div><p class=\"wp-block-paragraph\"><\/p><p class=\"wp-block-paragraph\">Si vous \u00e9valuez une alternative \u00e0 SolarWinds, la question n'est pas seulement de savoir quelle plateforme peut remplacer les fonctionnalit\u00e9s dont vous disposez d\u00e9j\u00e0. Il s'agit de savoir si la prochaine plateforme peut r\u00e9duire la complexit\u00e9 op\u00e9rationnelle qui vous a amen\u00e9 \u00e0 envisager des alternatives en premier lieu.<\/p><p class=\"wp-block-paragraph\">Pour de nombreuses \u00e9quipes, cette complexit\u00e9 s'est accumul\u00e9e au fil des ans. Les plateformes de surveillance h\u00e9rit\u00e9es et modulaires peuvent cr\u00e9er une visibilit\u00e9 fragment\u00e9e, un volume d'alertes et des angles morts \u00e0 travers le cloud, les applications et les d\u00e9pendances Internet que les \u00e9quipes ne contr\u00f4lent pas enti\u00e8rement, un d\u00e9fi structurel identifi\u00e9 dans le <a href=\"https:\/\/www.gartner.com\/en\/documents\/5663737\">2025 Gartner\u00ae Magic Quadrant\u2122 pour les plateformes d'observabilit\u00e9<\/a>.<\/p><p class=\"wp-block-paragraph\">Ces lacunes fa\u00e7onnent la rapidit\u00e9 avec laquelle les \u00e9quipes peuvent enqu\u00eater sur les incidents, le temps qu'elles consacrent au changement de contexte et la surcharge que la plateforme elle-m\u00eame ajoute aux op\u00e9rations quotidiennes.&nbsp;<\/p><p class=\"wp-block-paragraph\">L'\u00e9valuation d'une alternative \u00e0 SolarWinds doit aller au-del\u00e0 de la simple comparaison des fonctionnalit\u00e9s pour d\u00e9terminer si une plateforme peut connecter la surveillance, les analyses et l'automatisation s\u00e9curis\u00e9e dans des environnements hybrides sans cr\u00e9er de travail suppl\u00e9mentaire pour les \u00e9quipes qui l'utilisent.<\/p><h2 id=\"h-why-feature-checklists-dont-tell-you-enough\" class=\"wp-block-heading\">Pourquoi les listes de fonctionnalit\u00e9s ne vous disent pas assez<\/h2><p class=\"wp-block-paragraph\">De nombreuses plateformes peuvent correspondre \u00e0 des capacit\u00e9s isol\u00e9es, mais une meilleure \u00e9valuation commence par la mani\u00e8re dont la plateforme fonctionne lors d'incidents r\u00e9els :<\/p><ul class=\"wp-block-list\">\n<li>Comment les donn\u00e9es sont collect\u00e9es<\/li>\n\n\n\n<li>Comment les signaux sont corr\u00e9l\u00e9s<\/li>\n\n\n\n<li>La rapidit\u00e9 avec laquelle les \u00e9quipes peuvent enqu\u00eater sur les probl\u00e8mes<\/li>\n\n\n\n<li>Combien d'efforts manuels la plateforme supprime ou ajoute<\/li>\n<\/ul><p class=\"wp-block-paragraph\">La s\u00e9paration des produits de surveillance r\u00e9seau, de surveillance de serveurs, d'analyse de flux et de gestion de configuration oblige les \u00e9quipes \u00e0 changer constamment de contexte, augmentant l'effort manuel et retardant l'analyse de la cause premi\u00e8re lorsque chaque minute compte.<\/p><p class=\"wp-block-paragraph\"><a href=\"https:\/\/www.forrester.com\/report\/the-forrester-wave-observability-platforms-q4-2024\/RES179920\">\u00c9valuation de la plateforme d'observabilit\u00e9 de Forrester<\/a> refl\u00e8te cette \u00e9volution. Les acheteurs recherchent de plus en plus des plateformes qui combinent les m\u00e9triques, les logs, la topologie et les donn\u00e9es d'exp\u00e9rience utilisateur, au lieu de s'appuyer sur des outils d\u00e9connect\u00e9s. En pratique, l'\u00e9valuation devrait se concentrer sur la r\u00e9duction du travail requis pour connecter ces \u00e9l\u00e9ments en cas d'incident.<\/p><h2 id=\"h-start-with-architecture-when-evaluating-a-solarwinds-alternative\" class=\"wp-block-heading\">Commencez par l'architecture lors de l'\u00e9valuation d'une alternative \u00e0 SolarWinds<\/h2><p class=\"wp-block-paragraph\">L'architecture derri\u00e8re une plateforme fa\u00e7onne la fa\u00e7on dont les op\u00e9rations se d\u00e9roulent au quotidien. <a href=\"https:\/\/www.techtarget.com\/searchitoperations\/tip\/Observability-vs-monitoring-Key-differences-explained\">TechTarget note<\/a> que les tableaux de bord pr\u00e9d\u00e9finis et les seuils sont moins efficaces dans les syst\u00e8mes distribu\u00e9s dynamiques o\u00f9 les modes de d\u00e9faillance sont impr\u00e9visibles. Dans ces environnements, la v\u00e9ritable question est de savoir si les \u00e9quipes peuvent rassembler rapidement les m\u00e9triques, les \u00e9v\u00e9nements, les logs, la topologie et les donn\u00e9es de configuration pour comprendre ce qui se passe r\u00e9ellement.<\/p><p class=\"wp-block-paragraph\">Une plateforme con\u00e7ue pour centraliser les donn\u00e9es permet aux \u00e9quipes de disposer d'un espace unique o\u00f9 les signaux peuvent \u00eatre collect\u00e9s, mis en relation et interpr\u00e9t\u00e9s ensemble. Une plateforme assembl\u00e9e \u00e0 partir de plusieurs produits peut toujours offrir une large couverture, mais cette couverture peut s'accompagner de plus de transferts, de plus de maintenance et de plus de corr\u00e9lations manuelles pendant les incidents. Qu'une plateforme ait \u00e9t\u00e9 con\u00e7ue pour connecter nativement les signaux ou qu'elle d\u00e9pende de plusieurs produits travaillant ensemble, cela affecte tout, de la vitesse d'investigation \u00e0 la charge op\u00e9rationnelle.<\/p><h2 id=\"h-what-a-single-telemetry-pipeline-changes\" class=\"wp-block-heading\">Ce qu'un pipeline de t\u00e9l\u00e9m\u00e9trie unique change<\/h2><p class=\"wp-block-paragraph\">Un flux de donn\u00e9es unique modifie la r\u00e9ponse aux incidents car les \u00e9quipes n'ont pas \u00e0 assembler le tableau manuellement. Lorsque la t\u00e9l\u00e9m\u00e9trie circule \u00e0 travers un seul syst\u00e8me, les ing\u00e9nieurs peuvent corr\u00e9ler les signaux sans les extraire d'outils distincts, ce qui permet une analyse plus rapide des causes profondes. Au lieu de commencer par des alertes dispers\u00e9es et de construire le contexte \u00e0 la main, les \u00e9quipes commencent par une vue connect\u00e9e de ce qui a chang\u00e9, de ce qui est affect\u00e9 et o\u00f9 elles devraient enqu\u00eater en premier.<\/p><p class=\"wp-block-paragraph\">Cette diff\u00e9rence est essentielle dans les environnements hybrides o\u00f9 la fronti\u00e8re entre l'infrastructure, l'application et la d\u00e9pendance \u00e0 Internet est rarement nette. Une plateforme qui connecte les donn\u00e9es \u00e0 la source donne aux \u00e9quipes une meilleure chance de comprendre les probl\u00e8mes avant qu'ils ne d\u00e9g\u00e9n\u00e8rent en une longue enqu\u00eate ou en une crise plus importante.<\/p><h2 id=\"h-born-saas-vs-migrated-saas-what-buyers-should-ask\" class=\"wp-block-heading\">SaaS d\u00e9velopp\u00e9 \u00e0 l'origine ou SaaS migr\u00e9 : Ce que les acheteurs devraient demander<\/h2><p class=\"wp-block-paragraph\">Toutes les plateformes d'observabilit\u00e9 SaaS n'ont pas \u00e9t\u00e9 con\u00e7ues comme telles. Il est essentiel de se demander si une plateforme a \u00e9t\u00e9 con\u00e7ue dans le cloud d\u00e8s le d\u00e9part ou si un produit sur site a \u00e9t\u00e9 migr\u00e9 dans le cloud et, dans ce dernier cas, si toutes les fonctionnalit\u00e9s sont pr\u00e9sentes. Cette distinction affecte la rapidit\u00e9 avec laquelle la plateforme peut \u00e9voluer et la charge de travail qu'elle impose \u00e0 l'\u00e9quipe.&nbsp;<\/p><p class=\"wp-block-paragraph\">LogicMonitor fonctionne comme une plateforme SaaS depuis pr\u00e8s de deux d\u00e9cennies, recevant des mises \u00e0 jour r\u00e9guli\u00e8res sans base de code sur site \u00e0 maintenir ou \u00e0 migrer. Bien que les acheteurs doivent \u00e9galement peser la profondeur de la couverture, l'effort de migration et la gouvernance, d\u00e9terminer si une plateforme a \u00e9t\u00e9 con\u00e7ue d\u00e8s le d\u00e9part pour une livraison moderne r\u00e9v\u00e8le son aptitude aux environnements en \u00e9volution rapide.<\/p><h2 id=\"h-a-solarwinds-alternative-should-cover-the-full-digital-path\" class=\"wp-block-heading\">Une alternative \u00e0 SolarWinds devrait couvrir le parcours num\u00e9rique complet<\/h2><p class=\"wp-block-paragraph\">L\u2019une des faiblesses les plus flagrantes des solutions de surveillance traditionnelles appara\u00eet lorsqu\u2019un incident semble \u00eatre un probl\u00e8me d\u2019infrastructure, mais provient d\u2019ailleurs, comme une d\u00e9gradation du CDN, une panne d\u2019un fournisseur DNS ou une API tierce inaccessible. Les outils de surveillance ax\u00e9s sur l\u2019infrastructure peuvent afficher des sympt\u00f4mes sans identifier ces d\u00e9pendances externes sur lesquelles les \u00e9quipes informatiques s\u2019appuient pour une prestation de services transparente.<\/p><p class=\"wp-block-paragraph\">Sans visibilit\u00e9 sur le cheminement Internet et l'exp\u00e9rience num\u00e9rique, les \u00e9quipes passent des cycles d'escalade \u00e0 chercher dans la mauvaise couche, laissant la question \u201cest-ce nous ou eux ?\u201d sans r\u00e9ponse. Une alternative plus solide \u00e0 SolarWinds offre une visibilit\u00e9 sur l'infrastructure, les applications et les d\u00e9pendances Internet afin que les \u00e9quipes puissent voir la r\u00e9alit\u00e9 au lieu de la reconstituer apr\u00e8s coup.<\/p><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50\">\n  \n  <div class=\"rtc-text-content__wrapper\">\n    \n          <div class=\"rtc-text-content__body fs-sm-text-md fs-md-text-lg fs-lg-text-lg text-core-blue-900\">\n        <p>Explorez comment LogicMonitor et Catchpoint r\u00e9duisent les angles morts sur les d\u00e9pendances Internet, applicatives et infrastrukturales.<\/p>\n      <\/div>\n    \n          \n      \n              <div>\n            <a href=\"https:\/\/unicorn1.wpengine.com\/logicmonitor-catchpoint\" class=\"btn btn-link\" target=\"_self\">\n        Allons-y          <span class=\"icon-end\"><svg class=\"\" width=\"20px\" height=\"20px\" style=\"fill: #060F4B\">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-arrow-right\"><\/use>\n    <\/svg><\/span>\n      <\/a>\n        <\/div>\n            <\/div>\n<\/div><h2 id=\"h-evaluate-ai-by-what-it-helps-teams-do\" class=\"wp-block-heading\">\u00c9valuez l'IA par ce qu'elle aide les \u00e9quipes \u00e0 faire<\/h2><p class=\"wp-block-paragraph\">L'IA devrait \u00eatre \u00e9valu\u00e9e sur sa capacit\u00e9 \u00e0 am\u00e9liorer les op\u00e9rations, et non sur la place qu'elle occupe dans le marketing. Les acheteurs devraient consid\u00e9rer si elle contribue \u00e0 r\u00e9duire le bruit des alertes, \u00e0 am\u00e9liorer la priorisation, \u00e0 soutenir l'analyse des causes profondes et \u00e0 faciliter les investigations dans des environnements complexes.<\/p><p class=\"wp-block-paragraph\">Une approche plus forte de l'IA fait plus que r\u00e9sumer les alertes. Elle aide les \u00e9quipes \u00e0 connecter les signaux dans tout l'environnement, \u00e0 pr\u00e9server le contexte lorsque les incidents transitent entre les syst\u00e8mes et les \u00e9quipes, et \u00e0 r\u00e9duire le travail manuel qui ralentit les investigations. C'est important car les \u00e9quipes d'exploitation r\u00e9solvent rarement les probl\u00e8mes sur un seul \u00e9cran. Elles se d\u00e9placent entre les alertes, les journaux, les tickets, les fils de discussion et le contexte du service pour comprendre ce qui a chang\u00e9, ce qui est touch\u00e9 et o\u00f9 agir ensuite. <a href=\"https:\/\/unicorn1.wpengine.com\/edwin-ai\">Edwin AI de LogicMonitor<\/a> prend en charge ce r\u00f4le op\u00e9rationnel plus large, avec un accent sur l'investigation sensible au contexte, l'analyse inform\u00e9e par la topologie, la RCA \u00e9tay\u00e9e par des preuves, et la continuit\u00e9 entre les flux de travail plut\u00f4t que des fonctionnalit\u00e9s d'IA autonomes.<\/p><p class=\"wp-block-paragraph\">Pour les acheteurs qui \u00e9valuent les alternatives, la question la plus utile n'est pas simplement de savoir si une plateforme inclut l'IA, mais si cette IA aide les \u00e9quipes \u00e0 enqu\u00eater et \u00e0 r\u00e9pondre avec moins de friction. Edwin AI pointe vers ce mod\u00e8le plus op\u00e9rationnel en aidant \u00e0 connecter les signaux, \u00e0 transporter le contexte \u00e0 travers les flux de travail et \u00e0 soutenir un processus d'enqu\u00eate plus connect\u00e9. Le message cl\u00e9 pour les acheteurs est d'\u00e9valuer si l'IA est int\u00e9gr\u00e9e l\u00e0 o\u00f9 le travail op\u00e9rationnel se d\u00e9roule r\u00e9ellement et si elle aide les \u00e9quipes \u00e0 passer plus rapidement de la d\u00e9tection \u00e0 la compr\u00e9hension.<\/p><p class=\"wp-block-paragraph\">L'IA op\u00e9rationnelle n\u00e9cessite \u00e9galement des contr\u00f4les. Les acheteurs devraient \u00e9valuer les approbations, les contr\u00f4les d'acc\u00e8s bas\u00e9s sur les r\u00f4les, l'auditabilit\u00e9 et les playbooks standardis\u00e9s. Les \u00e9quipes d'entreprise ont besoin d'une automatisation qui fonctionne dans les limites requises par les environnements de production, et pas seulement d'une IA qui produit des r\u00e9sultats sans gouvernance.<\/p><h2 id=\"h-what-a-realistic-migration-from-solarwinds-looks-like\" class=\"wp-block-heading\">\u00c0 quoi ressemble une migration r\u00e9aliste de SolarWinds<\/h2><p class=\"wp-block-paragraph\">La plupart des \u00e9quipes d'entreprise craignent qu'une transition ne cr\u00e9e plus de risques que de rester sur place. Une migration r\u00e9aliste commence g\u00e9n\u00e9ralement par une couverture qui se chevauche dans les environnements d'infrastructure et de r\u00e9seau fondamentaux, puis s'\u00e9tend au cloud, aux logs et \u00e0 l'exp\u00e9rience num\u00e9rique \u00e0 mesure que la confiance grandit. \u00c9tant donn\u00e9 que la s\u00e9quence de migration et le retrait des outils varient selon l'environnement, les \u00e9quipes doivent planifier la variabilit\u00e9 plut\u00f4t qu'une progression lin\u00e9aire claire.<\/p><p class=\"wp-block-paragraph\">Tester la plateforme lors d'une \u00e9valuation r\u00e9elle reste important pour valider ces flux de travail. Plut\u00f4t que de se fier uniquement \u00e0 une liste de contr\u00f4le, les \u00e9quipes devraient rechercher un processus d'\u00e9valuation structur\u00e9 qui aide \u00e0 confirmer la simplicit\u00e9 du d\u00e9ploiement, la profondeur de la couverture et l'ad\u00e9quation op\u00e9rationnelle dans le contexte de la d\u00e9cision d'achat globale. LogicMonitor prend en charge ce type de validation en aidant les \u00e9quipes \u00e0 renforcer leur confiance technique avant de s'engager dans une migration plus large.<\/p><p class=\"wp-block-paragraph\">Le soutien joue aussi un r\u00f4le ; <a href=\"https:\/\/unicorn1.wpengine.com\/resources\/how-coca-cola-bottling-consolidated-have-revolutionized-their-it-infrastructure\">Coca-Cola Consolidated<\/a> effectu\u00e9 une mise en \u0153uvre en quelques semaines gr\u00e2ce \u00e0 une collaboration et une formation \u00e9troites. La migration est autant un probl\u00e8me d'adoption qu'un probl\u00e8me technique.<\/p><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50\">\n  \n  <div class=\"rtc-text-content__wrapper\">\n    \n          <div class=\"rtc-text-content__body fs-sm-text-md fs-md-text-lg fs-lg-text-lg text-core-blue-900\">\n        <p>Veuillez examiner le document de pr\u00e9sentation de la solution LogicMonitor vs SolarWinds.<\/p>\n      <\/div>\n    \n          \n      \n              <div>\n            <a href=\"https:\/\/unicorn1.wpengine.com\/resources\/logicmonitor-vs-solarwinds-solution-brief\" class=\"btn btn-link\" target=\"_self\">\n        Allons-y          <span class=\"icon-end\"><svg class=\"\" width=\"20px\" height=\"20px\" style=\"fill: #060F4B\">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-arrow-right\"><\/use>\n    <\/svg><\/span>\n      <\/a>\n        <\/div>\n            <\/div>\n<\/div><h2 id=\"h-cost-and-licensing-should-be-part-of-the-evaluation\" class=\"wp-block-heading\">Le co\u00fbt et la licence doivent faire partie de l'\u00e9valuation<\/h2><p class=\"wp-block-paragraph\">Le co\u00fbt doit \u00eatre \u00e9valu\u00e9 parall\u00e8lement \u00e0 l'architecture, en se concentrant sur la capacit\u00e9 de la structure \u00e0 perdurer face aux changements d'environnement. Les acheteurs doivent comprendre comment un fournisseur tarife les \u00e9l\u00e9ments surveill\u00e9s dans des environnements hybrides. LogicMonitor utilise des packages de plateformes et des unit\u00e9s hybrides pour couvrir diff\u00e9rents types de ressources dans les environnements sur site, cloud et p\u00e9riph\u00e9riques.<\/p><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50\">\n  \n  <div class=\"rtc-text-content__wrapper\">\n    \n          <div class=\"rtc-text-content__body fs-sm-text-md fs-md-text-lg fs-lg-text-lg text-core-blue-900\">\n        <p>Une unit\u00e9 hybride \u00e9quivaut \u00e0 un appareil surveill\u00e9 par un collecteur sur site, une infrastructure en tant que service (IaaS) cloud, sept plateformes en tant que service (PaaS) cloud ou cinq points d'acc\u00e8s sans fil.<\/p>\n      <\/div>\n    \n      <\/div>\n<\/div><p class=\"wp-block-paragraph\">Le probl\u00e8me principal est le co\u00fbt total de possession (TCO). Le prix d'entr\u00e9e ne refl\u00e8te pas les frais g\u00e9n\u00e9raux li\u00e9s \u00e0 l'extension de la couverture, \u00e0 la fr\u00e9quence des changements de licence, ni les points o\u00f9 les frais premium augmentent le co\u00fbt au fil du temps. Le prix, la gouvernance et la d\u00e9pendance vis-\u00e0-vis du fournisseur doivent \u00eatre \u00e9valu\u00e9s dans le cadre du fonctionnement \u00e0 long terme de la plateforme.<\/p><h2 id=\"h-solarwinds-vs-logicmonitor-what-actually-matters\" class=\"wp-block-heading\">SolarWinds vs. LogicMonitor : ce qui compte vraiment<\/h2><p class=\"wp-block-paragraph\">La comparaison se r\u00e9sume \u00e0 savoir si une plateforme peut prendre en charge un environnement hybride \u00e0 grande \u00e9chelle sans n\u00e9cessiter une maintenance constante.<\/p><h3 id=\"h-comparison-table-logicmonitor-vs-solarwinds\" class=\"wp-block-heading\">Tableau comparatif : LogicMonitor vs. SolarWinds<\/h3><figure class=\"wp-block-table\"><table class=\"has-fixed-layout\"><tbody><tr><td><strong>Dimension<\/strong><\/td><td><strong>LogicMonitor<\/strong><\/td><td><strong>SolarWinds<\/strong><\/td><\/tr><tr><td><strong>Approche de plateforme<\/strong><\/td><td>Plateforme d'observabilit\u00e9 unifi\u00e9e, hybride et ax\u00e9e sur l'IA pour un IT autonome.<\/td><td>Ensemble de produits modulaires pour la surveillance et les op\u00e9rations informatiques.<\/td><\/tr><tr><td><strong>Mod\u00e8le de d\u00e9ploiement<\/strong><\/td><td>Plateforme SaaS avec des collecteurs sans agent qui prennent en charge le d\u00e9ploiement et la d\u00e9couverte pour le cloud hybride et le cloud.<\/td><td>Le portefeuille refl\u00e8te la surveillance de l'infrastructure h\u00e9rit\u00e9e et les flux de travail d\u00e9pendant des produits.&nbsp;<\/td><\/tr><tr><td><strong>D\u00e9lai de mise en valeur<\/strong><\/td><td>D\u00e9ploiement rapide du collecteur, d\u00e9couverte automatique et int\u00e9gration plus rapide pour les environnements hybrides.<\/td><td>Mixte ; les outils traditionnels sont souvent d\u00e9crits comme n\u00e9cessitant une configuration intensive.&nbsp;<\/td><\/tr><tr><td><strong>IA et Automatisation<\/strong><\/td><td>AI first : Edwin AI prend en charge les enqu\u00eates contextuelles, la corr\u00e9lation d'\u00e9v\u00e9nements, la priorisation des alertes, la RCA bas\u00e9e sur des preuves et des flux de travail de r\u00e9ponse plus connect\u00e9s dans les environnements hybrides.<\/td><td>Les capacit\u00e9s de l'IA existent, mais elles sont moins centrales dans le positionnement public.<\/td><\/tr><tr><td><strong>Exp\u00e9rience num\u00e9rique et visibilit\u00e9 sur Internet<\/strong><\/td><td>Surveillance synth\u00e9tique native DEM avec surveillance \u00e9tendue des performances Internet et de l'exp\u00e9rience num\u00e9rique.<\/td><td>Capacit\u00e9s d'exp\u00e9rience num\u00e9rique, mais moins centrales dans son histoire de plateforme plus large.<\/td><\/tr><tr><td><strong>Flux de travail d'enqu\u00eate<\/strong><\/td><td>Flux d'investigation plus unifi\u00e9, corr\u00e9lant journaux, m\u00e9triques, alertes et topologie pour r\u00e9duire le bruit et acc\u00e9l\u00e9rer le d\u00e9pannage dans des environnements complexes<\/td><td>Outils r\u00e9seau\/infrastructure solides gr\u00e2ce \u00e0 NetPath, PerfStack, tableaux de bord et analyse chronologique, mais les flux de travail d\u00e9pendent davantage des fonctionnalit\u00e9s et des produits.<\/td><\/tr><tr><td><strong>Utilisabilit\u00e9 inter-\u00e9quipes<\/strong><\/td><td>Utilisation partag\u00e9e simplifi\u00e9e entre les \u00e9quipes, avec une interface moderne, une navigation rationalis\u00e9e, des tableaux de bord au niveau des ressources et le RBAC pour un acc\u00e8s sp\u00e9cifique \u00e0 l'\u00e9quipe depuis une seule plateforme.<\/td><td>La complexit\u00e9 et l'expansion modulaire peuvent cr\u00e9er plus de friction entre les \u00e9quipes, en particulier dans les organisations plus petites ou moins sp\u00e9cialis\u00e9es.<\/td><\/tr><tr><td><strong>Co\u00fbt total de possession<\/strong><\/td><td>Le mod\u00e8le SaaS enti\u00e8rement h\u00e9berg\u00e9 permet de r\u00e9duire la maintenance de la plateforme, les frais administratifs et les efforts quotidiens n\u00e9cessaires pour maintenir la surveillance \u00e0 grande \u00e9chelle.<\/td><td>Le fardeau op\u00e9rationnel total peut augmenter avec une infrastructure auto-g\u00e9r\u00e9e, un entretien continu et une administration de plateforme plus pratique.<\/td><\/tr><tr><td><strong>Mod\u00e8le de tarification<\/strong><\/td><td>Tarification flexible et conditionnement de plateformes.<\/td><td>A tendance \u00e0 d\u00e9pendre davantage du mix de produits et de l'engagement des ventes.<\/td><\/tr><tr><td><strong>Certifications de s\u00e9curit\u00e9<\/strong><\/td><td>ISO\/IEC 27001:2022, SOC 2 Type 2, FedRAMP Moderate (LM pour Gov).<\/td><td>ISO\/IEC 27001:2022, SOC 2 Type 2, Common Criteria EAL2+.<\/td><\/tr><tr><td><strong>Mise en \u0153uvre et support post-vente<\/strong><\/td><td>Assistance disponible par chat en direct et par e-mail, avec une assistance t\u00e9l\u00e9phonique disponible via le support Premier, ainsi que des options de service \u00e0 plusieurs niveaux et des commentaires positifs des examinateurs sur le support de d\u00e9ploiement et d'adoption.<\/td><td>Certaines critiques de praticiens d\u00e9crivent la configuration comme complexe et la qualit\u00e9 du support comme incoh\u00e9rente.<\/td><\/tr><\/tbody><\/table><\/figure><p class=\"wp-block-paragraph\">Une plateforme construite autour de modules distincts peut couvrir les bons domaines, mais les \u00e9quipes ressentent souvent la complexit\u00e9 dans la mani\u00e8re dont elles \u00e9tudient et maintiennent l'environnement. Une plateforme con\u00e7ue pour connecter directement ces domaines r\u00e9duit ce poids op\u00e9rationnel.&nbsp;<\/p><h2 id=\"h-the-best-solarwinds-alternative-should-make-operations-simpler\" class=\"wp-block-heading\">La meilleure alternative \u00e0 SolarWinds devrait simplifier les op\u00e9rations<\/h2><p class=\"wp-block-paragraph\">La solution de substitution la plus robuste n'est pas celle qui semble la plus similaire sur une liste de contr\u00f4le ; c'est celle qui r\u00e9duit la complexit\u00e9 de l'environnement dans lequel vous op\u00e9rez r\u00e9ellement. Cela n\u00e9cessite d'\u00e9valuer l'architecture, la visibilit\u00e9, l'IA et les licences dans le cadre de la m\u00eame d\u00e9cision afin de garantir que la plateforme aide les \u00e9quipes \u00e0 enqu\u00eater plus rapidement et \u00e0 g\u00e9rer les changements avec moins de frais g\u00e9n\u00e9raux.<\/p><p class=\"wp-block-paragraph\">La bonne alternative \u00e0 SolarWinds ne doit pas simplement ajouter un autre tableau de bord, mais r\u00e9duire activement les efforts requis lors des incidents. L'objectif est d'adopter une plateforme qui rationalise la surveillance, simplifie le triage et acc\u00e9l\u00e8re la r\u00e9ponse pour les \u00e9quipes qui g\u00e8rent ces probl\u00e8mes au quotidien. Il s'agit de minimiser le temps pass\u00e9 \u00e0 \u00e9teindre des incendies afin que les \u00e9quipes puissent consacrer plus de temps \u00e0 des initiatives strat\u00e9giques, pilot\u00e9es par l'entreprise.&nbsp;<\/p><div class=\"rtc-text-content rtc-text-content__light bg-cool-grey-50\">\n      <span class=\"head-icon\"><svg class=\"\" width=\"50px\" height=\"50px\" style=\"fill: \">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-light-calendar-check\"><\/use>\n    <\/svg><\/span>\n  \n  <div class=\"rtc-text-content__wrapper\">\n          <h4 class=\"rtc-text-content__headline fs-sm-text-display-xxs fs-md-text-display-xs fs-lg-text-display-sm font-medium text-core-blue-900\">\n        Faites votre prochain mouvement au-del\u00e0 de SolarWinds avec plus de confiance.      <\/h4>\n    \n          <div class=\"rtc-text-content__body fs-sm-text-md fs-md-text-lg fs-lg-text-lg text-core-blue-900\">\n        <p>Discutez avec notre \u00e9quipe de votre environnement, de vos priorit\u00e9s et de la meilleure voie \u00e0 suivre.<\/p>\n      <\/div>\n    \n          \n      \n              <div>\n            <a href=\"https:\/\/www.logicmonitor.com\/contact-us\" class=\"btn btn-link\" target=\"_self\">\n        Commencez ici          <span class=\"icon-end\"><svg class=\"\" width=\"20px\" height=\"20px\" style=\"fill: #060F4B\">\n        <use xlink:href=\"https:\/\/www.logicmonitor.com\/wp-content\/themes\/unicorntwentyfive\/assets\/icons\/sprite.svg#icon-arrow-right\"><\/use>\n    <\/svg><\/span>\n      <\/a>\n        <\/div>\n            <\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Remplacer SolarWinds ne consiste pas seulement \u00e0 \u00e9galer les fonctionnalit\u00e9s. Il s'agit de choisir une plateforme qui r\u00e9duit la complexit\u00e9 de l'infrastructure hybride et des d\u00e9pendances Internet.<\/p>","protected":false},"author":14,"featured_media":592021,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"unicorn_plugin_options_block_body_class":"","footnotes":""},"categories":[1],"tags":[],"industry":[6790],"role":[7820],"lm_strategic_tags":[],"topic":[6775],"author_attribution":[8014],"lm_product":[],"class_list":["post-609790","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","industry-all","role-it-operations-manager","topic-infrastructure","author_attribution-sofia-burton"],"acf":{"page_language":"english","translated_pages":"","updated_date":null,"author_section_checkbox":false,"author_image":null,"author_linkedin":"","author_name":"","author_job_title":"","author_dept":"","author_bio":"","reviewer_name":""},"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.4 (Yoast SEO v28.4) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>What to Look for in a SolarWinds Alternative | LogicMonitor<\/title>\n<meta name=\"description\" content=\"Evaluating a SolarWinds alternative takes more than a checklist. Compare architecture, AI, and cost to find a platform that reduces operational complexity.\" \/>\n<meta name=\"robots\" content=\"noindex, nofollow\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"How to Evaluate a SolarWinds Alternative\" \/>\n<meta property=\"og:description\" content=\"Evaluating a SolarWinds alternative takes more than a checklist. Compare architecture, AI, and cost to find a platform that reduces operational complexity.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.logicmonitor.com\/fr\/blog\/solarwinds-alternative-evaluation-guide\" \/>\n<meta property=\"og:site_name\" content=\"LogicMonitor\" \/>\n<meta property=\"article:published_time\" content=\"2026-09-01T15:27:43+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-09-03T22:13:35+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2025\/07\/Blog_Switching_Solarwinds_Hero-Image-350-MAX-px_transparent-2.webp\" \/>\n\t<meta property=\"og:image:width\" content=\"825\" \/>\n\t<meta property=\"og:image:height\" content=\"525\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/webp\" \/>\n<meta name=\"author\" content=\"rahma.naser@logicmonitor.com\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/solarwinds-alternative-evaluation-guide#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/solarwinds-alternative-evaluation-guide\"},\"author\":{\"name\":\"rahma.naser@logicmonitor.com\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/8b0f875e5edfedbcb4e6a71d6ff6c10e\"},\"headline\":\"How to Evaluate a SolarWinds Alternative\",\"datePublished\":\"2026-09-01T15:27:43+00:00\",\"dateModified\":\"2026-09-03T22:13:35+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/solarwinds-alternative-evaluation-guide\"},\"wordCount\":1833,\"image\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/solarwinds-alternative-evaluation-guide#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2025\\\/07\\\/Blog_Switching_Solarwinds_Hero-Image-350-MAX-px_transparent-2.webp\",\"articleSection\":[\"Uncategorized\"],\"inLanguage\":\"fr-FR\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/solarwinds-alternative-evaluation-guide\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/solarwinds-alternative-evaluation-guide\",\"name\":\"What to Look for in a SolarWinds Alternative | LogicMonitor\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/solarwinds-alternative-evaluation-guide#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/solarwinds-alternative-evaluation-guide#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2025\\\/07\\\/Blog_Switching_Solarwinds_Hero-Image-350-MAX-px_transparent-2.webp\",\"datePublished\":\"2026-09-01T15:27:43+00:00\",\"dateModified\":\"2026-09-03T22:13:35+00:00\",\"author\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/8b0f875e5edfedbcb4e6a71d6ff6c10e\"},\"description\":\"Evaluating a SolarWinds alternative takes more than a checklist. Compare architecture, AI, and cost to find a platform that reduces operational complexity.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/solarwinds-alternative-evaluation-guide#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/solarwinds-alternative-evaluation-guide\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/solarwinds-alternative-evaluation-guide#primaryimage\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2025\\\/07\\\/Blog_Switching_Solarwinds_Hero-Image-350-MAX-px_transparent-2.webp\",\"contentUrl\":\"https:\\\/\\\/www.logicmonitor.com\\\/wp-content\\\/uploads\\\/2025\\\/07\\\/Blog_Switching_Solarwinds_Hero-Image-350-MAX-px_transparent-2.webp\",\"width\":825,\"height\":525},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/blog\\\/solarwinds-alternative-evaluation-guide#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.logicmonitor.com\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"How to Evaluate a SolarWinds Alternative\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#website\",\"url\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/\",\"name\":\"LogicMonitor\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.logicmonitor.com\\\/fr\\\/#\\\/schema\\\/person\\\/8b0f875e5edfedbcb4e6a71d6ff6c10e\",\"name\":\"rahma.naser@logicmonitor.com\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"What to Look for in a SolarWinds Alternative | LogicMonitor","description":"\u00c9valuer une alternative \u00e0 SolarWinds demande plus qu'une simple liste de contr\u00f4le. Comparez l'architecture, l'IA et le co\u00fbt pour trouver une plateforme qui r\u00e9duit la complexit\u00e9 op\u00e9rationnelle.","robots":{"index":"noindex","follow":"nofollow"},"og_locale":"fr_FR","og_type":"article","og_title":"How to Evaluate a SolarWinds Alternative","og_description":"Evaluating a SolarWinds alternative takes more than a checklist. Compare architecture, AI, and cost to find a platform that reduces operational complexity.","og_url":"https:\/\/www.logicmonitor.com\/fr\/blog\/solarwinds-alternative-evaluation-guide","og_site_name":"LogicMonitor","article_published_time":"2026-09-01T15:27:43+00:00","article_modified_time":"2026-09-03T22:13:35+00:00","og_image":[{"width":825,"height":525,"url":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2025\/07\/Blog_Switching_Solarwinds_Hero-Image-350-MAX-px_transparent-2.webp","type":"image\/webp"}],"author":"rahma.naser@logicmonitor.com","twitter_card":"summary_large_image","twitter_misc":{"Written by":"","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/solarwinds-alternative-evaluation-guide#article","isPartOf":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/solarwinds-alternative-evaluation-guide"},"author":{"name":"rahma.naser@logicmonitor.com","@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/8b0f875e5edfedbcb4e6a71d6ff6c10e"},"headline":"How to Evaluate a SolarWinds Alternative","datePublished":"2026-09-01T15:27:43+00:00","dateModified":"2026-09-03T22:13:35+00:00","mainEntityOfPage":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/solarwinds-alternative-evaluation-guide"},"wordCount":1833,"image":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/solarwinds-alternative-evaluation-guide#primaryimage"},"thumbnailUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2025\/07\/Blog_Switching_Solarwinds_Hero-Image-350-MAX-px_transparent-2.webp","articleSection":["Uncategorized"],"inLanguage":"fr-FR"},{"@type":"WebPage","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/solarwinds-alternative-evaluation-guide","url":"https:\/\/www.logicmonitor.com\/fr\/blog\/solarwinds-alternative-evaluation-guide","name":"What to Look for in a SolarWinds Alternative | LogicMonitor","isPartOf":{"@id":"https:\/\/www.logicmonitor.com\/fr\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/solarwinds-alternative-evaluation-guide#primaryimage"},"image":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/solarwinds-alternative-evaluation-guide#primaryimage"},"thumbnailUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2025\/07\/Blog_Switching_Solarwinds_Hero-Image-350-MAX-px_transparent-2.webp","datePublished":"2026-09-01T15:27:43+00:00","dateModified":"2026-09-03T22:13:35+00:00","author":{"@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/8b0f875e5edfedbcb4e6a71d6ff6c10e"},"description":"Evaluating a SolarWinds alternative takes more than a checklist. Compare architecture, AI, and cost to find a platform that reduces operational complexity.","breadcrumb":{"@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/solarwinds-alternative-evaluation-guide#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.logicmonitor.com\/fr\/blog\/solarwinds-alternative-evaluation-guide"]}]},{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/solarwinds-alternative-evaluation-guide#primaryimage","url":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2025\/07\/Blog_Switching_Solarwinds_Hero-Image-350-MAX-px_transparent-2.webp","contentUrl":"https:\/\/www.logicmonitor.com\/wp-content\/uploads\/2025\/07\/Blog_Switching_Solarwinds_Hero-Image-350-MAX-px_transparent-2.webp","width":825,"height":525},{"@type":"BreadcrumbList","@id":"https:\/\/www.logicmonitor.com\/fr\/blog\/solarwinds-alternative-evaluation-guide#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.logicmonitor.com\/"},{"@type":"ListItem","position":2,"name":"How to Evaluate a SolarWinds Alternative"}]},{"@type":"WebSite","@id":"https:\/\/www.logicmonitor.com\/fr\/#website","url":"https:\/\/www.logicmonitor.com\/fr\/","name":"LogicMonitor","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.logicmonitor.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Person","@id":"https:\/\/www.logicmonitor.com\/fr\/#\/schema\/person\/8b0f875e5edfedbcb4e6a71d6ff6c10e","name":"rahma.naser@logicmonitor.com"}]}},"_links":{"self":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/609790","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/users\/14"}],"replies":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/comments?post=609790"}],"version-history":[{"count":5,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/609790\/revisions"}],"predecessor-version":[{"id":626105,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/posts\/609790\/revisions\/626105"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/media\/592021"}],"wp:attachment":[{"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/media?parent=609790"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/categories?post=609790"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/tags?post=609790"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/industry?post=609790"},{"taxonomy":"role","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/role?post=609790"},{"taxonomy":"lm_strategic_tags","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/lm_strategic_tags?post=609790"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/topic?post=609790"},{"taxonomy":"author_attribution","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/author_attribution?post=609790"},{"taxonomy":"lm_product","embeddable":true,"href":"https:\/\/www.logicmonitor.com\/fr\/wp-json\/wp\/v2\/lm_product?post=609790"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}]