Announcement

Collapse
No announcement yet.

Google Opens Patches For "METRICFS" That They Have Used Since 2012 For Telemetry Data

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Google Opens Patches For "METRICFS" That They Have Used Since 2012 For Telemetry Data

    Phoronix: Google Opens Patches For "METRICFS" That They Have Used Since 2012 For Telemetry Data

    The METRICFS file-system has been in use internally at Google since 2012 for exporting system statistics to their telemetry systems with around 200 statistics being exported per machine. They are now posting the METRICFS patches as open-source for review and possible upstreaming...

    http://www.phoronix.com/scan.php?pag...ource-METRICFS

  • #2

    Comment


    • #3
      I.e: Google wants to upstream their private work, trying to shoehorn it as a standard because it exists for longer, reduce their own burden to maintain it instead of allowing an open from beginning code from RH becoming the standard and Google would have to deal with their legacy 😒

      Comment


      • #4
        Canonical: Heavy breathing.

        Comment


        • #5
          So Google made this thing 8 years ago and now they suddenly want to "open it up to the community",

          What, does the advantage of leaving it in-house close no longer exist? -- and now the advantage is to reduce maintenance costs or prevent a competitor from standardizing a new system that differs from theirs?

          These days with Chrome tracking you up the wazoo, Google in bed with China there's not much they are doing that is interesting or trustworthy anymore, especially after creating Echo chambers and soaking up advertising money while trying to sway political elections to reinforce their own monopoly and continue to dismantle and consume competitors as seen in their Congress hearings with other Tech Giants sweating like they were in the sauna while being grilled alive.

          Comment


          • #6
            hm,, this might make monitoring of linux machines even easier. i wonder what sorts of metrics are exposed and can they be extended to cover e.g. containers.

            Comment


            • #7
              Originally posted by yoshi314 View Post
              hm,, this might make monitoring of linux machines even easier. i wonder what sorts of metrics are exposed and can they be extended to cover e.g. containers.
              Doesn't Netdata and Prometheus cover that pretty well already? Both are quite capable of gathering system metrics and doing so with low overhead afaik. For containers, there's googles cadvisor (https://github.com/google/cadvisor), which you can collect stats from to Prometheus .

              Comment


              • #8
                Originally posted by polarathene View Post

                Doesn't Netdata and Prometheus cover that pretty well already? Both are quite capable of gathering system metrics and doing so with low overhead afaik. For containers, there's googles cadvisor (https://github.com/google/cadvisor), which you can collect stats from to Prometheus .
                yes, but prometheus pulls data from exposed metric endpoints. and this might offer a more lightweight way to get at them. the less middlemen the better.

                Comment


                • #9
                  Originally posted by bachchain View Post
                  two of the big ones....do you offer beer aswell?

                  Comment


                  • #10
                    In some ways I'm thinking "oh that's nice, maybe now that we know how this all works, we can take off our tin-foil hats" but then I realized "Google probably isn't using the same code internally".

                    Not that I care anyway. Google can go ahead and collect my data, as long as it doesn't make my life worse.

                    Comment

                    Working...
                    X