<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SIG Instrumentation on Kubernetes Contributors</title><link>https://deploy-preview-846--kubernetes-contributor.netlify.app/community/community-groups/sigs/instrumentation/</link><description>Recent content in SIG Instrumentation on Kubernetes Contributors</description><generator>Hugo</generator><language>en</language><atom:link href="https://deploy-preview-846--kubernetes-contributor.netlify.app/community/community-groups/sigs/instrumentation/index.xml" rel="self" type="application/rss+xml"/><item><title>SIG Instrumentation Charter</title><link>https://deploy-preview-846--kubernetes-contributor.netlify.app/community/community-groups/sigs/instrumentation/charter/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deploy-preview-846--kubernetes-contributor.netlify.app/community/community-groups/sigs/instrumentation/charter/</guid><description>&lt;h2 id="scope">Scope&lt;/h2>
&lt;p>Owns best practices for cluster observability through metrics, logging, events,
and traces across all Kubernetes components and development of components
required for all Kubernetes clusters (eg. klog, kube-state-metrics).&lt;/p>
&lt;h3 id="in-scope">In scope&lt;/h3>
&lt;p>SIG-Instrumentation revolves around the process of instrumenting and exposing
observability signals.&lt;/p>
&lt;p>The act of instrumenting components not owned by SIG-Instrumentation is out of
scope, however SIG-Instrumentation is there to advise any contributors with
instrumentation decisions.&lt;/p>
&lt;p>As well as giving advice in regards to instrumentation, SIG-Instrumentation
coordinates metric requirements of different SIGs for other components through
finding common APIs (such as the resource/core, custom and external metrics
APIs).&lt;/p></description></item></channel></rss>