Your LLM feature went out at 2 a.m. last Thursday. Latency is fine. Error rate is zero. And somewhere, quietly, it is lying to a customer.
Traditional observability cannot see this. CPU graphs, HTTP status codes, and p99 dashboards were built for systems that either work or crash. LLMs do neither. They return a confident sentence, the span closes green, and the failure lives in the content.
If you ship LLM features in production — as a backend engineer, a platform engineer, an SRE who inherited someone else's prompt — this book is the operational handbook you have been missing. It is not a theory book about transformers. It is not a prompt engineering tour. It is the stack you actually need on Monday morning to know your AI works.
What you get: the three new pillars (traces, evals, cost and drift metrics), built first on vendor-neutral OpenTelemetry GenAI semantic conventions, then layered with the tools that matter in 2026 — Langfuse, LangSmith, Arize Phoenix, Braintrust, DeepEval, Helicone, and a roll-your-own OTel Collector + ClickHouse + Grafana stack for teams that want everything in-house. Every tool gets an honest verdict: what it is best at, what it is bad at, when to pick it, what it costs.
You will learn how to capture a full LLM decision path as a trace, run evals continuously in CI and in production, track token cost per user and per feature, detect drift before your users do, and write incident response runbooks for a failure mode your pager has never seen. Real code in Python, Go, and TypeScript. Real dashboards. Real traces.
Complementary to Hamel Husain's Evals for AI Engineers (O'Reilly, 2026): where that book goes deep on eval methodology for ML engineers, this one covers the wider operational stack — tracing, tooling, cost, drift, and on-call — for the platform-engineer reader.
By the end, you will have a production-readiness checklist you can run against your own system and mean it when you tell your boss the answer is yes. The first chapter starts with a real incident. Monday morning, you will have something to do.
Book 1 of The AI Engineer's Library.
"Sinopsis" puede pertenecer a otra edición de este libro.
Librería: GreatBookPrices, Columbia, MD, Estados Unidos de America
Condición: New. Nº de ref. del artículo: 53721973-n
Cantidad disponible: Más de 20 disponibles
Librería: California Books, Miami, FL, Estados Unidos de America
Condición: New. Print on Demand. Nº de ref. del artículo: I-9798257519970
Cantidad disponible: Más de 20 disponibles
Librería: GreatBookPrices, Columbia, MD, Estados Unidos de America
Condición: As New. Unread book in perfect condition. Nº de ref. del artículo: 53721973
Cantidad disponible: Más de 20 disponibles
Librería: PBShop.store US, Wood Dale, IL, Estados Unidos de America
PAP. Condición: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000. Nº de ref. del artículo: L0-9798257519970
Cantidad disponible: Más de 20 disponibles
Librería: Grand Eagle Retail, Bensenville, IL, Estados Unidos de America
Paperback. Condición: new. Paperback. Your LLM feature went out at 2 a.m. last Thursday. Latency is fine. Error rate is zero. And somewhere, quietly, it is lying to a customer. Traditional observability cannot see this. CPU graphs, HTTP status codes, and p99 dashboards were built for systems that either work or crash. LLMs do neither. They return a confident sentence, the span closes green, and the failure lives in the content. If you ship LLM features in production - as a backend engineer, a platform engineer, an SRE who inherited someone else's prompt - this book is the operational handbook you have been missing. It is not a theory book about transformers. It is not a prompt engineering tour. It is the stack you actually need on Monday morning to know your AI works. What you get: the three new pillars (traces, evals, cost and drift metrics), built first on vendor-neutral OpenTelemetry GenAI semantic conventions, then layered with the tools that matter in 2026 - Langfuse, LangSmith, Arize Phoenix, Braintrust, DeepEval, Helicone, and a roll-your-own OTel Collector + ClickHouse + Grafana stack for teams that want everything in-house. Every tool gets an honest verdict: what it is best at, what it is bad at, when to pick it, what it costs. You will learn how to capture a full LLM decision path as a trace, run evals continuously in CI and in production, track token cost per user and per feature, detect drift before your users do, and write incident response runbooks for a failure mode your pager has never seen. Real code in Python, Go, and TypeScript. Real dashboards. Real traces. Complementary to Hamel Husain's Evals for AI Engineers (O'Reilly, 2026): where that book goes deep on eval methodology for ML engineers, this one covers the wider operational stack - tracing, tooling, cost, drift, and on-call - for the platform-engineer reader. By the end, you will have a production-readiness checklist you can run against your own system and mean it when you tell your boss the answer is yes. The first chapter starts with a real incident. Monday morning, you will have something to do. Book 1 of The AI Engineer's Library. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability. Nº de ref. del artículo: 9798257519970
Cantidad disponible: 1 disponibles
Librería: PBShop.store UK, Fairford, GLOS, Reino Unido
PAP. Condición: New. New Book. Delivered from our UK warehouse in 4 to 14 business days. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000. Nº de ref. del artículo: L0-9798257519970
Cantidad disponible: Más de 20 disponibles
Librería: GreatBookPricesUK, Woodford Green, Reino Unido
Condición: As New. Unread book in perfect condition. Nº de ref. del artículo: 53721973
Cantidad disponible: Más de 20 disponibles
Librería: CitiRetail, Stevenage, Reino Unido
Paperback. Condición: new. Paperback. Your LLM feature went out at 2 a.m. last Thursday. Latency is fine. Error rate is zero. And somewhere, quietly, it is lying to a customer. Traditional observability cannot see this. CPU graphs, HTTP status codes, and p99 dashboards were built for systems that either work or crash. LLMs do neither. They return a confident sentence, the span closes green, and the failure lives in the content. If you ship LLM features in production - as a backend engineer, a platform engineer, an SRE who inherited someone else's prompt - this book is the operational handbook you have been missing. It is not a theory book about transformers. It is not a prompt engineering tour. It is the stack you actually need on Monday morning to know your AI works. What you get: the three new pillars (traces, evals, cost and drift metrics), built first on vendor-neutral OpenTelemetry GenAI semantic conventions, then layered with the tools that matter in 2026 - Langfuse, LangSmith, Arize Phoenix, Braintrust, DeepEval, Helicone, and a roll-your-own OTel Collector + ClickHouse + Grafana stack for teams that want everything in-house. Every tool gets an honest verdict: what it is best at, what it is bad at, when to pick it, what it costs. You will learn how to capture a full LLM decision path as a trace, run evals continuously in CI and in production, track token cost per user and per feature, detect drift before your users do, and write incident response runbooks for a failure mode your pager has never seen. Real code in Python, Go, and TypeScript. Real dashboards. Real traces. Complementary to Hamel Husain's Evals for AI Engineers (O'Reilly, 2026): where that book goes deep on eval methodology for ML engineers, this one covers the wider operational stack - tracing, tooling, cost, drift, and on-call - for the platform-engineer reader. By the end, you will have a production-readiness checklist you can run against your own system and mean it when you tell your boss the answer is yes. The first chapter starts with a real incident. Monday morning, you will have something to do. Book 1 of The AI Engineer's Library. This item is printed on demand. Shipping may be from our UK warehouse or from our Australian or US warehouses, depending on stock availability. Nº de ref. del artículo: 9798257519970
Cantidad disponible: 1 disponibles
Librería: AHA-BUCH GmbH, Einbeck, Alemania
Taschenbuch. Condición: Neu. Neuware - Your LLM feature went out at 2 a.m. last Thursday. Latency is fine. Error rate is zero. And somewhere, quietly, it is lying to a customer. Traditional observability cannot see this. CPU graphs, HTTP status codes, and p99 dashboards were built for systems that either work or crash. LLMs do neither. They return a confident sentence, the span closes green, and the failure lives in the content. If you ship LLM features in production - as a backend engineer, a platform engineer, an SRE who inherited someone else's prompt - this book is the operational handbook you have been missing. It is not a theory book about transformers. It is not a prompt engineering tour. It is the stack you actually need on Monday morning to know your AI works. What you get: the three new pillars (traces, evals, cost and drift metrics), built first on vendor-neutral OpenTelemetry GenAI semantic conventions, then layered with the tools that matter in 2026 - Langfuse, LangSmith, Arize Phoenix, Braintrust, DeepEval, Helicone, and a roll-your-own OTel Collector + ClickHouse + Grafana stack for teams that want everything in-house. Every tool gets an honest verdict: what it is best at, what it is bad at, when to pick it, what it costs. You will learn how to capture a full LLM decision path as a trace, run evals continuously in CI and in production, track token cost per user and per feature, detect drift before your users do, and write incident response runbooks for a failure mode your pager has never seen. Real code in Python, Go, and TypeScript. Real dashboards. Real traces. Complementary to Hamel Husain's Evals for AI Engineers (O'Reilly, 2026): where that book goes deep on eval methodology for ML engineers, this one covers the wider operational stack - tracing, tooling, cost, drift, and on-call - for the platform-engineer reader. By the end, you will have a production-readiness checklist you can run against your own system and mean it when you tell your boss the answer is yes. The first chapter starts with a real incident. Monday morning, you will have something to do. Book 1 of The AI Engineer's Library. Nº de ref. del artículo: 9798257519970
Cantidad disponible: 2 disponibles