Keboola Status

Have you ever used Sailthru and are you interested in analysis of your campaign data? If you answer is positive in both cases, you might be happy for this new extension to the Keboola Connection family - Sailthru Campaign Extractor. 

As title says, the extractor is able to download your campaign data and datasets like beacon times, devices, domains, engagement, just to name a few (you can see the full list in the documentation).

The configuration of this extractor is very simple and a lot of things are happening 'under the hood'. The output datasets are aggregated and some of them contain some additional information, just for your convenient to potentially simplify your analytics queries in Keboola Connection (at least a little bit). During the development there was a big focus on extensibility and for that reason there is a high probability there will be a new set of cool features in the future. 

The development was sponsored by Pond5 and developed independently by Radek Tomášek. I would love to thank Petr Havlik for his tremendous support during the whole development process. His experience made the whole development easier. For more information on how to use the extractor, please refer to the documentation.

It is my pleasure to announce a new extension to a Keboola Connection component family - Ooyala Video Analytics Extractor, which will help you with the extraction of the analytical data from Ooyala Analytical backend.

The component has quite flexible options for the configuration and you can get (aggregated) data based on various metrics and timeframes. 

There are also a lot of things for your convenient on the Ooyala backend. A good example are the error messages, if you put something unexpected into the configuration, the backend will raise a very specific response which helps you to debug the configuration easily.

This writer is developed independently by Blue Sky Media. For more information on how to use the writer, please refer to the documentation. In case you run into some issues or you have more questions, please contact me directly. 

Recently, there was an announcement from Apple about their plans to deprecate the iTunes Connect Autoingest tool by the end of November, 2016. They also mentioned the new way how to download financial and sales data from their APIs and for that reason they made available the new Reporter API.

In order to avoid any potential problems, it is my pleasure to announce that the iTunes Connect Extractor was updated and from now on it started using the new APIs which helps you to keep downloading data from the Apple reporting without any problem.

The new set of APIs is not the only change. I focused all my effort on simplicity and simplified the way how to pass the input params into Keboola. That means a lot of bigger things are now managed 'under the hood' and you don't to worry much about it. For instance, if you start selling the content in any new country, the extraction process will handle that and you will see the new region in your Keboola Storage object automatically. 

This writer is developed independently by Blue Sky Media. For more information on how to use the extractor, please refer to the documentation. In case you run into some issues or you have more questions, please contact me directly. 

We're encountering difficulties with our MySQL transformation server, some jobs are ending up with an application exception. We're closely monitoring this issue and restarting all failed orchestrations until the situation gets stable.

We're sorry for any inconvenience.

We're affected by DockerHub and Quay.io Service Disruption. Some components are failing. 

We'll update this post once the disruption is over and will restart all affected orchestrations.

You can also check the official DockerHub status page and Quay.IO status page for more information.

We're sorry for this inconvenience.

UPDATE: The Quay.IO disruption is over.

Between Oct 26 10:40am UTC and Oct 26 12:50am UTC we encountered issues connecting to Snowflake. 

Some jobs might have ended with Internal error or one of these exceptions:

• The error message SFExecuteQueryFailed could not be found in the en-US locale. Check that /en-US/SFMessages.xml exists., SQL state S1000 in SQLPrepare
• Failed to execute query. Error code=-1, GS error code=601, GS error message=Service temporarily unavailable. Retry the request later.
  

We're investigating the root cause with Snowflake support and identifying and restarting affected orchestrations. 

We have created a new currency exchange rate extractor. This component allows you to extract currency exchange rates as published by European Central Bank (ECB). Its configuration is dead simple, all you need to do is select the source currency (USD and EUR are currently supported).

Migration

This extractor provides the same data in the same format as the old extractor (which had to be configured through support). We encourage you to switch to the new one - set it up as any other extractor. We will keep running the old extractor till January 2017. Just let us know once you don't need it, so that we can deactivate it and stop magically pushing data to your project.

Like in the old currency extractor, the resulting data contains gaps for bank holidays (including weekends). If you would like to fill the gaps with last known value, you can use a little SQL script we hacked together.

We're encountering a higher number of "Output mapping does not match destination table" errors in applications today since 10:30am. This was caused by deploying strict validation in output mapping. Our detection script did not detect and prevent all cases, so we're rolling back this release and restarting all affected orchestrations.

We're sorry for this inconvenience.

On October 21, 2016 at 11:43:58 PM CEST/UTC+2 one of our database servers was restarted due to a hardware failure. Jobs running during that time failed when trying to reconnect to the database later in the processing.

Update October 21, 2016 at 01:20 AM CEST/UTC+2: Jobs/orchestrations affected with this restart didn't stop processing and finished successfully, they may show incorrect job result as error instead of success.

We're sorry for this inconvenience and we're restarting all failed orchestrations.

We have investigated issues with Amazon DNS service in us-east region.

It affects jobs processing and API availability of our components. Thanks for patience.

UPDATE: 

AWS confirmed the problem - 5:15 AM PDT We are investigating elevated errors resolving the DNS hostname used to access the EC2 APIs.

AWS status update - 5:51 AM PDT We have identified the root cause of the issue causing errors resolving the DNS hostname used to access the EC2 APIs and are currently working to resolve.