Wright Zebb (15 results)

Condition: New.

Condition: New.

Paperback. Condition: new. Paperback. Stop switching tabs. Start finding out what's going on.Whenever there's a major outage, it always starts the very same way. Five tools are open, four teams are talking past each other, and one question nobody can settle quickly. The idea behind this book is to give engineers the tools they need to keep an eye on things without breaking the bottom line.This book brings together logs, metrics, traces, frontend sessions and AI telemetry into one place, so you can figure out what's going on when things go wrong. It's all about setting up a production-ready OpenObserve cluster, hooking up every signal through OpenTelemetry, and tweaking the data until long-term storage becomes budget-friendly.There are several chapters that look at what can go wrong in a business, like infrastructure, networks, apps, data layers and user experience. They even talk about the AI service that went up by three times overnight. In the AI era, the way we think about failure has changed. Things like models drifting, prompts inflating and cost moving faster than latency. If you've got observability built for three signals, you won't be able to see any of them. This book shows what a unified platform can do.Key LearningsBuild a signal inventory tying every business driver to a measurable objective.Deploy a high-availability OpenObserve cluster with object storage, SSO, and role-based access.Instrument any stack through OpenTelemetry without rewriting application code or locking into a vendor.Shape telemetry with pipelines, VRL functions, and enrichment tables to cut ingest cost sharply.Design dashboards that engineers can actually open during incidents rather than decorative executive wall displays.Define burn-rate alerts and SLOs that flag real degradation without generating alert fatigue.Apply a repeatable seven-step diagnostic loop from scope through evidence to verified repair.Recognise infrastructure red flags like CPU throttling, disk eviction, and autoscaler thrash early.Diagnose AI-layer failures including token inflation, prompt drift, and runaway cost per request.Migrate from an existing platform using dual-run, honest measurement, and reversible cutover.Table of ContentGetting Started with OpenObserveHow Systems Fail with Hidden Failures?OpenObserve and Production-Ready EnvironmentGetting Every Signal InShaping, Governing and Affording DataBuilding Dashboards Engineers Actually UseFlagging Engine, Alerts, SLOs and IncidentsDiagnostic MethodInfrastructure and Kubernetes Red FlagsNetwork and Edge Red FlagsApplication and Service Red FlagsData-Layer Red FlagsUser-Facing and AI-Layer Red FlagsScaling OpenObserveTarget AudienceWhether you're an SRE, platform engineer or architect, you'll find configuration, queries, dashboards and alert definitions you can apply directly. You don't need to have experience with OpenObserve. This item is printed on demand. Shipping may be from multiple locations in the US or from the UK, depending on stock availability.…

PAP. Condition: New. New Book. Shipped from UK. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

PAP. Condition: New. New Book. Delivered from our UK warehouse in 4 to 14 business days. THIS BOOK IS PRINTED ON DEMAND. Established seller since 2000.

Taschenbuch. Condition: Neu. This item is printed on demand - it takes 3-4 days longer - Neuware 204 pp. Englisch.

Taschenbuch. Condition: Neu. This item is printed on demand - it takes 3-4 days longer - Neuware 344 pp. Englisch.

Paperback. Condition: new. Paperback. Stop switching tabs. Start finding out what's going on.Whenever there's a major outage, it always starts the very same way. Five tools are open, four teams are talking past each other, and one question nobody can settle quickly. The idea behind this book is to give engineers the tools they need to keep an eye on things without breaking the bottom line.This book brings together logs, metrics, traces, frontend sessions and AI telemetry into one place, so you can figure out what's going on when things go wrong. It's all about setting up a production-ready OpenObserve cluster, hooking up every signal through OpenTelemetry, and tweaking the data until long-term storage becomes budget-friendly.There are several chapters that look at what can go wrong in a business, like infrastructure, networks, apps, data layers and user experience. They even talk about the AI service that went up by three times overnight. In the AI era, the way we think about failure has changed. Things like models drifting, prompts inflating and cost moving faster than latency. If you've got observability built for three signals, you won't be able to see any of them. This book shows what a unified platform can do.Key LearningsBuild a signal inventory tying every business driver to a measurable objective.Deploy a high-availability OpenObserve cluster with object storage, SSO, and role-based access.Instrument any stack through OpenTelemetry without rewriting application code or locking into a vendor.Shape telemetry with pipelines, VRL functions, and enrichment tables to cut ingest cost sharply.Design dashboards that engineers can actually open during incidents rather than decorative executive wall displays.Define burn-rate alerts and SLOs that flag real degradation without generating alert fatigue.Apply a repeatable seven-step diagnostic loop from scope through evidence to verified repair.Recognise infrastructure red flags like CPU throttling, disk eviction, and autoscaler thrash early.Diagnose AI-layer failures including token inflation, prompt drift, and runaway cost per request.Migrate from an existing platform using dual-run, honest measurement, and reversible cutover.Table of ContentGetting Started with OpenObserveHow Systems Fail with Hidden Failures?OpenObserve and Production-Ready EnvironmentGetting Every Signal InShaping, Governing and Affording DataBuilding Dashboards Engineers Actually UseFlagging Engine, Alerts, SLOs and IncidentsDiagnostic MethodInfrastructure and Kubernetes Red FlagsNetwork and Edge Red FlagsApplication and Service Red FlagsData-Layer Red FlagsUser-Facing and AI-Layer Red FlagsScaling OpenObserveTarget AudienceWhether you're an SRE, platform engineer or architect, you'll find configuration, queries, dashboards and alert definitions you can apply directly. You don't need to have experience with OpenObserve. This item is printed on demand. Shipping may be from our Sydney, NSW warehouse or from our UK or US warehouse, depending on stock availability.…

Paperback. Condition: new. Paperback. Stop switching tabs. Start finding out what's going on.Whenever there's a major outage, it always starts the very same way. Five tools are open, four teams are talking past each other, and one question nobody can settle quickly. The idea behind this book is to give engineers the tools they need to keep an eye on things without breaking the bottom line.This book brings together logs, metrics, traces, frontend sessions and AI telemetry into one place, so you can figure out what's going on when things go wrong. It's all about setting up a production-ready OpenObserve cluster, hooking up every signal through OpenTelemetry, and tweaking the data until long-term storage becomes budget-friendly.There are several chapters that look at what can go wrong in a business, like infrastructure, networks, apps, data layers and user experience. They even talk about the AI service that went up by three times overnight. In the AI era, the way we think about failure has changed. Things like models drifting, prompts inflating and cost moving faster than latency. If you've got observability built for three signals, you won't be able to see any of them. This book shows what a unified platform can do.Key LearningsBuild a signal inventory tying every business driver to a measurable objective.Deploy a high-availability OpenObserve cluster with object storage, SSO, and role-based access.Instrument any stack through OpenTelemetry without rewriting application code or locking into a vendor.Shape telemetry with pipelines, VRL functions, and enrichment tables to cut ingest cost sharply.Design dashboards that engineers can actually open during incidents rather than decorative executive wall displays.Define burn-rate alerts and SLOs that flag real degradation without generating alert fatigue.Apply a repeatable seven-step diagnostic loop from scope through evidence to verified repair.Recognise infrastructure red flags like CPU throttling, disk eviction, and autoscaler thrash early.Diagnose AI-layer failures including token inflation, prompt drift, and runaway cost per request.Migrate from an existing platform using dual-run, honest measurement, and reversible cutover.Table of ContentGetting Started with OpenObserveHow Systems Fail with Hidden Failures?OpenObserve and Production-Ready EnvironmentGetting Every Signal InShaping, Governing and Affording DataBuilding Dashboards Engineers Actually UseFlagging Engine, Alerts, SLOs and IncidentsDiagnostic MethodInfrastructure and Kubernetes Red FlagsNetwork and Edge Red FlagsApplication and Service Red FlagsData-Layer Red FlagsUser-Facing and AI-Layer Red FlagsScaling OpenObserveTarget AudienceWhether you're an SRE, platform engineer or architect, you'll find configuration, queries, dashboards and alert definitions you can apply directly. You don't need to have experience with OpenObserve. This item is printed on demand. Shipping may be from our UK warehouse or from our Australian or US warehouses, depending on stock availability.…

Taschenbuch. Condition: Neu. nach der Bestellung gedruckt Neuware - Printed after ordering - Stop switching tabs. Start finding out what's going on.Whenever there's a major outage, it always starts the very same way. Five tools are open, four teams are talking past each other, and one question nobody can settle quickly. The idea behind this book is to give engineers the tools they need to keep an eye on things without breaking the bottom line.This book brings together logs, metrics, traces, frontend sessions and AI telemetry into one place, so you can figure out what's going on when things go wrong. It's all about setting up a production-ready OpenObserve cluster, hooking up every signal through OpenTelemetry, and tweaking the data until long-term storage becomes budget-friendly.There are several chapters that look at what can go wrong in a business, like infrastructure, networks, apps, data layers and user experience. They even talk about the AI service that went up by three times overnight. In the AI era, the way we think about failure has changed. Things like models drifting, prompts inflating and cost moving faster than latency. If you've got observability built for three signals, you won't be able to see any of them. This book shows what a unified platform can do.Key LearningsBuild a signal inventory tying every business driver to a measurable objective.Deploy a high-availability OpenObserve cluster with object storage, SSO, and role-based access.Instrument any stack through OpenTelemetry without rewriting application code or locking into a vendor.Shape telemetry with pipelines, VRL functions, and enrichment tables to cut ingest cost sharply.Design dashboards that engineers can actually open during incidents rather than decorative executive wall displays.Define burn-rate alerts and SLOs that flag real degradation without generating alert fatigue.Apply a repeatable seven-step diagnostic loop from scope through evidence to verified repair.Recognise infrastructure red flags like CPU throttling, disk eviction, and autoscaler thrash early.Diagnose AI-layer failures including token inflation, prompt drift, and runaway cost per request.Migrate from an existing platform using dual-run, honest measurement, and reversible cutover.Table of ContentGetting Started with OpenObserveHow Systems Fail with Hidden Failures OpenObserve and Production-Ready EnvironmentGetting Every Signal InShaping, Governing and Affording DataBuilding Dashboards Engineers Actually UseFlagging Engine, Alerts, SLOs and IncidentsDiagnostic MethodInfrastructure and Kubernetes Red FlagsNetwork and Edge Red FlagsApplication and Service Red FlagsData-Layer Red FlagsUser-Facing and AI-Layer Red FlagsScaling OpenObserveTarget AudienceWhether you're an SRE, platform engineer or architect, you'll find configuration, queries, dashboards and alert definitions you can apply directly. You don't need to have experience with OpenObserve.…

Taschenbuch. Condition: Neu. nach der Bestellung gedruckt Neuware - Printed after ordering - At some point, every software engineering organisation hits a point where shipping software feels like it's taking longer than writing it. So, developers are waiting days for a database, environments are drifting apart, and every team is deploying in its own way. This book shows you how to do that, one working layer at a time.In this book, you'll get to build a complete internal developer platform using tools you can run on a single Linux workstation. The plan is to provision multi-cluster infrastructure with OpenTofu, wire GitOps delivery with Argo CD, design a self-service component API with Kubebuilder and Crossplane, enforce policy with Kyverno and Cilium, and add observability and a Backstage portal that cuts onboarding from weeks to minutes. Then you'll adopt OpenChoreo and use it with custom component types, promotion pipelines, multi-cluster data planes, and AI agents connected through MCP.Out of the book, about 40% is about the thinking behind it, and the rest is all about putting it into practice. The idea is to make you capable and skilled to design, build, secure, measure and grow a platform that developers will actually use.Key LearningsProvision multi-cluster Kubernetes foundations with OpenTofu modules, gateways, and shared secret stores.Deliver change through GitOps with Argo CD, ApplicationSets, and progressive rollouts.Design single-file component API that hides Kubernetes detail from developers.Provision databases on demand with Crossplane compositions and a custom operator.Enforce security baselines through Kyverno policies, signed images, and zero-trust network rules.Instrument services with OpenTelemetry, and reuse dashboards, SLOs, burn-rate alerts.Speedup onboarding using Backstage templates, catalog entities, and TechDocs.Operate OpenChoreo with custom component types, traits, and promotion pipelines.Run dedicated production data planes across clusters using outbound cluster agents.Grow adoption voluntarily, score platform maturity, and prove ROI to leadership.Table of ContentWhy Platform Engineering ExistsThinking Like a Platform TeamArchitecting Internal Developer PlatformBuilding Foundation LayerGitOps and Delivery PipelinesSelf-Service and Platform APIsGuardrails, Security and GovernanceObservability and Developer PortalsOpenChoreo as Reference OutcomeOperating OpenChoreoScaling Platform AdoptionTarget AudienceIf you know to ship software, and have worked around Git, containers and the Linux command line, then this book is well-suited for you. No prior work with the platform tools is expected, although some knowledge of Kubernetes helps.…

Taschenbuch. Condition: Neu. This item is printed on demand - Print on Demand Titel. Neuware 204 pp. Englisch.

Taschenbuch. Condition: Neu. Unified Observability with OpenObserve | From red flags to root cause across infrastructure, network, application, data and AI layers | Zebb Wright | Taschenbuch | Englisch | 2026 | GitforGits | EAN 9789349174740 | Verantwortliche Person für die EU: Libri GmbH, Europaallee 1, 36244 Bad Hersfeld, gpsr[at]libri[dot]de | Anbieter: preigu Print on Demand. …

Taschenbuch. Condition: Neu. This item is printed on demand - Print on Demand Titel. Neuware -At some point, every software engineering organisation hits a point where shipping software feels like it's taking longer than writing it. So, developers are waiting days for a database, environments are drifting apart, and every team is deploying in its own way. This book shows you how to do that, one working layer at a time.In this book, you'll get to build a complete internal developer platform using tools you can run on a single Linux workstation. The plan is to provision multi-cluster infrastructure with OpenTofu, wire GitOps delivery with Argo CD, design a self-service component API with Kubebuilder and Crossplane, enforce policy with Kyverno and Cilium, and add observability and a Backstage portal that cuts onboarding from weeks to minutes. Then you'll adopt OpenChoreo and use it with custom component types, promotion pipelines, multi-cluster data planes, and AI agents connected through MCP.Out of the book, about 40% is about the thinking behind it, and the rest is all about putting it into practice. The idea is to make you capable and skilled to design, build, secure, measure and grow a platform that developers will actually use.Key LearningsProvision multi-cluster Kubernetes foundations with OpenTofu modules, gateways, and shared secret stores.Deliver change through GitOps with Argo CD, ApplicationSets, and progressive rollouts.Design single-file component API that hides Kubernetes detail from developers.Provision databases on demand with Crossplane compositions and a custom operator.Enforce security baselines through Kyverno policies, signed images, and zero-trust network rules.Instrument services with OpenTelemetry, and reuse dashboards, SLOs, burn-rate alerts.Speedup onboarding using Backstage templates, catalog entities, and TechDocs.Operate OpenChoreo with custom component types, traits, and promotion pipelines.Run dedicated production data planes across clusters using outbound cluster agents.Grow adoption voluntarily, score platform maturity, and prove ROI to leadership.Table of ContentWhy Platform Engineering ExistsThinking Like a Platform TeamArchitecting Internal Developer PlatformBuilding Foundation LayerGitOps and Delivery PipelinesSelf-Service and Platform APIsGuardrails, Security and GovernanceObservability and Developer PortalsOpenChoreo as Reference OutcomeOperating OpenChoreoScaling Platform AdoptionTarget AudienceIf you know to ship software, and have worked around Git, containers and the Linux command line, then this book is well-suited for you. No prior work with the platform tools is expected, although some knowledge of Kubernetes helps. 344 pp. Englisch.…

Taschenbuch. Condition: Neu. Platform Engineering in Practice | Build internal Developer Platform from Empty Clusters to Self-Service Delivery, Observability, and AI-Assisted Operations | Zebb Wright | Taschenbuch | Englisch | 2026 | GitforGits | EAN 9788117136034 | Verantwortliche Person für die EU: Libri GmbH, Europaallee 1, 36244 Bad Hersfeld, gpsr[at]libri[dot]de | Anbieter: preigu Print on Demand.…