Please make support for groups
(via settings for csv files or ldap. please...)
The group usage size\percentages would be fine and useful for p.e. departments' summary)
Grouping users in tree like nested pages or displayed in a tree on a single page is a major change in sarg's design. I can't do that before I have addressed more pressing matters.
But, I can add code to group users as is already done with the host names.
Basically, a useralias file provides a list of user names with wildcards or regular expressions. Matching user names are replaced by the alias effectively grouping users with the same alias.
Of course, details about a specific user are lost.
Sourceforge's new interface is horribly unstable and full of bugs. My reply got lost too.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you for your reply. It seems that I could not choose other option
on the feature request.
This issue is not that important I can see. I would like to ask that where
can I find a bit more on this useralias file you mentioned and a short
howto on how to work with it would be a good workaround for my problem this
time.
Grouping users in tree like nested pages or displayed in a tree on a
single page is a major change in sarg's design. I can't do that before I
have addressed more pressing matters.
But, I can add code to group users as is already done with the host names.
Basically, a useralias file provides a list of user names with
wildcards or regular expressions. Matching user names are replaced by the
alias effectively grouping users with the same alias.
Of course, details about a specific user are lost.
Sourceforge's new interface is horribly unstable and full of bugs. My
reply got lost too.
Status: open Created: Fri Feb 08, 2013 07:10 PM UTC by RudyD Last Updated: Fri Feb 08, 2013 07:10 PM UTC Owner: nobody
Please make support for groups
(via settings for csv files or ldap. please...)
The group usage size\percentages would be fine and useful for p.e.
departments' summary)
Ironically, documenting it in the wiki was the task I had assigned myself for the past week-end. Then, when I read your feature request, I decided to spend that time on the useralias I talked about in my previous reply :-)
I'll try to document it this week.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Grouping users in tree like nested pages or displayed in a tree on a single page is a major change in sarg's design. I can't do that before I have addressed more pressing matters.
But, I can add code to group users as is already done with the host names.
Basically, a useralias file provides a list of user names with wildcards or regular expressions. Matching user names are replaced by the alias effectively grouping users with the same alias.
Of course, details about a specific user are lost.
Sourceforge's new interface is horribly unstable and full of bugs. My reply got lost too.
Dear Mr. Frederic Marchal!
Thank you for your reply. It seems that I could not choose other option
on the feature request.
This issue is not that important I can see. I would like to ask that where
can I find a bit more on this useralias file you mentioned and a short
howto on how to work with it would be a good workaround for my problem this
time.
On 9 February 2013 16:04, Frederic Marchal [email protected] wrote:
Until then I wish You good luck!
Yours sincerely!
Rudolf Finszter
mailto:[email protected]
Related
Feature Requests: #24
The only documentation about the hostalias file is in the sample sarg.conf file distributed along with the sources (you can view it in git: https://sourceforge.net/p/sarg/code/ci/1ec278e6e9e97d4f5adcf294d0e5d9b3d0a0f691/tree/sarg.conf). Search for the hostalias option. It's near the bottom of the file.
Ironically, documenting it in the wiki was the task I had assigned myself for the past week-end. Then, when I read your feature request, I decided to spend that time on the useralias I talked about in my previous reply :-)
I'll try to document it this week.