With the data in a mysql db, then I can do adhock querries on
top of the standard awstats. Plus, we generate enormous
logs on our web servers (about 60 servers), and our poor little
machine that we have running awstats gets a bit bogged
down on Sunday trying to parse these log files. If I log my
web traffic to a DB, then awstats will always be instant / up-
to-date. But most of all, I thought it would be a good feature
for a world is quickly becoming more database driven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
All AWStats stores are the final totals. Storing this
information in MySQL would probably slow things down because
there is so little information to load; it would be much
faster to just read it out of the stats file.
If you mean it should pull from MySQL logs, as if you had
mod_log_sql installed with Apache, well, Apache still keeps
a text log when log_sql is used, so you could have Apache
log to MySQL to perform your own queries on the logs
quickly, and let AWStats just use the text log file that
Apache is still going to keep anyway. You still need to
rotate that text log file, so you may as well run your
AWStats -update on it when you do.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In my opinion it makes sense to implement SQL in AWStats. The CGI
itself should still get its data from the AWStats data files, but it would be
nice to have some of the analyzed data in SQL tables. AFAIK its not
possible to do long term comparisons with AWStats.
Example: If you wanna see, how the "number of visits per day" evolves
over the years, you have retrieve the data from every month and put it in
a database.
We're using NetCharts (http://www.netcharts.com/) to do data mining
and visualize the results. But we need the data in databases. All we need
is a little tool that converts some of the numeric data from the data files
to a database. Not all of the data would be useful, but at least everything
between "BEGIN_DAY" and "END_DAY" would be helpful.
Andi
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have created a script that pull data from a mod_sql_log
table, but I have to call it, redirect it's output to a file
then get awstats to process it, would it be nice to be able
to call a shell `` instead of a fimple file?
whuld any developer consider this? all I would like to see is a
log_file = "[filename]"
with the option to:
log_file = "shell:/usr/local/pull_script.sh param_1 param_2"
thank you guys for all the work done so far.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We have two identical web servers (redundancy set via DNS,
two identical host records, but different ip addresses for
values) logging to mysql as opposed to file based logs using
mod_log_mysql. What is the status of this project?
Perhaps my method of redundancy setup is not common. All
suggestions are welcome.
-=-Greg
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=546050
I desperately need logs to be collected from a db
(mod_log_sql/IIS odbs).
a connection string in the /awstats.*.conf would help, an
input from standard input would already be of help
Logged In: YES
user_id=404455
Yes that would be great! Because we all love mysql ;)
or maybe only an option to use mysql!
this would improve the performance wouldn't it?
Marc
Logged In: YES
user_id=788954
please don't forget us poor users using windows if you
implement database support - perhaps using odbc to connect
to the db or something?
Logged In: YES
user_id=825276
Maybe will it sound stupid, but why do yu want data in mysql
database ?
Logged In: YES
user_id=544414
With the data in a mysql db, then I can do adhock querries on
top of the standard awstats. Plus, we generate enormous
logs on our web servers (about 60 servers), and our poor little
machine that we have running awstats gets a bit bogged
down on Sunday trying to parse these log files. If I log my
web traffic to a DB, then awstats will always be instant / up-
to-date. But most of all, I thought it would be a good feature
for a world is quickly becoming more database driven.
Logged In: YES
user_id=341046
This is a confusing request, I think.
All AWStats stores are the final totals. Storing this
information in MySQL would probably slow things down because
there is so little information to load; it would be much
faster to just read it out of the stats file.
If you mean it should pull from MySQL logs, as if you had
mod_log_sql installed with Apache, well, Apache still keeps
a text log when log_sql is used, so you could have Apache
log to MySQL to perform your own queries on the logs
quickly, and let AWStats just use the text log file that
Apache is still going to keep anyway. You still need to
rotate that text log file, so you may as well run your
AWStats -update on it when you do.
Logged In: YES
user_id=869383
In my opinion it makes sense to implement SQL in AWStats. The CGI
itself should still get its data from the AWStats data files, but it would be
nice to have some of the analyzed data in SQL tables. AFAIK its not
possible to do long term comparisons with AWStats.
Example: If you wanna see, how the "number of visits per day" evolves
over the years, you have retrieve the data from every month and put it in
a database.
We're using NetCharts (http://www.netcharts.com/) to do data mining
and visualize the results. But we need the data in databases. All we need
is a little tool that converts some of the numeric data from the data files
to a database. Not all of the data would be useful, but at least everything
between "BEGIN_DAY" and "END_DAY" would be helpful.
Andi
Logged In: YES
user_id=362167
bump
Please implement reading log data from database, in
additional to traditionally reading the text log files.
Logged In: YES
user_id=546050
I have created a script that pull data from a mod_sql_log
table, but I have to call it, redirect it's output to a file
then get awstats to process it, would it be nice to be able
to call a shell `` instead of a fimple file?
whuld any developer consider this? all I would like to see is a
log_file = "[filename]"
with the option to:
log_file = "shell:/usr/local/pull_script.sh param_1 param_2"
thank you guys for all the work done so far.
Logged In: YES
user_id=1400544
To whom it may concern:
We have two identical web servers (redundancy set via DNS,
two identical host records, but different ip addresses for
values) logging to mysql as opposed to file based logs using
mod_log_mysql. What is the status of this project?
Perhaps my method of redundancy setup is not common. All
suggestions are welcome.
-=-Greg