97 things every SRE should know : (Record no. 171376)

MARC details
000 -LEADER
fixed length control field 07850nam a22003977a 4500
001 - CONTROL NUMBER
control field 22699554
003 - CONTROL NUMBER IDENTIFIER
control field IIITD
005 - DATE AND TIME OF LATEST TRANSACTION
control field 20230616154457.0
008 - FIXED-LENGTH DATA ELEMENTS--GENERAL INFORMATION
fixed length control field 230616b xxu||||| |||| 00| 0 eng d
010 ## - LIBRARY OF CONGRESS CONTROL NUMBER
LC control number 2022276249
015 ## - NATIONAL BIBLIOGRAPHY NUMBER
National bibliography number GBC0K1553
Source bnb
016 7# - NATIONAL BIBLIOGRAPHIC AGENCY CONTROL NUMBER
Record control number 020047577
Source Uk
020 ## - INTERNATIONAL STANDARD BOOK NUMBER
International Standard Book Number 9789385889516
035 ## - SYSTEM CONTROL NUMBER
System control number (OCoLC)on1156176748
040 ## - CATALOGING SOURCE
Original cataloging agency YDX
Language of cataloging eng
Transcribing agency YDX
Description conventions rda
Modifying agency BDX
-- EXR
-- OCLCO
-- MNW
-- OCLCF
-- EXH
-- UKMGB
-- OCLCO
-- DLC
-- IIITD
042 ## - AUTHENTICATION CODE
Authentication code lccopycat
050 00 - LIBRARY OF CONGRESS CALL NUMBER
Classification number TA169
Item number .N56 2020
082 ## - DEWEY DECIMAL CLASSIFICATION NUMBER
Classification number 620.001
Item number STO-9
245 00 - TITLE STATEMENT
Title 97 things every SRE should know :
Remainder of title collective wisdom from the experts
Statement of responsibility, etc edited by Emil Stolarsky and Jaime Woo
246 3# - VARYING FORM OF TITLE
Title proper/short title Ninety-seven things every Site Reliability Engineer should know
260 ## - PUBLICATION, DISTRIBUTION, ETC. (IMPRINT)
Place of publication, distribution, etc Mumbai :
Name of publisher, distributor, etc O'Reilly,
Date of publication, distribution, etc ©2021
300 ## - PHYSICAL DESCRIPTION
Extent xvii, 231 p. :
Other physical details ill. ;
Dimensions 24 cm.
504 ## - BIBLIOGRAPHY, ETC. NOTE
Bibliography, etc Includes bibliographical references and index.
505 00 - FORMATTED CONTENTS NOTE
Title New to SRE.
-- Site reliability engineering in six words /
Statement of responsibility Alex Hidalgo --
Title Do we know why we really want reliability? /
Statement of responsibility Niall Murphy --
Title Building self-regulating processes /
Statement of responsibility Denise Yu --
Title Four engineers of an SRE seder /
Statement of responsibility Jacob Scott --
Title The reliability stack /
Statement of responsibility Alex Hidalgo --
Title Infrastructure: it's where the power is /
Statement of responsibility Charity Majors --
Title Thinking about resilience /
Statement of responsibility Justin Li --
Title Observability in the development cycle /
Statement of responsibility Charity Majors and Liz Fong-Jones --
Title There is no magic /
Statement of responsibility Bouke van der Bijl --
Title How Wikipedia is served to you /
Statement of responsibility Effie Mouzeli --
Title Why you should understand ( a little) about TCP /
Statement of responsibility Julia Evans --
Title The importance of a management interface /
Statement of responsibility Salim Virji --
Title When it comes to storage, think distributed /
Statement of responsibility Salim Virji --
Title The role of cardinality /
Statement of responsibility Charity Majors and Liz Fong-Jones --
Title Security is like an onion /
Statement of responsibility Lucas Fontes --
Title Use your words /
Statement of responsibility Tanya Reilly --
Title Where to SRE /
Statement of responsibility Fatema Boxwala --
Title Dear future team /
Statement of responsibility Frances Rees --
Title Sustainability and burnout /
Statement of responsibility Denise Yu --
Title Don't take advice from Graybeards /
Statement of responsibility John Looney --
Title Facing that first page /
Statement of responsibility Andrew Louis --
Title Zero to one.
-- SRE, at any size, is cultural /
Statement of responsibility Matthew Huxtable --
Title Everyone is an SRE in a small organization /
Statement of responsibility Matthew Huxtable --
Title Auditing your environment for improvements /
Statement of responsibility Joan O'Callaghan --
Title With incident response, start small /
Statement of responsibility Thai Wood --
Title Solo SRE: effecting large-scale change as a single individual /
Statement of responsibility Ashley Poole --
Title Design goals for SLO measurement /
Statement of responsibility Ben Sigelman --
Title I have an error budget- now what? /
Statement of responsibility Alex Hidalgo --
Title How to change things /
Statement of responsibility Joan O'Callaghan --
Title Methodological debugging /
Statement of responsibility Avishai Ish-Shalom and Nati Cohen --
Title How startups can build an SRE mindset /
Statement of responsibility Tamara Miner --
Title Bootstrapping SRE in Enterprises /
Statement of responsibility Vanessa Yiu --
Title It's okay not to know, and it's okay to be wrong /
Statement of responsibility Todd Palino --
Title Storytelling is a superpower /
Statement of responsibility Anita Clarke --
Title Get your work recognized: write a brag document /
Statement of responsibility Julie Evans and Karla Burnett --
Title One to ten.
-- Making work visible /
Statement of responsibility Lorin Hochstein --
Title An overlooked engineering skill /
Statement of responsibility Murali Suriar --
Title Unpacking the on-call divide /
Statement of responsibility Jason Hand --
Title The maestros of incident response /
Statement of responsibility Andrew Louis --
Title Effortless incident management /
Statement of responsibility Suhail Patel, Miles Bryant, and Chris Evans --
Title If you're doing runbooks, do them well /
Statement of responsibility Spike Lindsey --
Title Why I hate our playbooks /
Statement of responsibility Frances Rees --
Title What machines do well /
Statement of responsibility Michelle Brush --
Title Integrating empathy into SRE tools /
Statement of responsibility Daniella Niyonkuru --
Title Using ChatOps to implement empathy /
Statement of responsibility Daniella Niyonkuru --
Title Move fast to unbreak things /
Statement of responsibility Michelle Brush --
Title You don't know for sure until it runs in production /
Statement of responsibility Ingrid Epure --
Title Sometimes the fix is the problem /
Statement of responsibility Jake Pittis --
Title Legendary /
Statement of responsibility Elise Gale --
Title Metrics are not SLIs (the measure everything trap) /
Statement of responsibility Brian Murphy --
Title When SLOs attack: pathological SLOs and how to fix them /
Statement of responsibility Narayan Desai --
Title Holistic approach to product reliability /
Statement of responsibility Kristine Chen and Bart Ponurkiewicz --
Title In search of the lost time /
Statement of responsibility Ingrid Epure --
Title Unexpected lessons from office hours /
Statement of responsibility Tamara Miner --
Title Building tools for internal customers that they actually want to use /
Statement of responsibility Vinessa Wan --
Title It's about the individuals and interactions /
Statement of responsibility Vinessa Wan --
Title The human baseline in SRE /
Statement of responsibility Effie Mouzeli --
Title Remotely productive or productively remote /
Statement of responsibility Avleen Vig --
Title Of margins and individuals /
Statement of responsibility Kurt Andersen --
Title The importance of margins in systems /
Statement of responsibility Kurt Andersen --
Title Fewer spreadsheets, more napkins /
Statement of responsibility Jacob Bednarz --
Title Sneaking in your DevOps deliciously /
Statement of responsibility Vinessa Wan --
Title Effecting SRE cultural changes in enterprise /
Statement of responsibility Vanessa Yiu --
Title To all the SREs I've loved /
Statement of responsibility Felix Glaser --
Title Complex: the most overloaded word in technology /
Statement of responsibility Laura Nolan --
Title Ten to hundred.
-- The best advice I can give to teams /
Statement of responsibility Nicole Forsgren --
Title Create your supporting artifacts /
Statement of responsibility Daria Barteneva and Eva Parish --
Title The order of operations for getting SLO buy-in /
Statement of responsibility David K. Rensin --
Title Heroes are necessary, but hero culture is not /
Statement of responsibility Lei Lopez --
Title On-call rotations that people want to join /
Statement of responsibility Miles Bryant, Chris Evans, and Suhail Patel --
Title Study of human factors and team culture to improve paper fatigue /
Statement of responsibility Daria Barteneva --
Title Optimize for MTTBTB (mean time to back to bed) /
Statement of responsibility Spike Lindsey --
Title Mitigating and preventing cascading failures /
Statement of responsibility Rita Lu --
Title On-call health: the metric you could be measuring /
Statement of responsibility Caitie McCaffrey --
Title The SRE as a diplomat /
Statement of responsibility Johnny Boursiquot --
Title Test your disaster plan /
Statement of responsibility Tanya Reilly --
Title Why training matters to an SRE practice and SRE matters to your training program /
Statement of responsibility Jennifer Petoff --
Title The power of uniformity /
Statement of responsibility Chris Evans, Suhail Patel, and Miles Bryant --
Title Bytes per user value /
Statement of responsibility Arshia Mufti --
Title Make your engineering blog a priority /
Statement of responsibility Anita Clarke --
Title Don't let anyone run code in your context /
Statement of responsibility John Looney --
Title Trading places: SRE and product /
Statement of responsibility Shubheksha Jalan --
Title You see teams, I see product /
Statement of responsibility Avleen Vig --
Title The performance emergency fund /
Statement of responsibility Dawn Parzych --
Title Important but not urgent: roadmaps for SREs /
Statement of responsibility Laura Nolan --
Title The future of SRE.
-- That 50% thing /
Statement of responsibility Tanya Reilly --
Title Following the path of safety-critical systems /
Statement of responsibility Heidy Khlaaf --
Title The importance of formal specification /
Statement of responsibility Hillel Wayne --
Title Risk and rot in sociotechnical systems /
Statement of responsibility Laura Nolan --
Title SRE in crisis /
Statement of responsibility Niall Murphy --
Title Expected risk limitations /
Statement of responsibility Blake Bisset --
Title Beyond local risk: accounting for Angry Birds /
Statement of responsibility Blake Bisset --
Title A word from software safety nerds /
Statement of responsibility J. Paul Reed --
Title Incidents: a window into Gaps /
Statement of responsibility Lorin Hochstein --
Title The third age of SRE /
Statement of responsibility Björn "Beorn" Rabenstein.
520 ## - SUMMARY, ETC.
Summary, etc "Site reliability engineering (SRE) is more relevant than ever. Knowing how to keep systems reliable has become a critical skill. With this practical book, newcomers and old hats alike will explore a broad range of conversations happening in SRE. You'll get actionable advice on several topics, including how to adopt SRE, why SLOs matter, when you need to upgrade your incident response, and how monitoring and observability differ. Editors Jaime Woo and Emil Stolarsky, co-founders of Incident Labs, have collected 97 concise and useful tips from across the industry, including trusted best practices and new approaches to knotty problems. You'll grow and refine your SRE skills through sound advice and thought-provoking questions that drive the direction of the field."--
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name as entry element Reliability (Engineering)
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name as entry element Engineering
General subdivision Management.
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name as entry element Cyberinfrastructure
General subdivision Management.
650 #0 - SUBJECT ADDED ENTRY--TOPICAL TERM
Topical term or geographic name as entry element Allied operations
700 1# - ADDED ENTRY--PERSONAL NAME
Personal name Stolarsky, Emil
Relator term editor
700 1# - ADDED ENTRY--PERSONAL NAME
Personal name Woo, Jaime
Relator term editor
856 ## - ELECTRONIC LOCATION AND ACCESS
Uniform Resource Identifier <a href="https://www.google.co.in/books/edition/97_Things_Every_SRE_Should_Know/CdwKEAAAQBAJ?hl=en&gbpv=1&dq=97+things+every+SRE+should+know&printsec=frontcover">https://www.google.co.in/books/edition/97_Things_Every_SRE_Should_Know/CdwKEAAAQBAJ?hl=en&gbpv=1&dq=97+things+every+SRE+should+know&printsec=frontcover</a>
906 ## - LOCAL DATA ELEMENT F, LDF (RLIN)
a 7
b cbc
c copycat
d 2
e ncip
f 20
g y-gencatlg
942 ## - ADDED ENTRY ELEMENTS (KOHA)
Source of classification or shelving scheme Dewey Decimal Classification
Koha item type Books
Holdings
Withdrawn status Lost status Source of classification or shelving scheme Damaged status Not for loan Collection code Home library Current library Shelving location Date acquired Bill No. Bill Date Cost, normal purchase price PO No. PO Date Total Checkouts Full call number Barcode Date last seen Cost, replacement price Price effective from Vendor/Supplier Koha item type
    Dewey Decimal Classification     Engineering and Allied Operation IIITD IIITD General Stacks 14/06/2023 TB575 2023-06-08 679.87 IIITD/LIC/BS/2021/03/37 2023-05-08   620.001 STO-9 012038 16/06/2023 925.00 16/06/2023 Technical Bureau India Pvt. Ltd. Books
© 2024 IIIT-Delhi, library@iiitd.ac.in