Google Site Reliability Engineering Reviews

Looker Reviews

Google Site Reliability Engineering mentions (84)

• Ask HN: What makes SRE great compared to "plain" DevOps?

  In my view it is having a dedicated team focusing their full mental bandwidth on pro-actively understanding and managing robustness of the system. In Pure DevOps, it seems to me developers often don't have the full picture of the system, and not enough bandwidth to foresee complex interactions from their changes. These are from my experiences spending one year as a developer in somewhat large a greenfield... - Source: Hacker News / 7 months ago

• How Site Reliability Engineering Is Different From DevOps

  Site Reliability Engineering, introduced by Google, extends the principles of software engineering to operations. Unlike DevOps, SRE places a stronger emphasis on reliability, availability, and scalability. SRE teams are tasked with maintaining the health and performance of systems by applying engineering practices to operations. The ultimate objective is to achieve a balance between service reliability and... Source: 9 months ago

• API Product Managers, what's your workflow when designing and maintaining an API?

  Define SLOs for availability and latency. Google's SRE book is good reading for this. Source: 12 months ago

• Starting an SRE position soon. No prior experience (except IT). Any suggestions? Sorry if it's too general.

  Have you gone through the SRE Books? Source: about 1 year ago

• Starting up with sre

  Google SRE books is always a good read. Source: about 1 year ago

Looker mentions (14)

• edit home page to add folder section

  Then in the "foldername" you can have 5 folders, each one for each of the groups. This means that when group1 enters looker.com, his default page will be the "foldername", which contains group1folder (he cannot see the rest of the folders if you have set the permissions correctly for each folder). Source: about 1 year ago

• Stars, tables, and activities: How do we model the real world?

  Even if you want to make Wide Tables, combining fact and dimensions is often the easiest way to create them, so why not make them available? Looker, for example, is well suited to dimensional models because it takes care of the joins that can make Kimball warehouses hard to navigate for business users. - Source: dev.to / over 1 year ago

• dbt for Data Quality Testing & Alerting at FINN

  We take daily snapshots of test results, aggregate them, and send Looker dashboards to the appropriate teams. - Source: dev.to / about 2 years ago

• I'm a dev ID 10 T please help me

  Dashboard: I like to use Datastudio because it's easy (just like using google sheets), but you can also try out Looker. Source: over 2 years ago

• The Data Stack Journey: Lessons from Architecting Stacks at Heroku and Mattermost

  For Growth and larger, I would recommend Looker. The only reason I wouldn't recommend it for the smaller company stages is that the cost is much higher than alternatives such as Metabase. With Looker, you define your data model in LookML, which Looker then uses to provide a drag-and-drop interface for end-users that enables them to build their own visualizations without needing to write SQL. This lets your... - Source: dev.to / over 2 years ago