hauser icon indicating copy to clipboard operation
hauser copied to clipboard

Service for moving your FullStory export files to a data warehouse

Results 8 hauser issues
Sort by recently updated
recently updated
newest added

Just opening an issue to track this feature request.

Have you ever caught below error? The environment is AWS S3, Redshift after the docker run. Failed to process exports: failed to create sync file reader: failed to read s3...

This recipe provides a script that deploys a recommended hauser deployment to GKE, including a service account with "least privilege".

Added a note about necessary FullStory API permission levels for the API key as well as change the note for StartTime as it errors with the pre-existing empty string while...

I'd like to suggest adding a config parameter to make the "sleep until an export is ready" behavior optional. This would be very useful in the case where a long-running...

I am getting repeated error messages like: ``` 16:20:34 Processing bundle 156453120048 (start: 2019-07-31 00:00:00 +0000 UTC, end: 2019-08-01 00:00:00 +0000 UTC) 16:20:34 Getting Export Data for bundle 156453120048 16:30:36...

This doesn't work for Amazon RedShift yet, but should serve as a good jumping-off point to get it started Executable container is available at `quay.io/jewlr/hauser`