cacti

Compare this with Nagios or Cacti where you have to configure checks/graph collection for each thing you care about.

This is how cacti work; the needles slow surrounding air to reduce moisture loss through convective evaporation.

Graphite + Grafana are like Cacti or Munin, but orders of magnitude smarter and more powerful.

Similarly, the acceptable plurals of cactus are cactuses, cacti, or (los) cactus (pronounced as in Spanish).

I prefer Munin over Cacti because Munin's config is in simple text-based config files which can be scripted.

Are any of these charting solutions being actively used in a cacti-like application?

Combine with the Cacti pull model, and I think a wait-and-see attitude is the best for this for now.

Fly-by comment: C4 is very similar to CAM, the scheme that cacti use.

We dug deep with tools like cacti and ended up being able to point only at the 'unknowns' of the shared resources and EBS.

With Cloudwatch I don't have to manage munin, cacti, and a server to run them on.

I had nagios, cacti, munin, graphite all running and had two ops guys pretty much 80% of their time managing it.

All the cacti will die, but there won't be many mudslides.

There are tons of old programs based on PHP and Cacti, etc.

Cacti, ganglia, and so forth are useful adjuncts for routers, clusters, and the like.

Cacti for network traffic monitoring (and alerting using thold plugin).