Spryker analytics

[andriitserkovnyi]

PR Description

Docs for spryker analytics

Steps before you submit a PR

• Please add tests for the code you add if it's possible.
• Please check out our contribution guide: https://docs.spryker.com/docs/dg/dev/code-contribution-guide.html
• Add a contribution-license-agreement.txt file with the following content:
  I hereby agree to Spryker\'s Contribution License Agreement in https://github.com/spryker/spryker-docs/blob/HASH_OF_COMMIT_YOU_ARE_BASING_YOUR_BRANCH_FROM_MASTER_BRANCH/CONTRIBUTING.md.

This is a mandatory step to make sure you are aware of the license agreement and agree to it. HASH_OF_COMMIT_YOU_ARE_BASING_YOUR_BRANCH_FROM_MASTER_BRANCH is a hash of the commit you are basing your branch from the master branch. You can take it from commits list of master branch before you submit a PR.

Checklist

• I agree with the Code Contribution License Agreement in CONTRIBUTING.md

[mikost7]

let's please add here a small section talking about SPICE (https://docs.aws.amazon.com/quicksight/latest/user/spice.html)

I think users need to understand what it is in general, as it is a paid line item (500 GB is included, we don't have to mention it) in the QS SKU.

the main idea is to talk about the benefits of SPICE:
(from AWS page):

• Your analytical queries process faster.
• You don't need to wait for a direct query to process.
• Data stored in SPICE can be reused multiple times without incurring additional costs. If you use a data source that charges per query, you're charged for querying the data when you first create the dataset and later when you refresh the dataset.

[mikost7]

we also need to add the possibility on how to check the current SPICE usage in the top right corner under QS > Datasets > New Dataset.

[andriitserkovnyi]

Are you referring to this?

[mikost7]

Yes, I believe it is the only way how to check the capacity for the customer.