Stopped Docker jobs

Due to a spike in AWS SPOT instances price our Docker workers were shut down around 12am UTC. This affects all jobs that are running on Docker components. We're working on fixing this issue and hope to resume all operations shortly. Thanks for your patience.

Update 04:30am UTC: All operations back to normal, all jobs should have resumed their execution. There was a minor failure with a Docker image for Generic Extractor, some of its jobs have failed with this error

User error: Container 'keboola/docker-generic-extractor:latest' failed: no such file or directory Error response from daemon: Cannot start container 08763383d5370bcdd6e1479da00ae369fe5d845c33485df5337239cc7bdd9c90: [8] System error: no such file or directory

This issue is now fixed and if you have encountered this error, please restart the job. 

Thanks for bearing with us and we're sorry for the inconvenience. 

Data Takeout

As a part of our commitment to openness and total, utter and complete aversion to "customer lock in" tactics, we introduced a "Data Takeout" functionality. It's been around for awhile actually, but now it is right there in the UI. This means that shall our customer become less than completely satisfied with us, there's no technical barrier for them to collect all their data AND the project structure (including all transformation scripts and queries etc.) at a push of a button. (And yeah, we took a hint from Google on how to call the service.)

What this button does is to export everything into AWS Simple Storage Service (S3).

Several files will be created there, which will contain:

  • All bucket and table metadata (attributes, names, columns, settings)
  • All table data exported to gzipped CSV files
  • All component configurations (e.g. transformation configuration with all queries, database extractor settings and queries, etc.)

Export can be limited only to metadata and configurations and the "Data Take Out" button can be found at Users & Settings page.


GoodData Writer Failures

There is some problem on GoodData API since about 12:00 CEST (10:00 UTC) which causes failures on some model updates and data loads. We are investigating the problem with GoodData support and will keep you updated.

UPDATE 16:15 CEST GoodData support is still investigating the problem but our logs show that it didn't appear again almost three hours. Preliminary report indicates that they had some troubles with connection to S3 storage where LDM models of projects are stored.

AdWords Extractor Update

New version v201509 of AdWords API has been released recently and our extractor will update in the beginning of November. Please be sure to review your configuration so that it does not use unsupported metric names till the end of October. Also do not use new metrics until the update, we will let you know about it.