article thumbnail

Site reliability engineering: 5 things you need to know

Dynatrace

The term “site reliability engineering” was coined in 2003 by Google VP of Engineering Ben Sloss , who famously noted on his LinkedIn profile that “if Google ever stops working, it’s my fault.” This can be anything from adjusting monitoring and alerting to making code changes in production.

article thumbnail

Site reliability engineering: 5 things to you need to know

Dynatrace

The term “site reliability engineering” was coined in 2003 by Google VP of Engineering Ben Sloss , who famously noted on his LinkedIn profile that “if Google ever stops working, it’s my fault.” This can be anything from adjusting monitoring and alerting to making code changes in production.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

HammerDB v4.7 New Features Pt 2: Example CLI Scripts

HammerDB

Copyright (C) 2003-2023 Steve Shaw Type "help" for a list of commands Initialized SQLite on-disk database /home/steve/HammerDB-4.7/TMP/hammer.DB Copyright (C) 2003-2023 Steve Shaw Type "help" for a list of commands Initialized SQLite on-disk database /home/steve/HammerDB-4.7/TMP/hammer.DB Copy Code Copied Use a different Browser $./scripts/tcl/maria/tprocc/maria_tprocc.sh

C++ 83
article thumbnail

What is a Site Reliability Engineer (SRE)?

Dotcom-Montior

The term site reliability engineering first came into existence at Google in 2003 when a site reliability team was created. Monitoring. He was asked in 2003 to create and manage a team of seven engineers which eventually led him to create the new role/title. At that time, the team was made up of software engineers. Availability.

article thumbnail

HammerDB v4.6 New Features Pt1: Python CLI Interface

HammerDB

Copyright (C) 2003-2022 Steve Shaw. Copyright (C) 2003-2022 Steve Shaw. Therefore, although on both Linux and Windows, you will see Python as the top process in performance monitoring tools when running the workload. /hammerdbcli py HammerDB CLI v4.6. Type "help()" for a list of commands. Use a different Browser.

article thumbnail

HammerDB v4.6 New Features Pt2: Jobs Interface

HammerDB

Copyright (C) 2003-2022 Steve Shaw Type "help" for a list of commands Initialized new SQLite on-disk database C:/Users/Hdb/AppData/Local/Temp/hammer.DB Copyright (C) 2003-2022 Steve Shaw Type "help" for a list of commands Initialized new SQLite on-disk database C:/Users/Hdb/AppData/Local/Temp/hammer.DB Use a different Browser.

article thumbnail

HammerDB v4.1 New Features Pt3: Step Workloads

HammerDB

When taking this approach you would not focus on the test result but instead monitor the databases ability to cope with the variation in demand and transaction response times. This is because Virtual User 1 is the monitor Virtual User but this Virtual User does not run in the replica meaning it ends immediately. Step Workloads.