KML_FLASHEMBED_PROCESS_SCRIPT_CALLS
 

New Feature: Job History – A Log File for GoGrid

April 10th, 2009 by - 6,400 views

Many GoGrid users may have noticed a new tab that has appeared within the GoGrid Web Interface. The new "Jobs" tab is a great new addition for those who want details on any action or activity that has taken place on an object (e.g., Server, Load Balancer, Cloud Storage) within their GoGrid account.

jobs_tab_highlight

Think of this new section as your GoGrid log file. It keeps track of actions that you have made on objects in your account, broken down chronologically. In fact, since we have been keeping an internal log for some time, many of your older activities prior to the release of this feature will show up in your log. Also, if you use the GoGrid API, any requests made through the API show up in the Job section as well.

GoGrid actions that are currently tracked are:

  • Add Server
  • Delete Server
  • Restart Server
  • Add Load Balancer
  • Delete Load Balancer
  • Add Cloud Storage

All actions are also logged with the following information:

  • Date & Time (UTC timestamp – a good time converter can be found here)
  • Action Details
  • Action Status
  • User that requested the action

Job History List

jobs_event_list

The Job list contains all of the actions that have taken place on your GoGrid account. The icons represent both the Action and the Object and are followed by a brief name of the event. Date, action Status and User that requested the action follow that.

Job Details

The power is in the details. You can drill down each object action to see greater detail on what transpired. Shown below are: Create Server, Start Server, Create Load Balancer and Create Cloud Storage. You always have full insight into who requested the action and what state the object is in. Current states include:

  • Created: The time and date the job request was made.
  • Queued: The time and date the job was received.
  • Processing: The time and date the job began processing.
  • Succeeded:The time and date the job was completed.
  • Fatal: The time and date the job became fatal (if applicable). This means the job failed and could not be executed to completion.
  • Canceled: The time and date the job was canceled by the system (if applicable).
  • Failed: The time and date the job failed (if applicable). This may occur multiple times as a job can fail and then be queued again before succeeding or becoming fatal.

jobs_create_virt_svr2 

jobs_start_virt_svr2 

jobs_create_lb2 

jobs_create_storage2

Search Box

If you need to search for a particular object quickly, you can use the Search Box.

jobs_search

Advanced Searching

To quickly drill down to a specific action on a specific object, or to constrain your search by a date range, use the Advanced Search.

jobs_adv_search jobs_adv_search_calendar

We would love to hear what you think about this feature. It’s a great way to keep track of you and other users in your account and what they have been doing with GoGrid. As always, we hope you like it!

The following two tabs change content below.

Michael Sheehan

Michael Sheehan, formerly the Technology Evangelist for GoGrid, is a recognized technology, social media, and cloud computing pundit and blogger who writes regularly about technology news and trends.

3 Responses to “New Feature: Job History – A Log File for GoGrid”

  1. Hi, this looks a good step around visibility. 2 questions:
    - can the log be pushed/pulled in near real-time to an enterprise SEIM? (i.e. enterprise event integration)
    - didn't see any mention of source IP (especially for API requests) – is that included in the customer facing log?

    Cheers

    Craig

    • Thanks for the note Craig.

      In response to your first question, we do provide various methods to list and get details for various GoGrid jobs through our REST-like API. For details, please visit the following pages:
      http://wiki.gogrid.com/wiki/index.php/API:grid.jo
      and
      http://wiki.gogrid.com/wiki/index.php/API:grid.jo
      If you use those methods, you could conceivably pull out the jobs to an external system for event integration.

      In answer to your second question, while we do provide the user name for who initiated the job or action, we currently do not capture the source IP for jobs. API requests are not currently listed in the Job History, only the result of those actions (e.g., create server). I  have, however, sent this information on to our Product team for possible inclusion in future releases.

      Thanks,
      Michael

  2. OK so I assume GoGrid captures the source IPs of requests when API calls are made, just that you're not exposing that information via your API/web interface. Thanks, Craig

Leave a reply