Graphite integration

[Jeff Goldschrafe]

Hi there!

After a tiny bit of sorting out some warts, I've gotten ESxSNMP running and successfully polling the switches in our environment and dumping their metrics into the directory we've specified. However, based on the documentation and a cursory read of the graphite_store.py file, I'm still a bit clueless about how to get the metrics pumped into Graphite for dashboarding. Can anyone provide me a 30-second rundown of the steps that are involved? I'll gladly contribute back to the documentation.

Thanks!

[Ryan Landry]

hi. i'm in the same boat.

i've done well enough to get the data into tsdb. i'm struggling going thru the documentation for the tsdb -> newdb -> graphite piece. unfortunately it is left as "needing to be fleshed out" in the doc.

any tips or advice from your experiences?

thank you kindly in advance.

ryan

[Jeff Goldschrafe]

This isn't much help, but I actually gave up and just ended up using the SNMP plugin in collectd, which feels more idiomatic for what we're trying to do.

--
You received this message because you are subscribed to the Google Groups "esxsnmp" group.

To view this discussion on the web visit https://groups.google.com/d/msg/esxsnmp/-/XtyXvzoJoUEJ.

To post to this group, send email to esx...@googlegroups.com.
To unsubscribe from this group, send email to esxsnmp+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/esxsnmp?hl=en.

[Jon Dugan]

On Thu, Sep 27, 2012 at 2:59 PM, Ryan Landry <ryan....@gmail.com> wrote:
> hi. i'm in the same boat.

Apparently I missed Jeff's email in July. My apologies. I am the
primary author of ESxSNMP.

> i've done well enough to get the data into tsdb. i'm struggling going thru
> the documentation for the tsdb -> newdb -> graphite piece. unfortunately it
> is left as "needing to be fleshed out" in the doc.

Yeah, I keep hoping to get to the docs but you know how things go...

> any tips or advice from your experiences?

There are a few custom changes to Graphite, plus an implementation of
the Graphite Finder class that knows how to speak to newdb.

The Graphite changes that we run in production at ESnet are here:

https://github.com/esnet/graphite-web/tree/esnet_tweaks

The Finder class isn't published anywhere public. I have one other
person who is interested in it as well. I will work on making it
available this afternoon. If you don't see it by the end of the week,
ping me again.

[ryanL]

Mr. Dugan, thank you for replying! You can probably ignore the direct email I sent you from my work address, unless you have more advice you can offer there, too.

Cheers,

Ryan

--
You received this message because you are subscribed to the Google Groups "esxsnmp" group.

[Jon Dugan]

Ah, good. It made it through Google groups this time! And feel free
to call me Jon.

[Ryan Landry]

Thanks again, Jon.

I'm still a bit stuck on the newdb operation. newdb isn't in the bin folder, but is in the src/python/esxsnmp folder. Was this supposed to be a part of the bootstrapping process and I messed something up?

As it is, per the guide, when I run bin/esdbd -f /etc/esxsnmp.cfg it complains that -f is a bad IP address. If I place esxsnmp.cfg in $esxsnmp directory and just run bin/esdbd it seems to open an interface on 8080, even though the config file says 9090.

However, the docs then discuss that esdbd is deprecated and replaced by newdb. Hence my stuck state.

I think once I get this API up to tsdb I'll be (almost) off to the races.

Appreciate your time here.

Ryan

[Ryan Landry]

It looks like I got it working. esdbd seems to call newdb in some manner. Running newdb directly didn't work unless i changed postgres to postgresql in the config file, but then i had problems beyond that getting any of the uri structure to work properly. So, i changed it back, and ran esdbd, which successfully exposes tsdb for me. Success!

[Jon Dugan]

On Fri, Sep 28, 2012 at 3:27 PM, Ryan Landry <ryan....@gmail.com> wrote:
> It looks like I got it working. esdbd seems to call newdb in some manner.

Yes, newdb.py is really not so new anymore and should get renamed to
reflect that it is the current main database layer for ESxSNMP. This
is getting cleaned up in the mongodb-integration branch.

> Running newdb directly didn't work unless i changed postgres to postgresql
> in the config file, but then i had problems beyond that getting any of the
> uri structure to work properly.

Hmm, the name change from postgres to postgresql sounds like it might
be due to a newer version of sqlalchemy. I have sqlalchemy 0.7.3
installed on my production instance. What version do you have
installed?

> So, i changed it back, and ran esdbd, which successfully exposes tsdb for me. Success!

OK. Glad to hear it is working. I'm not sure I follow what you did
to make it work. You are able to get get data via the REST API now?

In my deployment I am running esdb using mod_wsgi in Apache. I have
attached an excerpt from my Apache config and the corresponding
esdb_wsgi script. You'll need to adjust paths to reflect where you
have things installed. You don't necessarily need the exact same
versions of the packages shown in esdb_wsgi script.

Let me know if that helps or leads to more questions.

I'm working on packaging up the stuff I'm using to connect ESxSNMP to
Graphite and hopefully I can send it out later tonight.

Jon