About Rootconf 2018 and who should attend:
Rootconf is India’s best conference on DevOps, SRE and IT infrastructure. Rootconf attracts systems and operations engineers to share real-world knowledge about building reliable systems.
The 2018 edition is a single track conference. Day 1 – 10 May – features talks on security. Colin Charles (chief evangelist at Percona Foundation), Pukhraj Singh (former national cybersecurity manager at UIDAI), Shamim Reza (open source enthusiast), Alisha Gurung (network engineer at Bhutan Telecom) and Derick Thomas (former network engineer at VSNL and Airtel Bharti) will touch on important aspects of infrastructure, database, network and enterprise security.
Day 2 – 11 May – is filled with case studies and stories about legacy code, immutable infrastructure, root-cause analysis, handling dependencies and monitoring. Talks from Exotel, Kayako, Intuit, Helpshift, Digital Ocean, among others, will help you evaluate DevOps tools and architecture patterns.
If you are a:
- DevOps programmer
- Systems engineer
- VP of engineering
- IT manager
you should attend Rootconf.
Birds Of Feather (BOF) sessions at Rootconf 2018 will cover the following topics:
- DevSec Ops
- Microservices - tooling, architecture, costs and culture
- Mistakes that startups make when planning infrastructure
- Handling technical debt
- How to plan a container strategy for your organization
- Evaluating AWS for scale
- Future of DevOps
Rootconf is a conference for practitioners, by practitioners.
The call for proposals is closed. If you are interested in speaking at Rootconf events in 2018, submit a proposal here: rootconf.talkfunnel.com/rootconf-round-the-year-2018/
NIMHANS Convention Centre, Lakkasandra, Hombegowda Nagar, Bengaluru, Karnataka 560029.
Schedule, event details and tickets: https://rootconf.in/2018
For more information about Rootconf, sponsorships, outstation events, contact email@example.com or call 7676332020.
Prometheus: Introduction, Design and Philosophy
Prometheus is an opinionated monitoring system that chooses to do a lot of things differently from traditional monitoring systems. This leads to a culture clash for those used to other approaches, and raises questions as to why we didn’t take a seemingly better approach. This talk focuses on the “why” behind many of the design decisions that are core to Prometheus, including pull vs. push, the dimensional data model, relabeling, per-process exporters, stateful client libraries, as well as aspects like metric naming conventions and having a non-distributed storage as a design goal.
This talk is an updated version of the talk by Julius, the co-founder of Prometheus given at Promcon.
- Introduce prometheus
- The datamodel
- Query Language
- Pull vs Push
- Alternatives and Workarounds
- A couple more concepts
- Remote Storage
Goutham is a student and a developer from India. His enthusiasm for Ops got him an internship on the infra team of a large company where he worked on Production infrastructure and built the company’s monitoring system on top of Prometheus.
That was his first encounter with production systems and Prometheus, and this summer, he started contributing to Prometheus and interned with CoreOS, working on Prometheus’ new storage engine. He is now a maintainer for Prometheus with a focus on TSDB, the storage engine powering it.