Help Docs

Reboot a Neptune Instance

Using Site24x7's IT automation framework, you can create an action profile to reboot a Neptune Instance automatically when there's a threshold breach or if there's a change in the status of a monitor.

Required Permissions

Please make sure the IAM role assumed by Site24x7, or the IAM user created for Site24x7, has the following partial write actions in the attached policy document to perform the actions.

  • rds:RebootDBInstance

Create an action profile

  • Log in to the Site24x7 web console, select Admin > IT Automation Templates.
  • Click on the drop-down, and select the action to be performed: Reboot Neptune Instance.
  • Provide a display name.
  • The action will be pre-populated in the field below.
  • The instances that have to be rebooted can be selected by providing your preference in the Destination Neptune Instance(s) field.
  • Max Allowed Action Execution Time: The maximum number of seconds Site24x7 has to wait before the request times out. The execution time is set at 15 seconds, by default. You can define an execution time between 1-90 seconds.
  • Send the Automation Result via Email: You can choose to receive an email regarding the automation result by toggling this setting to Yes. Share automation results via an email to your User Alert Group configured in the Notification Profile. This email will contain parameters including the automation name, type of automation, incident reason, destination hosts, and more.
  • Click Save.

Simulate the Automation

Before mapping the action profile, you can test its functionality by invoking the operational task manually within the Site24x7 console or by using our REST APIs. This is done to check whether the appropriate write-level permissions required to execute the reboot action are in place. To test, navigate back to the IT Automation summary page (Admin > IT Automation), and click on the play icon to execute a dry run.

Map the Action Profile

To execute the automation, map the action profile to the desired alert event. You can either map the profile to a predefined monitor-level event type or to a custom attribute-level event type.

Monitor-level mapping

Navigate to the Edit page of the monitored Neptune Instance, and map the action profile with any of the following monitor status changes:

  • Execute on Down
  • Execute on Up
  • Execute on Trouble
  • Execute on Critical
  • Execute on any Status change

Attribute-level mapping

You can also associate the action profile to any monitored AWS resource or application-related metric data points like CPU Utilization, Network Throughput, Gremlin Errors, SPARQL Errors and more.

Navigate to the Edit Threshold Profile page of the monitored AWS resource (go to the Edit page of the resource, and click on the Pencil icon beside the Threshold and Availability field), and map the profile to any desired attribute by clicking on Select Automation to Execute.

Was this document helpful?

Would you like to help us improve our documents? Tell us what you think we could do better.

We're sorry to hear that you're not satisfied with the document. We'd love to learn what we could do to improve the experience.

Thanks for taking the time to share your feedback. We'll use your feedback to improve our online help resources.

Shortlink has been copied!