{
  "@context":[
    "https://www.w3.org/ns/activitystreams",
    {"Hashtag":"as:Hashtag"}
  ],
  "published":"2022-12-07T18:18:11.743Z",
  "attributedTo":"https://k.matthias.org/actors/relistan",
  "to":["https://www.w3.org/ns/activitystreams#Public"],
  "cc":["https://k.matthias.org/actors/relistan/followers"],
  "content":"<p>We wanted to have a service that would optionally tail logs from <a href=\"https://k.matthias.org/tags/Kubernetes\" class=\"hashtag\" rel=\"tag\">#Kubernetes</a> for apps we deploy and report them over UDP syslog&mdash;in an existing JSON log format that we use from <a href=\"https://k.matthias.org/tags/Mesos\" class=\"hashtag\" rel=\"tag\">#Mesos</a>.</p><ul><li>It should make the log scrape/relay decision based on Annotations on the Pods.</li><li>It should rate limit by *pod* and not by host/node so that we don't overrun our log provider (e.g. when someone forgets to turn of debug logging) or starve other apps on the same node from being able to send their logs.</li><li>It should report rate limiting to our metrics system so we can track which pods are getting limited.</li></ul><p>There was nothing that we could find that was able to do all of that. So I spent the last two days writing it in <a href=\"https://k.matthias.org/tags/Golang\" class=\"hashtag\" rel=\"tag\">#Golang</a> and we're doing initial deployment of that as a DaemonSet. Seems to work nicely &#127881;</p>",
  "mediaType":"text/html",
  "attachment":[],
  "tag":[
      {"type":"Hashtag","name":"#Kubernetes","href":"https://k.matthias.org/tags/Kubernetes"},
      {"type":"Hashtag","name":"#Mesos","href":"https://k.matthias.org/tags/Mesos"},
      {"type":"Hashtag","name":"#Golang","href":"https://k.matthias.org/tags/Golang"}
  ],
  "type":"Note",
  "id":"https://k.matthias.org/objects/O-f7qLShCn0"
}