<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<oembed>
  <author_name>kwbtblog</author_name>
  <author_url>https://blog.hatena.ne.jp/kwbtblog/</author_url>
  <blog_title>Welcome to new things</blog_title>
  <blog_url>https://www.ekwbtblog.com/</blog_url>
  <categories>
    <anon>Cloud Monitoring</anon>
    <anon>GCP</anon>
    <anon>Go</anon>
    <anon>Go Language</anon>
    <anon>Golang</anon>
    <anon>Google Cloud Platform</anon>
    <anon>Gothin (e.g. Gortin)</anon>
    <anon>goroutine</anon>
  </categories>
  <description>Goroutine Leak The Go language is a fascinating language because it is so easy to create goroutines (like threads). However, since the goroutine is executed separately from the main flow, it was unnoticed when the goroutine process stopped midway due to a deadlock, etc. &quot;I thought it had finished, b…</description>
  <height>190</height>
  <html>&lt;iframe src=&quot;https://hatenablog-parts.com/embed?url=https%3A%2F%2Fwww.ekwbtblog.com%2Fentry%2F2020%2F07%2F22%2F235648&quot; title=&quot;Using GCP to monitor goroutine leaks in the Go language as effortlessly as possible - Welcome to new things&quot; class=&quot;embed-card embed-blogcard&quot; scrolling=&quot;no&quot; frameborder=&quot;0&quot; style=&quot;display: block; width: 100%; height: 190px; max-width: 500px; margin: 10px 0px;&quot;&gt;&lt;/iframe&gt;</html>
  <image_url>https://cdn-ak.f.st-hatena.com/images/fotolife/k/kwbtblog/20200722/20200722112037.png</image_url>
  <provider_name>Hatena Blog</provider_name>
  <provider_url>https://hatena.blog</provider_url>
  <published>2020-07-22 23:56:48</published>
  <title>Using GCP to monitor goroutine leaks in the Go language as effortlessly as possible</title>
  <type>rich</type>
  <url>https://www.ekwbtblog.com/entry/2020/07/22/235648</url>
  <version>1.0</version>
  <width>100%</width>
</oembed>
