Skip to content

Instantly share code, notes, and snippets.

@metalmatze

metalmatze/devsummit.md

Last active December 4, 2019 17:00
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save metalmatze/a68db3addb66224355b4789b27ae6a6a to your computer and use it in GitHub Desktop.
Save metalmatze/a68db3addb66224355b4789b27ae6a6a to your computer and use it in GitHub Desktop.
Download ZIP
Prometheus 2019 Dev Summit 2 Summary
Raw
devsummit.md

Doc: https://docs.google.com/document/d/1VVxx9DzpJPDgOZpZ5TtSHBRPuG5Fr3Vr6EFh8XuUpgs/edit#

PromCon NA

  • Vancouver in Q2
  • ~500 is fine, need to be <1k.
  • Keep it low price for attendees
  • We want to try to have a onboarding/workshop day before and then ramp up over the two days

PrometheusDay

  • Let CNCF organise a PrometheusDay in India

ServiceDiscovery Moratorium

  • Lift moratorium
  • New SD has to have maintainer with push access (ie, on -team)

Tracing

  • Prometheus will out of the box do Jaeger for now as that solves -team need, mark EXPERIMENTAL, re-eval as per above consensus
  • Wait until next DevSummit for OpenTelemtry to settle

Stale Bot

  • We should have a bot mark PRs as stale, all repos, 60 days.

TL;DR

  • Style Guide for PromQL
  • head block memory improvements
  • looking into further new/old chunk encodings
  • streamable compaction
  • lsp (at least give people a teaser for the next meeting)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment