Please let us know where or if we need to set $GOPATH and $GOROOT after we clone this repo. If I clone this repo as it is, and cd into any of the directories with cpustat.go or main.go and run the go build as shown on slide 41, it's kicks out all kinds or errors. I really would like to get these go examples going so I can understand this better. Thanks so much for all you work.
![CNCF [Cloud Native Computing Foundation]](http://yt3.ggpht.com/93B7ElGi-TMF2lISQD79p1MVhUf4jVfE8KMyAmVAVUEMp8jvARqS0TtQxelj_odxgmJ_SAYsjg=s48-c-k-c0x00ffffff-no-rj)
Great talk! Thanks very much for building such cool examples!
Very useful. Thanks a lot
Notes for my self:
- build exporter in go : 3:50
Please let us know where or if we need to set $GOPATH and $GOROOT after we clone this repo. If I clone this repo as it is, and cd into any of the directories with cpustat.go or main.go and run the go build as shown on slide 41, it's kicks out all kinds or errors. I really would like to get these go examples going so I can understand this better. Thanks so much for all you work.
Yes you need to set your $GOPATH when yousing go
Title is misleading. Prometheus has nothing to do with this talk. This is a talk about how to put UNIX data into Prometheus format using golang.