<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: New Feature: Job History &#8211; A Log File for GoGrid</title>
	<atom:link href="http://blog.gogrid.com/2009/04/10/new-feature-job-history-%E2%80%93-a-log-file-for-gogrid/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.gogrid.com/2009/04/10/new-feature-job-history-%e2%80%93-a-log-file-for-gogrid/</link>
	<description>&#34;Complex Infrastructure Made Easy™&#34;</description>
	<lastBuildDate>Wed, 22 May 2013 15:20:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Michael Sheehan</title>
		<link>http://blog.gogrid.com/2009/04/10/new-feature-job-history-%e2%80%93-a-log-file-for-gogrid/#comment-1517</link>
		<dc:creator>Michael Sheehan</dc:creator>
		<pubDate>Sat, 11 Apr 2009 06:27:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gogrid.com/?p=859#comment-1517</guid>
		<description><![CDATA[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: 
&lt;a href=&quot;http://wiki.gogrid.com/wiki/index.php/API:grid.job.list&quot; rel=&quot;nofollow&quot;&gt;http://wiki.gogrid.com/wiki/index.php/API:grid.jo...&lt;/a&gt; 
and 
&lt;a href=&quot;http://wiki.gogrid.com/wiki/index.php/API:grid.job.get&quot; rel=&quot;nofollow&quot;&gt;http://wiki.gogrid.com/wiki/index.php/API:grid.jo...&lt;/a&gt; 
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 &nbsp;have, however, sent this information on to our Product team for possible inclusion in future releases. 
 
Thanks, 
 Michael ]]></description>
		<content:encoded><![CDATA[<p>Thanks for the note Craig. </p>
<p>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:<br />
<a href="http://wiki.gogrid.com/wiki/index.php/API:grid.job.list" rel="nofollow"></a><a href="http://wiki.gogrid.com/wiki/index.php/API:grid.jo" rel="nofollow">http://wiki.gogrid.com/wiki/index.php/API:grid.jo</a>&#8230;<br />
and<br />
<a href="http://wiki.gogrid.com/wiki/index.php/API:grid.job.get" rel="nofollow"></a><a href="http://wiki.gogrid.com/wiki/index.php/API:grid.jo" rel="nofollow">http://wiki.gogrid.com/wiki/index.php/API:grid.jo</a>&#8230;<br />
If you use those methods, you could conceivably pull out the jobs to an external system for event integration. </p>
<p>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 &amp;nbsp;have, however, sent this information on to our Product team for possible inclusion in future releases. </p>
<p>Thanks,<br />
 Michael </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Balding</title>
		<link>http://blog.gogrid.com/2009/04/10/new-feature-job-history-%e2%80%93-a-log-file-for-gogrid/#comment-1519</link>
		<dc:creator>Craig Balding</dc:creator>
		<pubDate>Fri, 10 Apr 2009 23:02:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gogrid.com/?p=859#comment-1519</guid>
		<description><![CDATA[OK so I assume GoGrid captures the source IPs of requests when API calls are made, just that you&#039;re not exposing that information via your API/web interface.  Thanks, Craig ]]></description>
		<content:encoded><![CDATA[<p>OK so I assume GoGrid captures the source IPs of requests when API calls are made, just that you&#039;re not exposing that information via your API/web interface.  Thanks, Craig </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig Balding</title>
		<link>http://blog.gogrid.com/2009/04/10/new-feature-job-history-%e2%80%93-a-log-file-for-gogrid/#comment-1516</link>
		<dc:creator>Craig Balding</dc:creator>
		<pubDate>Fri, 10 Apr 2009 20:50:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.gogrid.com/?p=859#comment-1516</guid>
		<description><![CDATA[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&#039;t see any mention of source IP (especially for API requests) - is that included in the customer facing log? 
 
Cheers 
 
Craig ]]></description>
		<content:encoded><![CDATA[<p>Hi, this looks a good step around visibility.  2 questions:<br />
- can the log be pushed/pulled in near real-time to an enterprise SEIM? (i.e. enterprise event integration)<br />
- didn&#039;t see any mention of source IP (especially for API requests) &#8211; is that included in the customer facing log? </p>
<p>Cheers </p>
<p>Craig </p>
]]></content:encoded>
	</item>
</channel>
</rss>
