Application Perf Mgmt (BAC / BSM) Practitioners Forum
Showing results for 
Search instead for 
Do you mean 

Sitesscope Log Monitor issue.

Regular Visitor

Sitesscope Log Monitor issue.

I am currently using SiteScope 11.20, and have been working to setup a log file monitor but have been getting an error when I try to run the monitor("unable to read log file").

 

I have made sure the sitescope user is able to read the file when I manually log into the server.  Sitescope is using netbios for this windows server and trying to read the log file from the following path.

 

d:\prod\system\logs\ect.bat.log

 

Any help is appreciated.

 

5 REPLIES
Highlighted
Valued Contributor

Re: Sitesscope Log Monitor issue.

Try this :

 

\\Server Name\d$\prod\system\logs\ect.bat.log

 

Also Check the same is accessible from sitescope server.

 

Revert if you are finding difficulties ahead.

 

Regards,

Mascotte

-/-\- Mascotte
"Assign the Kudos to the kind fellas to shew the appreciation"
http://h30499.www3.hp.com/t5/custom/page/page-id/hp.rulespage
Honored Contributor Honored Contributor

Re: Sitesscope Log Monitor issue.

Though you select the Target server in monitor, the log file path should reflect the absolute path from SiteScope server. Try to use the path as \\RemoteServer\D$\\prod\system\logs\ect.bat.log

Regards,
Raj

Like this Post? Click Kudos! to show appreciation.
Is your issue addressed? Click "ACCEPT AS SOLUTION" against the post which helped you the most.
Honored Contributor Honored Contributor

Re: Sitesscope Log Monitor issue.

Hello, mdez

 

#1.  Did you share the log file in Windows?

 

In Windows, you must do a file share for SiteScope to read the log.

 

Best Regards,

 

David

Occasional Advisor

Re: Sitesscope Log Monitor issue.

Hi,

 

Are you trying to read the log file for Windows server 2003 OR 2008.

 

If you are using 2008, Try to give the path As specifed in the particular event.

 

I have added an attachment for your reference.

 

Regards,

Somank

Regular Visitor

Re: Sitesscope Log Monitor issue.

It appears that using the below format for the path seems to have worked.

 

\\Server Name\d$\prod\system\logs\ect.bat.log