Skip to main content

Saved Searches

Data is a double-edged sword lightsaber. Sometimes you find things that you wish you hadn't (but it's always good that you did). Now we've got some work to do to report the status of our failed web requests, fix them, and monitor them.

We could take these logs and send them to a centralized data platform for analysis... but why? There's no fun in that! (It is literally not a fun process. Hence, the need for searching data in place.) We've already done most of the work, so let's leave that data in S3 and use Saved Searches and Dashboards to wrap things up.

Saved Searches​

Saved Searches are a great way to keep and organize searches that you find useful, but what's even better is they can be set to alert you when things go awry.

It's safe to say we've determined this search to be useful, so let's save it.

Save the Search. Save the World.
  1. Select the Actions dropdown at the top right of the bar chart.
  2. Click Save Search.
  3. In the Name field, name the search Sandbox Webserver Fails.
  4. Click Time Range.
tip

The time picker can be used to select the time range that should be applied every time the search is run. For now we will leave it set for 1 hour ago.

  1. Click Save.
  2. Click the saved-searches-icon Saved Searches tab.
  3. Click Sandbox Webserver Fails to make sure your search saved correctly.
  4. Click the X to close the saved search.
Alerting

Saved searches can be scheduled to run automatically at a set interval and configured to send notifications to external systems such as Slack. For our purposes we won't be scheduling notifications.