Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Agentless Monitoring

Created: 12 Aug 2014 | 14 comments

I am trying to setup some Agentless monitoring for our enterprise. I followed the tutorial here, but im not sure how to assign the policies to a webpage? After i setup the Policy how to do I tell what webpage to monitor?

Thanks

 

 

Operating Systems:

Comments 14 CommentsJump to latest comment

Igor Perevozchikov's picture

If I correctly remember, 'path' in HTTP agentless metric is a path to virtual directory of web site.

For example default path is root / for default http metric:

Path_1.jpg

You can try to set exact path to required directory and monitor it.

Path_2.jpg

  1. Don't forget that, first you can find an answer for your question in Knowledge base
  2. If answer solves your question, then please mark as solution to close a thread
mchipser's picture

I understand that, but dont you need to point it to a domain somewhere?

For instance we have a Agentless ICMP policy that are targeting "all servers" which will alert us if any of the servers go offline. This is a filter comprising of all our servers.. I need to apply the HTTP monitor policy to test if a random website is online or offline, how / where do I apply the policy?

for instance if I want to monitor "www.yahoo.com" where could I apply that policy?

mchipser's picture

Thanks for the response.. I already have that set, but I'm not sure how to apply this policy to a filter which has a domain.

Capture.PNG

 For instance we currently have a agentless policy for ICMP and applied to a filter that lists all the servers in the organization. This notifies us if any of the server no longer respond to ping requests. How can I apply this same functionality to an SQL port, or a HTTP port. How can I apply those policies to a specific web page / port?

Capture_0.PNG

I tried adding a weblink as a filter to the web page i want to monitor, but then I can't set the target to that filter.

Igor Perevozchikov's picture

1st: Make sure that NS server knows/has this resource/computer (where required Web SIte is running, which you'd like to monitor)

  • At least you can check "All Resources"

AvailableResourceWebSite.jpg

2nd: If it doesn't exists and you don't want to make this server as managed resource (otherwise to install there Symantec Management Agent), then you can discover this resource and it will be available on NS server as unmanaged resource, which you can add in resource target of your agentless monitor policy.

ND1.jpg

  • After completed network discovery task, you can choose this discovered resource from resource list to add it in resource target

ResourceTarget_CustomResource.jpg

  1. Don't forget that, first you can find an answer for your question in Knowledge base
  2. If answer solves your question, then please mark as solution to close a thread
mchipser's picture

Ahhh.... I was assuming since this is an "agentless" policy I could monitor anything, even if it didnt have a agent installed on the system. Isn't that how a ICMP or a SNMP monitoring works?

Igor Perevozchikov's picture

No. Agentless monitoring is for unmanaged resource/devices (where no Symantec Management Agent is installed), although you can add managed resources as well for such monitoring.

Your current ICMP/SNMP Agentless monitoring performs for known managed or unmanaged resources in NS servers, depending on what you've added in resource target of agentless monitor policy.

Also, each resource, which is monitoring via agentless policy, will consume 1 license node for Monitor Solution Pack for Server product.

Summary

Case:

  • I want to monitor ICMP Availability, SNMP OID and HTTP status of my Web Site which is running on some server.

What to do:

  • Install Symantec Management Agent on this Server where Web Site is running, to make NS server to know about this resource as managed resource, and then include this managed server in resource target of agentless monitor policy.

OR

  • Do not install Symantec Management Agent on this Server, where Web Site is running and just perform Network Discovery task to discover this server and make as known unmanaged resource on NS server, and then include it in resource target of agentless monitor policy.

Thanks,

IP.

  1. Don't forget that, first you can find an answer for your question in Knowledge base
  2. If answer solves your question, then please mark as solution to close a thread
mchipser's picture

Thanks for the clarification! I think i can figure it out now..

 

Igor Perevozchikov's picture

You're welcome!

I think that this thread will be useful for you, because you're configuring an agentless monitoring

  1. Don't forget that, first you can find an answer for your question in Knowledge base
  2. If answer solves your question, then please mark as solution to close a thread
mchipser's picture

Ok I have yet to get this to work..

I setup a test system with IIS installed to test the agentless and to see if I could determine if the webpage is down. I set the target to only that system, and made sure the path in HTTP metirc is "/wwwroot/" or "/wwwroot/iisstart.htm" and neither can tell if the page goes down (testing turning of the service)

 

http.png

 

http2.png

Igor Perevozchikov's picture

Do not forget that by default HTTP protocol credentials are set to "Anonymous"

In case, if your Web Site has another credentials to access, then change them for HTTP protocol in "Connection Profile"

HTTP_Creds.jpg

  1. Don't forget that, first you can find an answer for your question in Knowledge base
  2. If answer solves your question, then please mark as solution to close a thread
mchipser's picture

I still can't get this to work.. Is it possible to see the status of the policy? Something like permissions error, or anything that points to the problem?

Igor Perevozchikov's picture

You need to know what resource you've added in resource target of agentless monitor policy

⇒ then you open "Resource Manager" of this monitored resource ⇒ click "View" ⇒ "Inventory" ⇒ "Monitor" ⇒ "Monitor Detected Policies" ⇒ there you will see state of policy.

Also you can check metrics state @ "View" ⇒ "Events" ⇒ "Monitor" ⇒

  1. Don't forget that, first you can find an answer for your question in Knowledge base
  2. If answer solves your question, then please mark as solution to close a thread
mchipser's picture

It appears is isnt being applied to the resource..

Untitled.png

Untitled1.png

Untitled2.png

Igor Perevozchikov's picture

You can check what metrics are available or unavailable, using "Real Time Performance Viewer"

realtime.jpg

  • Choose there your monitored resource and set to see also unavailable metrics for this resource

RealTIme_Metrics.jpg

If an agentless metric is unavailable for monitored resource, then you need to:

1. Specify these registry keys to enable traces/verbose logging of PPA and RMS plugin on server, where RMS plug-in is running and monitoring.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\PluggableProtocols\Debug]
"Level"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\PluggableProtocols\CimWsMan]
"tracelevel"=dword:0000001f

[HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\eXpress\Monitor\Debug]
"Error"=dword:00000003
"Information"=dword:00000003
"Profile"=dword:00000003
"Trace"=dword:00000003
"Warning"=dword:00000003

2. Download "DebugView" tool from Microsoft web page http://technet.microsoft.com/en-ie/sysinternals/bb896647.aspx 

  • Start "DebugView" on server, where RMS is monitoring (You can filter out unnecessary traces, etc) and then restart "Altiris Monitor Agent" service.

In debugview log output, you will see such information, when RMS is trying to perform an agentless monitoring of appropriate resource. Then you will be able to determine why this metric is unavailable for your monitored resource.

DebugView log output example:

PPA:  [Debug] Plugin HttpPlugin {46F4D792-F2C3-4F05-A023-0C673B551661} initialized successfully!
PPA:  [Debug] Connection::Id f547669e-587a-11e4-99a5-005056895eb0: Connection Successful.
PPA:  [Debug] Session::Connection successfully established.
PPA:  [Debug] Session::Exiting EstablishSimpleSession().
PPA:  [Debug] SessionMgr::Simple session id: f547669d-587a-11e4-99a5-005056895eb0 for IP: 1x.1x.6x.1x was successfully created    
PPA:  [Debug] SessionMgr::Exiting CreateSimpleSession()
PPA:  [Debug] PAL::Exiting OpenSession().

[TRA] HTTP[host:{6420FE79-3E1A-4F75-9D2D-3EA2EAF2378C};request:Status]: GetSession: Session 'simple:cpm:{6420FE79-3E1A-4F75-9D2D-3EA2EAF2378C}' opened (PAL session ID: 'f547669d-587a-11e4-99a5-005056895eb0'). Took 53 sec(s).

[TRA] HTTP[host:{6420FE79-3E1A-4F75-9D2D-3EA2EAF2378C};request:Status]: Using PAL session 'f547669d-587a-11e4-99a5-005056895eb0'
PPA:  [Debug] PAL::SendCommand(): Current Session ID: f547669d-587a-11e4-99a5-005056895eb0 Primary Session ID: 

[TRA] HTTP[host:{6420FE79-3E1A-4F75-9D2D-3EA2EAF2378C};request:Status]: result[0]: Attribute:HTTP::ErrorCode,Value:0|Attribute:HTTP::Status,Value:0|

[TRA] HTTP[host:{6420FE79-3E1A-4F75-9D2D-3EA2EAF2378C};request:Status]: Returning PPAERR_OK. # of instances: 1

[PRO] HTTP[host:{6420FE79-3E1A-4F75-9D2D-3EA2EAF2378C};request:Status]: GetPpaMetric execution time: 53 sec(s)

  1. Don't forget that, first you can find an answer for your question in Knowledge base
  2. If answer solves your question, then please mark as solution to close a thread