AWS wellarchitected: Restructure ADVOPS02 observability page; add bot traffic guidance
Summary
Rewrites the ADVOPS02 observability best-practice page: adds a capability intent section, a 'Common issues to watch for' list, expands the best-practices links (BP01-BP09), updates the question wording, and adds guidance on classifying bot/agent traffic and correlating telemetry across layers.
Security assessment
The change is documentation-only guidance for advertising observability. It adds security-adjacent best practices: centralized logging, structured metrics/traces with correlation identifiers, and distinguishing authorized crawlers/licensed AI agents from unauthorized scrapers and fraudulent impression traffic. No specific vulnerability, CVE, or incident is referenced, so it is not security_issue_related, but it does document monitoring/logging and bot-traffic classification practices.
Evidence
+ * Grouping licensed AI agents, authorized crawlers, unauthorized scrapers, and fraudulent impression traffic into one bot category.
Diff
diff --git a/wellarchitected/latest/video-streaming-advertising-lens/advops02.md b/wellarchitected/latest/video-streaming-advertising-lens/advops02.md index 039489f..8ff947f 100644 --- a//wellarchitected/latest/video-streaming-advertising-lens/advops02.md +++ b//wellarchitected/latest/video-streaming-advertising-lens/advops02.md @@ -7 +7 @@ -# Prepare +Capability intentCommon issues to watch for @@ -9 +9,5 @@ -ADVOPS02: How do you ensure comprehensive observability and monitoring across your advertising workload? +# Advertising workload observability + +Advertising delivery depends on distributed systems, partner connections, automated decisions, and channel-specific fulfillment paths. Operators need correlated telemetry across technical and business layers to identify whether a failure affects infrastructure, auction behavior, campaign pacing, or revenue. This capability defines the observability needed to detect, diagnose, and route those conditions. + +ADVOPS02: How do you observe advertising workload health and connect technical signals to delivery and revenue outcomes? @@ -10,0 +15,28 @@ ADVOPS02: How do you ensure comprehensive observability and monitoring across yo +[ADVOPS02-BP01 Implement monitoring across each layer of your advertising stack](./advops02-bp01.html) +[ADVOPS02-BP02 Collect and analyze detailed metrics for successful operations and ad campaigns](./advops02-bp02.html) +[ADVOPS02-BP03 Implement centralized logging to aggregate logs from all components of your advertising stack](./advops02-bp03.html) +[ADVOPS02-BP04 Instrument your advertising application code and infrastructure to emit detailed, structured logs and metrics](./advops02-bp04.html) +[ADVOPS02-BP05 Monitor partner connectivity health and traffic management effectiveness across your advertising network](./advops02-bp05.html) +[ADVOPS02-BP06 Implement distributed tracing for automated and agent-driven advertising operations](./advops02-bp06.html) +[ADVOPS02-BP07 Implement observability for bot and agent traffic in AI content licensing](./advops02-bp07.html) +[ADVOPS02-BP08 Monitor server-side auction health and demand partner yield across your header bidding infrastructure](./advops02-bp08.html) +[ADVOPS02-BP09 Implement centralized observability for campaign delivery pacing and fulfillment across linear and digital channels](./advops02-bp09.html) + +## Capability intent + + * Advertising workloads have telemetry across infrastructure, applications, delivery pipelines, user experience, and monetization layers. + + * Structured metrics, logs, and traces share correlation identifiers so teams can follow failures across components and automated decisions. + + * Partner connectivity and traffic-management health are measured independently from application health and tied to bid outcomes. + + * Bot and agent traffic is classified by operational purpose and revenue effect rather than treated as one traffic category. + + * Server-side auction health is visible by adapter, demand partner, identity framework, and yield contribution. + + * Campaign pacing and fulfillment are measured against shared commitments across linear and digital channels. + + + + +## Common issues to watch for @@ -12 +44 @@ ADVOPS02: How do you ensure comprehensive observability and monitoring across yo -Advertising workloads often involve complex and distributed systems that must operate reliably and efficiently. To detect, diagnose, and resolve issues quickly, it's important to have comprehensive observability across the entire advertising workload. This includes implementing monitoring and logging solutions that provide visibility into key metrics, events, and dependencies between various components. By having a holistic view of the workload's performance and health, you can proactively identify and address problems. This approach can help ensure a reliable and predictable advertising experience for your customers. + * Monitoring infrastructure health without a monetization layer, allowing technical SLOs to remain healthy while revenue declines. @@ -14 +46 @@ Advertising workloads often involve complex and distributed systems that must op -###### Best practices + * Treating SGAI health as one completion metric instead of measuring manifest generation, content delivery, and client retrieval separately. @@ -16 +48 @@ Advertising workloads often involve complex and distributed systems that must op - * [ADVOPS02-BP01 Implement monitoring across each layer of your advertising stack including infrastructure, applications, and user experience](./advops02-bp01.html) + * Collecting metrics, logs, and traces without consistent identifiers, which leaves teams unable to correlate one failure across layers. @@ -18 +50 @@ Advertising workloads often involve complex and distributed systems that must op - * [ADVOPS02-BP02 Collect and analyze detailed metrics for successful operations and ad campaigns](./advops02-bp02.html) + * Grouping licensed AI agents, authorized crawlers, unauthorized scrapers, and fraudulent impression traffic into one bot category. @@ -20 +52 @@ Advertising workloads often involve complex and distributed systems that must op - * [ADVOPS02-BP03 Implement centralized logging to aggregate logs from all components of your advertising stack](./advops02-bp03.html) + * Monitoring aggregate auction revenue without per-adapter and per-identity-framework dimensions, which hides underperforming demand partners. @@ -22 +54 @@ Advertising workloads often involve complex and distributed systems that must op - * [ADVOPS02-BP04 Instrument your advertising application code and infrastructure to emit detailed, structured logs and metrics](./advops02-bp04.html) + * Maintaining separate linear and digital campaign dashboards or relying on delayed reports and static pacing thresholds, which reduces the time available for recovery. @@ -33 +65 @@ To use the Amazon Web Services Documentation, Javascript must be enabled. Please -ADVOPS01-BP04 Establish data governance and compliance operations +ADVOPS01-BP06 Implement a unified campaign management interface across linear and digital operations @@ -35 +67 @@ ADVOPS01-BP04 Establish data governance and compliance operations -ADVOPS02-BP01 Implement monitoring across each layer of your advertising stack including infrastructure, applications, and user experience +ADVOPS02-BP01 Implement monitoring across each layer of your advertising stack