statistics

Visualize is a Views style plug-in for implementing the jQuery Visualize charting tool.

jQuery Visualize provides accessible charts providing textual information to non-visual users.
It uses a technique with JavaScript to scrape data from an HTML table and generate charts using the HTML 5 Canvas element.

Try out a demo: http://lakeandweb.com/visualize/

For a drupal.org's list ordered by popularity, that is by usage statistics in descending order, see: Taxonomy modules. Currently, there are 218 contributed modules related to the core Taxonomy module, 134 of them with a Drupal 6.x version available.

As posted by Dries today, indeed.com tell us that Drupal jobs are on the rise and are outpacing Joomla and Wordpress by a massive margin. Yes, you are indeed in the right user group. This highlights why a DrupalCamp is so badly needed. Remember that we will be discussing holding a future DrupalCamp tomorrow night at the monthly DUG meet-up.

I was thinking about trying to monitor several Drupal metrics using Cacti and went looking for someone who's done it before. Doesn't seem so, but I would have thought monitoring statistics on your site(s) is an essential part of any high performance setup so bring it up here.

Anyhow - found something similar only and added a comment over on a thread about monitoring Drupal:

http://groups.drupal.org/node/20271#comment-74657

Anyone here interested in such an effort and how it might be built?

If your server has high load you may consider following approach:
1. Use logs of server (i.e. Apache) + awstats updated by cron.
2. run awstats to parse log on another server or nightly when no load.
3. Apache work slower with logging. I prefer to log only php,html - content, no jpg,css,js etc.
4. Why Apache? nginx works much faster. nginx + php-fpm + e-accelerator 2-3 times faster and don't use so much memory like apache.

eaccelerator.shm_size="16" - you may consider to add some memory here
eaccelerator.compress="1" - there is no need if you use gzip/deflate in apache.

Any comments about OpenDNS?

OpenDNS
http://www.opendns.com/

About OpenDNS
http://www.opendns.com/about/overview/

OpenDNS Solutions
http://www.opendns.com/solutions/overview/

OpenDNS Customers
http://www.opendns.com/customers/featured/

Hello all,
Drupal already has its own statistic system that grabs the number of installation that uses a determined module (here you can see an example: http://drupal.org/project/usage/blocks404).
There's more we can do to make statistics useful. It could be useful to understand the number of users are using a determined feature inside a module, and how are they using this.

Examples:

The module creates statistics with aggregated data. The data will be stored in a new table, which will be updated with a cron run. This statistic module provides statistical results of nodes, comments and users. Those results will be stored even if the access-log or the watchdog table have been deleted. For the presentation the data views and charts module are used. The Drupal core statistics module is used for the raw data (actually it is required for statspro).

I thought you guys might be interested in these search numbers from DrupalModules.com. It turns out they're very similar to what's being reported by Drupal.org. One thing to note, my data has been filtered for IP-uniqueness to prevent result spamming (intentional, or not), the Drupal.org data is just coming right out of the watchdog log unfiltered.

Not everyone I know is on the Drupal development mailing list so I thought I'd pass along this interesting bit of research that webchick compiled. It's a number of Drupal statistics including number of active installations, most popular modules, number of Drupal downloads, etc.

Read it here.