I don't understand your question. There is no "inline" vs. "external" script. Using the "execute new = <command>", you run a script on the server side. Can be powershell under Windows or bash/csh under Linux. I remember however that there has been issues under recent windows in passing parameters to the shell. Linux certainly works fine, we usse it all the time.

I think it was just a matter of my specific interepretation of the documentation, ie: using native OS shell commands vs any script language file containing shell commands or any app for that matter. Nevertheless I think you've answered my questiuon so it's all good. Thanks Stefan.

I have the line in my elog config to run a Powershell script when submitting a New entry. I just send an email as a test:

Execute New = "Powershell.exe -ExecutionPolicy Bypass D:\SendEmail.ps1"

Fyi, the Powershell statement itself (Send-MailMessage -From 'MeterElog@winnipeg.ca' -To 'alangrant@mts.net' -Subject 'New meter entry' -Body 'TEST' -Priority High -DeliveryNotificationOption OnSuccess, OnFailure -SmtpServer 'citygw') works fine and the email is received when running it from the Powershell ISE app directly from the same elog vm server but not from within Elog with the above statement.

I'd like to first confirm that the syntax of the line Execute New = is correct, ie, double quoting the entire command. Can anyone please confirm.

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

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.

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

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).

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.