Extend and customize Drupal functionality with contributed modules.
If a module doesn't quite do what you want it to do, if you find a bug or have a suggestion, then join forces and help the module maintainer. Or, share your own by starting a new module.
This module logs system events to a file, as a tiny and lightweight replacement option for watchdog (dblog for Drupal 6) module. It is intended for using in situations when the site is highly loaded and even disabling DB logging activity can slightly help, or you want a dedicated log file for events on site, different from a system log.
Among the Rawlog features:
Log file path/name changing. You may specify a path and name for your log file. If file not exists, it will be created.
Severity level filtering. If you having lots of activity on site, you can record only errors not notices etc.
Tags. If you set the severity level high to record errors only, but you want to keep track of operations like delete, you may add a "delete" tag so events having it will be logged disregarding of severity. Negative Tags were added as discussed in #814148: Negative Tags.
File format. You may change the log file format to show full events info on multiple lines or stretch these to one line without event field titles for saving disk space and quicker review.
Logs rotation #742380: Rawlog options . This sets how often the log file will change - hourly, daily, weekly, monthly or never. This may be useful if you need to review activity on site per the particular day or a week.
There are a variety of web statistics collection and analysis packages around. Webalizer is one of the fine old traditional (and free) ones. This module provides a mechanism for configuring webalizer, instructions on how to configure your (Apache) webserver to gather the statistics in the proper format, and the necessary (U*x) shell scripts to process the log files via cron.
The Sampler API allows modules to easily collect and store calculated pieces of data. It's designed primarily to assist in collection, storage, and display of metrics.
Modules provide the API with a metric to track (eg. 'Number of comments added to a node') a listing of objects to be tracked (for example, you may only want to track that for certain nodes) , a sampling strategy (eg. 'every 3 days'), and a method that returns the calculated values for the metric (eg. 'give me the values that you want to store for the period of January 1st midnight to January 4th midnight).
Based on the provided data, the framework:
Performs calculations to determine the how to sample for the metric
Calls the necessary functions to gather the calculated values
Handles all storage of the metrics
Provides default views of the metrics
Metrics are made available to the API via plugins, and are responsible for handling the calculations that the API tracks. This architecture allows for a large amount of flexibility in what can be collected and stored -- there are thousand of things that could be measured, and the API makes no attempt to decide which ones matter.
This module connects to Google Analytics and filters the tracking data for consumption by the node_counter table. Specifically this module was designed to solve the problem of displaying statistics information on a Drupal site behind a CDN or other fast forward caching service. The node_counter table data is periodically replaced with the statistics from Google Analytics. This module requires the Google Analytics API and a GA account.
Extends the node accessibility module, providing centralized statistics information pages. The Phplot API is used to add charts and graphs of the validation problems derived from the node accessibility statistics information.
Scoville tracks the "hotness" of content of your site. The hotness score is calculated from the number of hits the content has received, but the score "cools down" over time, so nodes which are newer but have fewer reads will be "hotter" than nodes which have more reads but are far older. The hotness score is exposed to Views, making it easy to create a block or page which lists your site's recently popular content.
Allows for logging user actions on sensitive/critical administrative pages. Logging is limited to specific users and/or user roles (configurable). Logging only occurs on specific administrative pages (configurable). Features include:
Comment Timer module provides an easy-to-use JS timer for the given content type's nodes, with Views support.
When a comment is to be submitted for a node that has enabled Comment Timer support, two textfields and two buttons will show up below the comment form. The first one is empty: if you enter a HH:MM:SS value there, that value gets stored. The second textfield is a counting timer. The first button resets that counter to 00:00:00, the second one pauses/continues the counter. You may update the counter while it's paused: if you enter a proper HH:MM:SS value, the counter will continue from there; if you have entered something else, the counter will continue from where it was paused.
Timing information is stored both for the comments and the nodes, with Views support for both.
Drupal 6 only
Manipulating timing information is done via hook_comment() and hook_nodeapi() to keep it in sync. A checkbox is provided at the admin interface to add timing information to the comments' text; if it's unchecked, timing information is only available for themers as $comment->comment_timer.
Note: Gauges tries to ensure that they aren't tracking your own activity by automatically ignoring any browser you use to log into their service. If it appears that the Gauges module isn't working, please try with a browser you have never used to log in to Gauges with.
Comment Count Notify is easy to configure module that sends a periodic mail with count of comments there in approval queue.
For advanced configuration of mail sending intervals, UI of Elysia Cron can be utilized.
This module does NOT provide summary or any other information about the comments posted - for that you can check Notify, Comment Notify and Comment Mail modules.
This module is basically of use for site administrators/moderators.
***Please do not reply to this mail***
You have 119 comments pending for approval.
To clear the pending comment approval queue, kindly login at http://example.com with your admin account and clear the comment approval queue at:
CASAA is a framework that allows admins to group systems such as Omniture Site Catalyst, Google Analytics, Yahoo APT, and other such services, and manage them from a single interface.
Through the interface, mappings, or tags as some refer to them, can be created across the site using URL paths or taxonomy terms to place specific values over content, sections, and other areas of the site.
With the developer's API, developers can easily create new plug-ins for the framework to support any service you wish.
What's new in 2.x:
Integration with CTools, providing a faster more intuitive interface.
Integration with the Domain Access module to allow managing services for multiple domains easier.
Performance tweaks to keep the system running fast so that users still get to their content fast and you get your data.
Plug-in registry system allows plug-ins to be installed and supported as external modules.
What's coming for 2.x:
Advanced help docs to help admins on the go.
2.x-Alpha release notes:
For current users:
existing plug-ins for 1.x are not supported and an upgrade to the 2.x compatible version will be required (data will not be lost, though!)
This module reads and parses your Amazon S3 account's various log files, so you can easily track your most popular uri's, and how much bandwidth has been used per-file. It also makes sure to never download the same log file twice (saving you bandwidth), and can be configured to only check for new log files every few hours (saving you GET and LIST requests).