AWstats

Do you want AWstats in DirectAdmin?

  • Yes, it should be included ASAP.

    Votes: 53 79.1%

  • Yes, but it's not very important.

    Votes: 13 19.4%

  • I don't know.

    Votes: 1 1.5%

  • No, it shouldn't be included.

    Votes: 0 0.0%
  • Total voters
    67
smtalk

smtalk

Administrator
Staff member
Joined
Aug 22, 2006
Messages
10,162
Location
LT, EU
Hello,

This thread is for you opinion and suggestions about AWstats integration into DirectAdmin. Please feel free to suggest some options, feature requests etc. for AWstats in DirectAdmin.
 
Last edited:
As I see all the people are voting for "Yes", don't you have any requests?
 
There should be an advice for it :) As I know - there will be used static pages for the statistics, but I don't know anything else.
 
Last edited:
The following would be useful.

1. The user should only be able to have Awstats or Webalizer. They should not be able to use both.

2. The admin should be able to offer one or the other or both to clients.

3. Their should be a gui to configure the default settings for awstats.

4. Admin should be able to choose what hours stats WILL NOT be processed.

5. It should not conflict with scheduled backups if we choose.

6. We should be able to when we want stats to run. Every 12 hours, 24 hours, etc.

7. I can't stress this enough. Site Summary and Stats should be on separate pages. One has nothing to do with the other. Make sure the info generated on the stats main page is from the stats software the user chooses. Possibly include ftp stats last visitor, sub domain, etc.

Basically Cpanel has this covered well.
 
Good suggestions :) Are there any suggestions about URL to AWstats and its security (if it should be accessible not through DirectAdmin too)? And about ability to choose AWstats or Webalizer - there should be converter for this or it should be changed in the 1st day of the next month after the change?
 
A converter would excellent if possible. But not if it hinders a quick release.

"Are there any suggestions about URL to AWstats"

This should be configured to /stats folder by default and changeable as it currently is.
There should also be a feature to password protect the stats folder in the stats config section. No need to confuse the client to use the file manager to do this.
AWstats must be the framed version as the non-frame version is not nearly as good. I think this is possibly not static though. This is most critical IMHO. Also make it an option if admins want there users to be able to update reports(most will not).

It amazes me. People have been asking for awstats for 2 years and nobody else has anything to say:)
 
Not that amazing; the poll so far has garnered only 12 votes. While forum polling is incredibly inacurrate, one thing it does show is that of 8000 registered users (probably most inactive; I didn't check), only 12 users are even interested enough to see the poll, and vote in it.

Jeff
 
Perhaps you can make a post in the AWstats plugin threads and point them here. I know there are times I have not read the feedback forum for a while. I know this is one of the top requests.
 
I wouldn't mind seeing DA develop a AWStats integrated option in DA other then the plugins..including the one I've worked on.

Few issues people need to be aware of when asking for options...it's NOT that simple.

- The way DA performs it's log rolls is one of the hurdles that would need to be overcome. DA keeps individual logs in /var/log/httpd/domains, then just after midnight it rolls those logs into the users /stats files as gzipped tar files and empties them. At the same time it does the tallies and webalzier updates. Now, in order to do AWStats, at least in the case of teh AWStats 3.0 plugin, it needs to do it's update BEFORE DA's tally/webalizer run, or you get nada or really incomplete stats.

- AWStats is easily abused and because of the level of access it requires, can be a security issue, thus the reason why I disabled the update from web feature. While it would be nice to give some flexibility to the site owners (like where they want the stats stored, etc) there are just some things that should NOT be allowed IMHO.
 
if this is going to be implemented I suggest going for compatability with the first plugin that was made as many users will be currently using that.
 
Only ok, if this awstats generated every domain.com static html version example every night.

Have few times awstats non-static version, generated dynamicly, but awstats have lot of security bugs, and server hackered very easly.
 
smtalk said:
Yes, that's really amazing :)
Click to expand...

And most importantly, it should be upgradable at any time, by the server admin, and not have to rely on DA to deploy new versions of AWSTATS when they feel it. An when doing so, it should not break the entire installation.

As with cPanel, everyone has to rely on them to get new version out the door. Most of the times, and i mean 99% of the time, vulns and security holes found in this application was never upgraded by cpanel in time leaving alot of installations hackable. Therefore, the request to not have to reply on DA to upgrade an installation is a smart one.
 
You must log in or register to reply here.
Back
Top