| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
68982
|
Tue May 21 12:51:08 2019 |
 | Antonio Bulgheroni | antonio.bulgheroni@gmail.com | Question | Windows | 3.1.4 | Re: How to pre-fill an attribute that was added later |
Thanks, it worked great!
| Stefan Ritt wrote: |
|
Find all entries which have this attribute empty. Then click on Select, then select all, then click on Edit, then change all values. There might be a limit how many entries you can select in one go, so you might have to do it in bunches.
| Antonio Bulgheroni wrote: |
|
Dear all,
I have a question about my logbook. I have recently added a new attribute to my logbook and I would like to prefill all previous entries with a fixed value for this field. Is it possible?
Thanks for your help and best regards,
toto
|
|
|
|
68981
|
Tue May 21 12:08:17 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 3.1.4 | Re: How to pre-fill an attribute that was added later |
Find all entries which have this attribute empty. Then click on Select, then select all, then click on Edit, then change all values. There might be a limit how many entries you can select in one go, so you might have to do it in bunches.
| Antonio Bulgheroni wrote: |
|
Dear all,
I have a question about my logbook. I have recently added a new attribute to my logbook and I would like to prefill all previous entries with a fixed value for this field. Is it possible?
Thanks for your help and best regards,
toto
|
|
|
68980
|
Tue May 21 11:57:50 2019 |
 | Antonio Bulgheroni | antonio.bulgheroni@gmail.com | Question | Windows | 3.1.4 | How to pre-fill an attribute that was added later |
Dear all,
I have a question about my logbook. I have recently added a new attribute to my logbook and I would like to prefill all previous entries with a fixed value for this field. Is it possible?
Thanks for your help and best regards,
toto |
|
68979
|
Mon May 20 18:10:02 2019 |
 | Daniel Pfuhl | daniel.pfuhl@medizin.uni-leipzig.de | Question | Windows | V3.1.4 | Re: custom subject for mail info |
thank you!
| Stefan Ritt wrote: |
|
Use Email subject = $Subject
or a bit more detailed
Use Email subject = ELOG Ticket: "$Subject" posted by $Author
| Daniel Pfuhl wrote: |
|
Hello,
we are extensively using ELOG for documenting changes in our infrastructure. It is very helpful for us.
To avoid multiple documentation efforts it would be even more helpful if the subject of an ELOG entry also could be the subject of the mail which is sent out. With that we could send mails to our ticket system and include the special ticket number to make the right assignment in our ticket system.
Does anyone know if this could be accomplished with the latest version of ELOG?
Best regards,
daniel
|
|
|
|
68978
|
Mon May 20 16:39:50 2019 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | V3.1.4 | Re: custom subject for mail info |
Use Email subject = $Subject
or a bit more detailed
Use Email subject = ELOG Ticket: "$Subject" posted by $Author
| Daniel Pfuhl wrote: |
|
Hello,
we are extensively using ELOG for documenting changes in our infrastructure. It is very helpful for us.
To avoid multiple documentation efforts it would be even more helpful if the subject of an ELOG entry also could be the subject of the mail which is sent out. With that we could send mails to our ticket system and include the special ticket number to make the right assignment in our ticket system.
Does anyone know if this could be accomplished with the latest version of ELOG?
Best regards,
daniel
|
|
|
68977
|
Thu May 16 23:07:53 2019 |
| Lesley Herren | lherren@lhs.org | Question | Windows | 2.9.2 | Re: Windows Server 2012 - moving logs |
Thank you Stefan - it will take a couple of months to set up (many servers being built at the new farm). I will update you on the success of the files converting automatically.
| Stefan Ritt wrote: |
|
Just stop the server. Move your elog directory to the new server (including elogd.cfg, logbook directories, ...). Then check that the elogd.cfg needs modifications, like the URL which might have changed, then start the new server. V2.9.2 did have an old data format, which *should* be converted automatically. But first try it out before deleting the old server.
| Lesley Herren wrote: |
|
We are installing a new data center which will be based on Windows 2012 servers. Our current center is on Windows 2008 and will be decommissioned this year - 2008 servers (because of the security issue) will not be allowed in the new data center. So game plan is to install latest ELOG (3.1.2) on the 2012 server at the new data center and move the logs over from the 2008 server. I've looked through entries and do not see anything about moving the logs over from one system to another. In this case there are 2 concerns:
1. Has anyone moved the log entries from one system over to another?
2. Since we are also looking at updating version of ELOG - are there conversion steps necessary for the log entries or will v3.1.2 be able to use the log files from v2.9.2 as is?
Thank you, Lesley
|
|
|
|
68976
|
Thu May 16 21:49:06 2019 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | Windows | 2.9.2 | Re: Windows Server 2012 - moving logs |
Hi Lesley,
Perhaps I can restate Stefan's comment. The data structure of an elog entry, or indeed the structure of daily file(s) for any particular logbook has not changed between v2 and v3. What has changed is the directory structure. A set of sub-directories (named by calendar years) are added to each logbook, and all entries/files for any said calendar year moved into the directory for that year. It gave me a shock the first time I tried using v3 elog, I wondered what it was doing - it was the auto-conversion to v3 file structure. I had to convert it all back to v2 file structure, so as to continue to use v2.9.2, so I'm pretty sure there is no change to the data structure within any file, else I think the older elog would kick up a fuss. As an elog (ab)user, I've plenty of practice with the struture of the data files.
(There was a data structure change between v1 and v2 elog).
| Stefan Ritt wrote: |
|
Just stop the server. Move your elog directory to the new server (including elogd.cfg, logbook directories, ...). Then check that the elogd.cfg needs modifications, like the URL which might have changed, then start the new server. V2.9.2 did have an old data format, which *should* be converted automatically. But first try it out before deleting the old server.
| Lesley Herren wrote: |
|
We are installing a new data center which will be based on Windows 2012 servers. Our current center is on Windows 2008 and will be decommissioned this year - 2008 servers (because of the security issue) will not be allowed in the new data center. So game plan is to install latest ELOG (3.1.2) on the 2012 server at the new data center and move the logs over from the 2008 server. I've looked through entries and do not see anything about moving the logs over from one system to another. In this case there are 2 concerns:
1. Has anyone moved the log entries from one system over to another?
2. Since we are also looking at updating version of ELOG - are there conversion steps necessary for the log entries or will v3.1.2 be able to use the log files from v2.9.2 as is?
Thank you, Lesley
|
|
|
|
68975
|
Thu May 16 18:00:22 2019 |
| Daniel Pfuhl | daniel.pfuhl@medizin.uni-leipzig.de | Question | Windows | V3.1.4 | custom subject for mail info |
Hello,
we are extensively using ELOG for documenting changes in our infrastructure. It is very helpful for us.
To avoid multiple documentation efforts it would be even more helpful if the subject of an ELOG entry also could be the subject of the mail which is sent out. With that we could send mails to our ticket system and include the special ticket number to make the right assignment in our ticket system.
Does anyone know if this could be accomplished with the latest version of ELOG?
Best regards,
daniel |