patrick-fs/segment-export-cli

CLI for FullStory segment export

segment-export-cli's Issues

Always returns 403

Hi @patrick-fs,

Thx for creating this. Really helps to understand how FS export works.

I have tried it with a FS admin apikey but it never seems to work for me. Always throwing a 403.

Is there something I need to be aware of?

Thanks,
Temi

Retry on HTTP 429 responses

Per the limits outlined here, retry requests when HTTP 429 status codes are returned in the response: https://developer.fullstory.com/get-data-export

This will still need to work with the concurrent request strategy that has already been implemented.

Dependant on this PR going to prod: https://github.com/cowpaths/mn/pull/21448

Define the interval size via a flag

Right now, the interval size is hard-coded to 15 minutes. Make this size configurable via an --interval flag that has the following options (minutes):

• 5
• 10
• 15
• 30
• 60

Add instructions for getting the segment ID

Include a screen grab of the FullStory search UI as well as a visual pointer to the segment ID in the URL.

Add to the Readme.

Default start flag value

Right now, the --start flag is required. Choose a reasonable default (maybe 30 days in the past?) when --start is not provided.

Default ID argument value

Right now the ID argument is required. Use the everyone segment as the default value.

Restart from latest file downloaded

When the CLI is run, check the output directory to see if there are any existing files and use the latest file name (files are named according to ISO datetime standard) as the start parameter for downloading additional files.

One thing to consider: any contention between the --start flag value and the latest file downloaded. How to handle?