in reply to Parsing a really, REALLY big MRTG config

For a long-term plan, you should consider upgrading the MRTG system to cacti.

Cacti stores the MRTG config info in a MySQL database.

Although the learning-curve for cacti is fairly steep, your MRTG background should help considerably. You will gain scalibility, efficiency, tons of features, and end-user friendliness.

     "An undefined problem has an infinite number of solutions." - Robert A. Humphrey         "If you're not part of the solution, you're part of the precipitate." - Henry J. Tillman

  • Comment on Re: Parsing a really, REALLY big MRTG config

Replies are listed 'Best First'.
Re^2: Parsing a really, REALLY big MRTG config
by Hercynium (Hermit) on Jun 09, 2007 at 00:34 UTC
    Thanks for the cacti suggestion... I tried rolling it out and it was immediately rejected by everyone who used it. Really, I think it was one of those odd, NIH-sort-of things, telco engineers being afraid of something they don't already know.

    Luckily for me... I just need to make this system work for one more quarter... and we'll be rolling out a brand-new polling solution company-wide that should banish MRTG forever. Hence my reluctance to re-write the current system! :)
[reply]

In Section Seekers of Perl Wisdom