The document lists the locations of log files for various Ipro Tech applications, including Eclipse, eCapture, and Allegro. It notes that the log files contain error and debugging information but accessing them across multiple machines can be time-consuming. The Log Reader tool allows centralizing and searching the logs but does not include logs for Media Manager/Self Service or Allegro.

1. 2-25-2017

2. The 1st
place to check for errors & stack traces:
Log files

3. List of Log File Locations:
 "C:ProgramDataIpro TechEclipseAdminEclipseAdminLog.log“
 "C:ProgramDataIpro TechEclipseAgentServiceAgentServiceHost.log“
 "C:ProgramDataIpro TechEclipseEclipseWebEclipseWeb.log“
 "C:ProgramDataIpro TechEclipseEclipseWebEclipseClient.log“
 "C:ProgramDataIpro TechEclipseSchedulerServiceSchedulerServiceHost.log“
 Import Logs located at C:EclipseScheduler
 "C:Ipro.dtSearch.ServiceIpro.dtSearch.ServiceHost.log“
 "C:Ipro.dtSearch.ServiceKeywordTermProcess.log“
 Note: Exception Log in SQL (Not gathered by Log Reader Tool)

4. List of Log File Locations:
 "C:ProgramDataIpro TecheCaptureControllerController.log“
 "C:ProgramDataIpro TecheCaptureEnterpriseServicesEnterpriseServices.log“
 "C:ProgramDataIpro TecheCaptureQCQC.log“
 "C:ProgramDataIpro TecheCaptureQueueManagerQueueManager.log“
 "C:ProgramDataIpro TecheCaptureQueueManagerDeletionHistory.log“
 "C:ProgramDataIpro TecheCaptureWorkerWorker.log“
 "C:ProgramDataIpro TecheCaptureWorkerWorkerAgent.log“
 "C:ProgramDataIpro TecheCaptureWorkereCaptureServiceHost-[Premium
EDD Driver 1].log“
 Can be up to 8 driver logs per worker
 "C:ProgramDataIpro TecheCaptureWorkerStreamingDiscovery-Premium EDD
Driver 1.log“
 Can be up to 8 streaming logs per worker

5. Pros
Lot of information is stored
Plenty of places to check
Detailed errors and DEBUG toggle available
Cons
Time consuming
Having to log into several machines to track down an
error
Decentralized information

7. Uses:
Centralize all of the log information into one
screen/machine
Search for specific words/phrases through all logs at
once
Filter log information within a time frame
Export Log information for viewing later

8. Log Reader grabs info for:
Eclipse Scheduler App Environment
Eclipse Service App Environment
eCapture App Environment
But does not grab info for:
Media Manager/Self Service
Ipro Allegro App Environment
Side Note:
I had to insert
this in
manually

9. List of Log File Locations:
Most Important:
 "C:ProgramDataIPRO TechAllegroEcaQueueReaderEcaQueueReader1.log“
 "C:ProgramDataIPRO TechAllegroIpro.Eca.Admin.ServiceHostIpro.Eca.Admin.ServiceHost.log“
 "C:ProgramDataIPRO TechAllegroIpro.Eca.Analyzer.ServiceHostIpro.Eca.Analyzer.ServiceHost.log“
 "C:ProgramDataIPRO
TechAllegroIpro.Eca.QueueMonitor.ServiceHostIpro.Eca.QueueMonitor.ServiceHost.log“
 Web Log if using AllegroWeb
 "C:ProgramDataIPRO TechAllegroIpro.Eca.Ingestion.ServiceHostIpro.Eca.Ingestion.ServiceHost1.log
 Depending on amount of threads, there may be anywhere from 1-16 Ingestion Service Host (worker) logs to check.
 "C:ProgramDataIPRO
TechAllegroIpro.Eca.FileMounting.ServiceHostIpro.Eca.FileMounting.ServiceHost.log“
Least Important:
 "C:ProgramDataIPRO TechAllegroIngestionManagerIngestionManager.log“
 "C:ProgramDataIPRO TechAllegroIpro.Eca.Admin.DesktopIpro.Eca.Admin.Desktop.log“
 "C:ProgramDataIPRO TechAllegroIpro.EcaAnalyzer.DesktopIpro.Eca.Analyzer.Desktop.log“
 "C:ProgramDataIPRO
TechAllegroIpro.Eca.Admin.LoggingServiceHostIpro.Eca.Admin.LoggingServiceHost.log“

10.  Demonstration…

11. ???