ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1814
|
Wed May 3 00:16:42 2006 |
 | Mark Bergman | mark.bergman@uphs.upenn.edu | Request | Linux | 2.6.1 | allow per-logfile attributes to be added/subtracted from the global settings | I think it would be a big enhancement to allow per-logbook attributes to be additions or subtractions from the global attributes, rather than replacing the global settings.
For example, the [global] section of my elogd.cfg reads:
Attributes = Author, Type, Category, Severity, Subject, Entry ID, Status
Extendable Attributes = Type, Category, Severity, Subject, Status
Options Category = Hardware, Software (OS and utilities), Software (Application), Network, Security, Other
Options Severity = None, Low, Medium, High, Critical
Options Status = Open, Closed, In-Progress, Suspended
Options Type = To-Do, Problem Report, Problem Fixed, Informational Note, Software Installation, Configuration, Other
Required Attributes = Type, Category, Subject, Status
I've also got an logbook for each server for hardware issues. Within those logbooks, I'd like to keep all the fields except the software fields, and add fields for memory and storage.
Adding 7 definitions to each server logbook makes the config file huge and difficult to edit, and it means that a future change to the global settings wouldn't propagate to the individual log files. I'd really like to do something like:
[server47]
-Options Category = Software (OS and utilities), Software (Application)
+Options Category = Storage, Memory
-Options Type = Software Installation
+Options Type = RAM Installation, Drive upgrade
As I see it, the initial "-" sign in front of an attribute or option would indicate that the fields listed should be deleted from the global set (if the field name is an exact match), and a leading "+" indicates that the given fields would be added to the global attribute of the same name, for that specific logbook.
The current behavior--without a leading "+" or "-" would be unchanged, so that existing config files don't change.
Thanks,
Mark |
|
1815
|
Wed May 3 08:28:05 2006 |
 | Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.6.1 | Re: allow per-logfile attributes to be added/subtracted from the global settings |
| Mark Bergman wrote: | | I think it would be a big enhancement to allow per-logbook attributes to be additions or subtractions from the global attributes, rather than replacing the global settings. |
Sounds to me like a good idea. I will put it on the wishlist. |
|
1816
|
Wed May 3 08:31:52 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.6.1 | Re: Is it possible to require certain attributes for specific users (guests)? | > First of all, thanks for writing and maintaining eLog.
>
> I've been using it for a few years, but I'm now introducing it in an environment that may have a lot of "Guest"
> accounts.
>
> I'd like to have two "Required Attributes" when a guest enters a new entry; their name and e-mail address. These
> fields don't need to be required for registered accounts, since that information is available already.
>
> Is there any way to have conditional statements act on the value of $short_name?
No, this is not implemented. The only way you have right now is to make two separate logbooks, one for guests and
one for registered users. But I know this is not an optimal solution. I will think about it. |
|
1817
|
Thu May 4 16:01:29 2006 |
 | Tim Fowler | timfowler1@gmail.com | Bug report | Windows | 2.6.1-1681 | Elogd.exe crashes on windows | I have elog setup to send emails based on the priority of one of the attributes. When a new entry is created, the emails are sent successfully, however if the entry is edited or if you changed the attribute, elogd.exe will crash with a memory access error.
I have tried this and received the same results on different computers and different versions on Elog down to versions 2/6.0 beta 5. (it works correctly in that version).
The attribute in question is setup something like below:
Attributes = Ticket #, Site, Shift, Type, Area, System Name, Description, Priority, Status, Total Down Time, Last Revision
...(omitted config)
Options Priority = High, Medium, Low
...(omitted config)
Use Email Subject = $Site -- $System Name $Description
Use Email From = testuser@myexample.com
;Send email if priority is set to high
Email Priority High = testuser2@myexample.com
Display Email recipients = 1
Email Format = 14 |
|
1818
|
Thu May 4 17:26:41 2006 |
| Alex H | alex@synergie-inf.com | Question | Windows | 2.6.1-1668 | Date automatically generated by another one | Hi Stefan,
I am searching for a solution in order to have a date automatically generated by another one.
For example I want 1 month more :
I input the first date in "Date publication" : 01/01/2006 and the "Date validation" took automatically the 01/02/2006 value from themselve.
Can I do that with ELOG ?
Thanks for answer. |
|
1819
|
Fri May 5 07:58:53 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.6.1-1668 | Re: Date automatically generated by another one |
| Alex H wrote: | Hi Stefan,
I am searching for a solution in order to have a date automatically generated by another one.
For example I want 1 month more :
I input the first date in "Date publication" : 01/01/2006 and the "Date validation" took automatically the 01/02/2006 value from themselve.
Can I do that with ELOG ?
Thanks for answer. |
No, this is not implemented right now. |
|
1820
|
Fri May 5 09:01:04 2006 |
| Alex H | alex@synergie-inf.com | Question | Windows | 2.6.1-1668 | Re: Date automatically generated by another one |
| Stefan Ritt wrote: |
| Alex H wrote: | Hi Stefan,
I am searching for a solution in order to have a date automatically generated by another one.
For example I want 1 month more :
I input the first date in "Date publication" : 01/01/2006 and the "Date validation" took automatically the 01/02/2006 value from themselve.
Can I do that with ELOG ?
Thanks for answer. |
No, this is not implemented right now. |
OK! Thank for your response. |
|
1821
|
Fri May 5 14:49:19 2006 |
| Bertram Metz | bmetz@sbs.com | Question | Linux | 2.6.1-1622 | Email notification (bug tracking system) | Hello,
I'd like to use ELOG like a bug tracking system. I've created an attribute with the name AssignedTo. The attribute type is set to userlist. The value of AssignedTo is set to the full name of the selected user. There is no simple relationship between the full name and the email address on our system. Is it possible to get the email address of a user from the full name?
Attributes = Author, Category, Hardware, Software, Subject, Keywords, Status, AssignedTo
Options Category = Bug Report{1}, Observation{2}, Other{3}
Type AssignedTo = userlist
Show Attributes = Author, Category, Hardware, Software, Subject, Keywords
{1} Show Attributes = Author, Category, Hardware, Software, Subject, Keywords, Status, AssignedTo
Required Attributes = Author, Hardware, Software, Category
Options Status = new, open, confirmed, closed
;the following line does not work, since $AssinedTo contains the full name of the user
Email Category Bug Report = $AssignedTo@company.com
Kind regards,
Bertram |
|