Page History
...
- The context of the Uptime HTTP server http://<hostname>:<port> httpContext= http://localhost:9999
To ensure that the link back URL works correctly, update this field to the proper hostname of the Uptime Infrastructure Monitor monitoring station.
If this hostname is not resolvable from other networks, some users may not be able to resolve the URL in the email alert.
A restart of the uptime_core or "up.time Data Collector" service is required after applying this change.
...
Windows Agent
...
- Click on the Services tab.
- Click the Add Action Profile link on the left tree menu.
- Set up the action profile to perform the desired steps (e.g. log to file, run a script, start / stop Windows service, send an SNMP trap, etc.) and click Save.
Next, attach the action profile to an existing service monitor with the following steps:
- Click on the Services tab.
- Locate the service monitor in the list and click its name (or click the View icon).
- Scroll to the bottom of the page and click the Edit Action Profiles button.
- Add the appropriate Action Profile to the right list and click the Save button.
...
- Take LDAP Query, replace %s in the query with the name under LDAP Username
- Connect to LDAP using the distinguished name pointing to that user. If authentication fails (or user is not found), it will return "Invalid Credentials"
- On success, it takes LDAP Group Distinguished Name, and reads the object.
- If it can not find the object at all, it will output "No Group exists under that Distinguished Name."
- If it finds the object but the Group object is not under a domain name, it will not be able to read it and returns "Could not get members listing for Group Distinguished Name."
- If object is read, and the distinguished name in the object exists, the users are inserted into the local Uptime Infrastructure Monitor database
- If object is read, but it contains entries that do not link to a user, that particular user is skipped and not inserted into Uptime Infrastructure Monitor.
...
Active Directory Explorer
http://technet.microsoft.com/en-ca/sysinternals/bb963907.aspx
Wireshark
...