Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<blockquote> <p>What would be the most efficient way to go for this?</p> </blockquote> <p>That's up for debate - I dare say part of the reason for the post. Personally, I would threadpool the reading of the logs on a machine by machine basis and store the results of these operations in a SQL Server back end. However, this is the heavy-duty, production environment approach and may not be applicable depending on how much effort you want to put in.</p> <p>Ideally, this would be written as a dedicated Windows Service and building/debugging these has become a lot easier in more recent versions of Visual Studio. Another viable approach is to create a console application that you can easily run and see the output of. When deploying you can use a tool all NSSM to allow the console application to run as a windows service. This is probably the least painful but slightly clunky method - other posters may have a neater solution.</p> <p>Having one application or program running on a single server would be the easiest way but this assums that the server has access to the relevant shares on each machine where the log files are located.</p> <p>If you wanted to deploy a service onto each machine in question and have it run locally (bypassing the whole multi-threaded methodology as you have one thread checking one set of log files on a defined schedule), then having a SQL Server back end is the easier way to go as it's easier to configure a SQL Server account and allow remote connections to it than it is to configure folder shares across a set of machines (I stand to be corrected on thsi as I'm not a domain admin). The downside to this is that if you need to update the application then updating on each machine is a pain.</p> <p>It comes down to which approach suits your situation best? The single deployment requiring machine shares or the multi-deployment with a single SQL Server (or other data store) instance?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload