Windows Reboot Monitor

Windows reboot Monitor works with .NET Agent Extension Manager to capture and report last windows reboot time and reason as controller event.

Contents

Windows Reboot monitor require extension.xml file to be placed in a new folder under <Extension Manager Root Directory>/Extensions

Prerequisites

  • .NET Agent Extension Manager, can be downloaded from here
  • The AppDynamics .NET Agent
  • .NET 4.0 or later

Installation

Download and copy extension.xml in a new folder under Extensions directory of .Net Extension Manager. Please refer to the next section for detailed steps.

Getting Started

  1. Create a new folder under Extension Manager root directory. We can name it WindowsRebootMonitor
  1. Copy extension.xml to this folder.
  1. Edit extension.xml to provide controller details and target specific events.
    • Change the name of extension if required. (It will take the folder name if we leave it blank.)
      <extension type="Event" name="WindowsRebootMonitor" enabled="true">
      
    • Provide controller user credentials. These are required for publishing custom events to the controller. For single-tenant controllers, use "customer1" for the account. Controller host/port are read from the Agent Configuration file (config.xml).
      <controller-info user="username" account="customer1" password="password" />
      
    • Associate event to any node or tier. This is optional and if we leave these commented then the event will be associated with application only.
        <controller-event-properties>
          <add key="node" value="MyNodeName"></add>
          <add key="tier" value="MyTier"></add>
        </controller-event-properties>
      
      NOTE: The node and Tier names must match an existing Node/Tier exactly, or an error will be generated and event will not be registered. Also valid property combination are : Only Tier or Node+Tier.
  1. Save the file and launch Extension Manager UI. We should be able to see WindowsRebootMonitor extension listed under "List of extensions loaded"
  1. Start Extension Service, if it was stopped or Restart for the changes to take effect.
    • We will see new custom events sent to the controller. We should be able to view link to Custom Events on Application Dashboard. For more details https://docs.appdynamics.com/display/PRO41/Monitor+Events.
    • Event will contain following details-

Troubleshooting

Please note that this extension reports last windows shutdown time and reason upon extension service start up. It will generate an event to report last shutdown time, if we simply restart extension service. Also it will fail to report last shutdown time if machine fails to start.

If you're not seeing events reported to the controller, check to make sure the controller credentials are correct and try removing node/tier mapping if added. If this doesn't help, check the Logs folder for any errors.

Upgrade

  1. Upgrade to latest version of extension manager.
  2. Copy new extension.xml and make appropriate changes.
  3. Start Extension Service to use latest version.