docs: Clarify the effects of auto-suspension

Author: igorlukanin

docs/docs-new/pages/product/deployment/cloud/auto-suspension.mdx

@@ -12,12 +12,18 @@ Auto-suspension is available in Cube Cloud on
 
 </SuccessBox>
 
-Cube Cloud can automatically suspend deployments when not in use to prevent
-[resource consumption][ref-deployment-pricing] when infrastructure is not being
-actively used, which helps manage spend and preventing unnecessary quota use.
+Cube Cloud can automatically suspend deployments when not in use to reduce
+[resource consumption][ref-deployment-pricing], which helps manage your spend.
 
-This is useful for deployments that are not used 24/7, such as staging
-deployments. Auto-suspension will hibernate the deployment when **no** API
+<WarningBox>
+
+Auto-suspension is useful for deployments that are not used 24/7, such as
+staging deployments. However, **auto-suspension shall not be used for production
+deployments**. See [effects on experience][self-effects] for details.
+
+</WarningBox>
+
+Auto-suspension will hibernate the deployment when **no** API
 requests are received after a period of time, and automatically resume the
 deployment when API requests start coming in again:
 
@@ -38,6 +44,25 @@ During auto-suspension, resources are monitored in 5 minute intervals. This
 means that if a deployment was suspended 4 minutes ago, and a request comes in,
 the deployment will resume immediately and 5 minute of CCU usage will be billed.
 
+## Effects on experience
+
+If auto-suspension is enabled, the behavior of your Cube Cloud deployment will
+experience some notable changes.
+
+When a deployment is auto-suspended:
+
+- [Data model][ref-data-model] compilation artifacts are discarded since the
+API instances are de-provisioned.
+- [Monitoring integrations][ref-monitoring] are also suspended, which prevents
+the export of metrics and logs.
+
+When a deployment is resumed from auto-suspension:
+
+- [Data model][ref-data-model] compilation would need to be done from scratch.
+It applies to all tenants in case [multitenancy][ref-multitenancy] is set up.
+Consequently, one or more queries served after a deployment is resumed from
+auto-suspension are likely to have suboptimal performance.
+
 ## Configuration
 
 To configure auto-suspension settings, navigate to the <Btn>Settings</Btn>
@@ -94,3 +119,7 @@ response times to be significantly longer than usual.
   /product/deployment/cloud/deployment-types#production-multi-cluster
 [ref-deployment-pricing]: /product/deployment/cloud/pricing
 [ref-workspace-dev-api]: /product/workspace/dev-mode
+[ref-monitoring]: /product/monitoring/integrations
+[ref-data-model]: /product/data-modeling/overview
+[ref-multitenancy]: /product/configuration/advanced/multitenancy
+[self-effects]: #effects-on-experience

docs/docs-new/pages/product/monitoring/integrations.mdx

@@ -25,6 +25,12 @@ deployments.
 
 </InfoBox>
 
+<WarningBox>
+
+Monitoring integrations suspend their work when a deployment goes to [auto-suspension][ref-autosuspend].
+
+</WarningBox>
+
 Under the hood, Cube Cloud uses [Vector][vector], an open-source tool for
 collecting and delivering monitoring data. It supports a [wide range of
 destinations][vector-docs-sinks], also known as _sinks_.
@@ -243,13 +249,7 @@ You can also customize the user name and password for `prometheus_exporter` by
 setting `CUBE_CLOUD_MONITORING_METRICS_USER` and
 `CUBE_CLOUD_MONITORING_METRICS_PASSWORD` environment variables, respectively.
 
-## Auto-suspend behavior
-
-If [auto-suspension][ref-deploy-autosuspend] is enabled for a deployment with
-configured monitoring integrations, then the integrations will also be
-suspended, which prevents the export of metrics and logs.
-
-[ref-deploy-autosuspend]: /product/deployment/cloud/auto-suspension
+[ref-autosuspend]: /product/deployment/cloud/auto-suspension#effects-on-experience
 [self-sinks-for-metrics]: #configuration-sinks-for-metrics
 [ref-vpc]: /product/configuration/vpc
 [vector]: https://vector.dev/