Skip to content

Latest commit

 

History

History
41 lines (35 loc) · 2.91 KB

sink-owners.md

File metadata and controls

41 lines (35 loc) · 2.91 KB

Sink Owners

Each sink in Heapster needs to have at least one "owner". The owner will be responsible for doing code reviews of pull requests regarding their sink, and will be a point of contact for issues relating to their sink.

Owners will not be responsible for actually triaging issues and pull requests, but once assigned, they will be responsible for responding to the issues.

PRs affecting a particular sink generally need to be approved by the sink owner. Similarly, PRs affecting a particular sink that have LGTM from the sink owner will be considered ok-to-merge by the Heapster maintainers (i.e. sink owners will not have official merge permissions, but the maintainer's role in this case is just to perform the actual merge).

List of Owners

  • 🆗 : has owners
  • 🆘 : needs owners, will eventually be deprecated and removed without owners
  • 🆕 : in development
  • ⛔ : deprecated, pending removal
Sink Metric Event Owner(s) Status
ElasticSearch ✔️ ✔️ @AlmogBaku / @andyxning / @huangyuqi 🆗
GCM ✔️ @kubernetes/heapster-maintainers 🆗
Stackdriver ✔️ @kubernetes/heapster-maintainers 🆗
Hawkular ✔️ @burmanm / @mwringe 🆗
InfluxDB ✔️ ✔️ @kubernetes/heapster-maintainers / @andyxning 🆗
Metric (memory) ✔️ @kubernetes/heapster-maintainers 🆗
Kafka ✔️ ✔️ @miaoyq / @Kokan 🆗
OpenTSDB ✔️ @bluebreezecf 🆗
Riemann ✔️ ✔️ @jamtur01 @mcorbin 🆗
Graphite ✔️ @jsoriano / @theairkit 🆕 #1341
Wavefront ✔️ @ezeev 🆗
Librato ✔️ @johanneswuerbach 🆗
Honeycomb ✔️ ✔️ @emfree 🆕 #1762
StatsD ✔️ @yogeswaran 🆗