<brixen>
goyox86_, |jemc|: playing around with the influxdb-grafana container on my DO droplet, thanks for building that!
<|jemc|>
brixen: happy to contribute
<|jemc|>
I think the future of rubinius is bright, and want to do my part to get it there
<brixen>
thank you!
<|jemc|>
responding to your email now, btw
<brixen>
it's kinda crazy how difficult it still is to distribute stuff
<brixen>
sweet, thanks
<brixen>
I think we can leverage Docker a great deal
<|jemc|>
the grafana docker container never got to where I wanted to to be
<|jemc|>
it still is not self-contained enough
<brixen>
was going to play with an Atom plugin but went down the Docker rabbit hole...
<brixen>
"I'll just try this on OS X... oh, maybe my droplet..." 2 hrs later heh
<|jemc|>
the need for the js code in the browser to connect back to the docker container is the biggest problem
<|jemc|>
something rendered server-side would be better in this regard
<brixen>
hmm
<brixen>
yeah, I think static html rendered server side would be good
<|jemc|>
I thought goyox86 was looking into a couple other options with that in mind, but hadn't talked about it with him since
<brixen>
there's a ton of room for improvement, of course
<brixen>
pretty sure I have a "Systems as a Service" post in the near future :)
<brixen>
need to draw some contours and start filling in the pieces
<brixen>
unfortunately, every SaaS thing I see is basically, "pay us to run our code on our servers"
<yorickpeterse>
Rubinius as a service
<brixen>
which is really missing the boat
<brixen>
why should I need an account with NewRelic or Skylight or anything like this
<yorickpeterse>
Just think of the marketing: "Featuring a cloud based Just In Time Compiler"
<brixen>
at most I should be able to grab a token from an account provider, use that token to use a service (eg render my metrics data) and be on my way
<yorickpeterse>
brixen: well, convenience is the biggest reason
<yorickpeterse>
e.g. we ran our own stack for metrics and all that (logstash, kibana and some custom stuff) but it's a total pain to _also_ maintain that
<brixen>
it's not convenient to need a separate account for all this stuff when I could just get tokens from one account
<yorickpeterse>
oh true, it would be nice if it was unified
<brixen>
yep, that's my point about systems as a service
<brixen>
it *shouldn't* be a pain to maintain all that stuff
<brixen>
that's what I should be able to pay for, for a few fractions of a cent / hour, etc
<yorickpeterse>
It's not just the technical stuff, it's also part psychological
<yorickpeterse>
e.g. I don't want to even think of having to maintain an ElasticCache cluster, even if it were 100% bulletproof
<brixen>
"I want to store my statsd metrics" and later "I want to render my statsd metrics"
<brixen>
I should be able to compose those programmatically
<brixen>
it goes deeper than convenience, too
<yorickpeterse>
What I would like is some metrics app that goes beyond the initial 10%
<brixen>
witness Skylight's supposedly MRI-specific agent (depends on some C-API crap)
<yorickpeterse>
New Relic is nice, but it abstracts things far too much
<brixen>
it's the idea that a coherent service needs some sort of end-to-end thing (including an account with them)
<cpuguy83>
Boo, the only way to get grafana is from an unencrpyted s3?
<brixen>
cpuguy83: that seems weird
<brixen>
they aren't on github?
<cpuguy83>
Well, other than GH
mbj has quit [Ping timeout: 256 seconds]
<yorickpeterse>
brixen: well, with Rbx you could solve this by basically dumping the metrics in JSON somewhere on a webserver, then just point a local docker thing to it
havenwood has quit []
<yorickpeterse>
That way you only need to have a webserver (perhaps with some authentication), but chances are that's already present
<brixen>
yorickpeterse: yep
<brixen>
we're building out some of those pieces
<brixen>
the instrumentation bytecode are the next big component
<yorickpeterse>
this is actually what I did for a while: have a local version of Kibana running and point it straight to our elasticsearch server
<brixen>
rendering the NewRelic or Skylight generic one-size-never-works approach obsolete
<yorickpeterse>
brixen: not entirely
<yorickpeterse>
One of the nice features is that you can attach custom metrics, or visualize them over time, something Rbx can't do atm
mbj has joined #rubinius
<yorickpeterse>
errr custom metadata
<brixen>
it's not implemented yet but will be soon
RageLtMan has joined #rubinius
goyox86 has joined #rubinius
goyox86_ has quit [Ping timeout: 252 seconds]
elia has quit [Quit: Computer has gone to sleep.]
<goyox86>
brixen I love RBX, as <|jemc|> says RBX future is bright :)
diegoviola has quit [Read error: Connection reset by peer]
diegovio1 has joined #rubinius
mbj has quit [Ping timeout: 264 seconds]
Bwild has joined #rubinius
diegovio1 has quit [Quit: WeeChat 1.0.1]
slaught has joined #rubinius
goyox86 has quit [Quit: My Mac has gone to sleep. ZZZzzz…]