diff --git a/_partials/_devops-cli-service-forks.md b/_partials/_devops-cli-service-forks.md new file mode 100644 index 0000000000..88708ebc17 --- /dev/null +++ b/_partials/_devops-cli-service-forks.md @@ -0,0 +1,61 @@ +import CLIINSTALL from "versionContent/_partials/_devops-cli-install.mdx"; + +To manage development forks: + + + + + +1. **Fork the $SERVICE_SHORT** + + ```shell + tiger service fork tgrservice --now --no-wait --name bob + ``` + By default a fork matches the resource of the parent $SERVICE_LONGs. For paid plans specify `--cpu` and/or `--memory` for dedicated resources. + + You see something like: + + ```terminaloutput + 🍴 Forking service 'tgrservice' to create 'bob' at current state... + ✅ Fork request accepted! + 📋 New Service ID: + 🔐 Password saved to system keyring for automatic authentication + 🎯 Set service '' as default service. + ⏳ Service is being forked. Use 'tiger service list' to check status. + ┌───────────────────┬──────────────────────────────────────────────────────────────────────────────────────────────────┐ + │ PROPERTY │ VALUE │ + ├───────────────────┼──────────────────────────────────────────────────────────────────────────────────────────────────┤ + │ Service ID │ │ + │ Name │ bob │ + │ Status │ │ + │ Type │ TIMESCALEDB │ + │ Region │ eu-central-1 │ + │ CPU │ 0.5 cores (500m) │ + │ Memory │ 2 GB │ + │ Direct Endpoint │ ..tsdb.cloud.timescale.com: │ + │ Created │ 2025-10-08 13:58:07 UTC │ + │ Connection String │ postgresql://tsdbadmin@..tsdb.cloud.timescale.com:/tsdb?sslmode=require │ + └───────────────────┴──────────────────────────────────────────────────────────────────────────────────────────────────┘ + ``` + +1. **When you are done, delete your forked $SERVICE_SHORT** + + 1. Use the CLI to request $SERVICE_SHORT delete: + + ```shell + tiger service delete + ``` + 1. Validate the $SERVICE_SHORT delete: + + ```terminaloutput + Are you sure you want to delete service ''? This operation cannot be undone. + Type the service ID '' to confirm: + + ``` + You see something like: + ```terminaloutput + 🗑️ Delete request accepted for service ''. + ✅ Service '' has been successfully deleted. + ``` + + \ No newline at end of file diff --git a/_partials/_manage-a-data-exporter.md b/_partials/_manage-a-data-exporter.md index 96d7cc4641..de90b1d41c 100644 --- a/_partials/_manage-a-data-exporter.md +++ b/_partials/_manage-a-data-exporter.md @@ -109,4 +109,4 @@ It must be one of the following: [console-cloudwatch-configuration]: https://console.aws.amazon.com/cloudwatch/home#logsV2:log-groups [console-cloudwatch-create-group]: https://console.aws.amazon.com/cloudwatch/home#logsV2:log-groups/create-log-group [services-portal]: https://console.cloud.timescale.com/dashboard/services -[pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-plan +[pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-pricing-plan diff --git a/_partials/_prometheus-integrate.md b/_partials/_prometheus-integrate.md index 62307cdb28..f8ded461d2 100644 --- a/_partials/_prometheus-integrate.md +++ b/_partials/_prometheus-integrate.md @@ -209,4 +209,4 @@ You can further [visualize your data][grafana-prometheus] with Grafana. Use the [enable-timescaledb]: /self-hosted/:currentVersion:/install/ [prometheus-authentication]: https://prometheus.io/docs/guides/basic-auth/ [scrape-targets]: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#scrape_config -[pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-plan +[pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-pricing-plan diff --git a/about/changelog.md b/about/changelog.md index 9c27be4557..7f2b229558 100644 --- a/about/changelog.md +++ b/about/changelog.md @@ -919,7 +919,7 @@ Highlighted features in TimescaleDB v2.17 are: ### HIPAA compliance -Timescale Cloud's [Enterprise plan](https://docs.timescale.com/about/latest/pricing-and-account-management/#features-included-in-each-plan) is now HIPAA (Health Insurance Portability and Accountability Act) compliant. This allows organizations to securely manage and analyze sensitive healthcare data, ensuring they meet regulatory requirements while building compliant applications. +Timescale Cloud's [Enterprise plan](https://docs.timescale.com/about/latest/pricing-and-account-management/#features-included-in-each-pricing-plan) is now HIPAA (Health Insurance Portability and Accountability Act) compliant. This allows organizations to securely manage and analyze sensitive healthcare data, ensuring they meet regulatory requirements while building compliant applications. ### Expanded logging within Timescale Console diff --git a/about/pricing-and-account-management.md b/about/pricing-and-account-management.md index 0ba87ada6b..42e9b38d5b 100644 --- a/about/pricing-and-account-management.md +++ b/about/pricing-and-account-management.md @@ -224,7 +224,7 @@ When you get $CLOUD_LONG at AWS Marketplace, the following pricing options are a [cloud-billing]: https://console.cloud.timescale.com/dashboard/billing/details [commercial-sla]: https://www.timescale.com/legal/timescale-cloud-terms-of-service [pricing-plans]: https://www.timescale.com/pricing -[plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-plan +[plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-pricing-plan [production-support]: https://www.timescale.com/support [hipaa-compliance]: https://www.hhs.gov/hipaa/for-professionals/index.html [aws-pricing]: /about/:currentVersion:/pricing-and-account-management/#aws-marketplace-pricing diff --git a/ai/index.md b/ai/index.md index df59104433..9fa6044fcf 100644 --- a/ai/index.md +++ b/ai/index.md @@ -1,6 +1,6 @@ --- title: Integrate AI with Tiger Data -excerpt: Build AI assistants with Tiger Data using pgvector, Tiger Eon, Tiger Agents, and MCP server for seamless data integration +excerpt: Build AI Assistants with Tiger Data using pgvector, Tiger Eon, Tiger Agents, and MCP server for seamless data integration products: [cloud, mst, self_hosted] keywords: [ai, vector, pgvector, pgvectorscale, pgai, tiger-eon, tiger-agents, mcp-server] tags: [ai, vector, agents, assistants] @@ -54,7 +54,7 @@ The [$MCP_LONG](/ai/:currentVersion:/mcp-server/) integrates directly with popul - Access comprehensive $COMPANY documentation during development - Use secure authentication and access control -Use the $MCP_SHORT when you want to manage $COMPANY resources from your AI assistant. +Use the $MCP_SHORT when you want to manage $COMPANY resources from your AI Assistant. diff --git a/getting-started/page-index/page-index.js b/getting-started/page-index/page-index.js index d33b812fad..459e52ec0e 100644 --- a/getting-started/page-index/page-index.js +++ b/getting-started/page-index/page-index.js @@ -23,7 +23,7 @@ module.exports = [ excerpt: "Create a Tiger service and connect to it", }, { - title: "DevOps as code with Tiger", + title: "DevOps as code with Tiger Cloud", href: "get-started-devops-as-code", excerpt: "Set up secure authentication for the Tiger REST API and create your first service", }, diff --git a/integrations/cloudwatch.md b/integrations/cloudwatch.md index 9901a0a9a1..5872b81e60 100644 --- a/integrations/cloudwatch.md +++ b/integrations/cloudwatch.md @@ -34,7 +34,7 @@ tool. You create an exporter on the [project level][projects], in the same AWS r [projects]: /use-timescale/:currentVersion:/security/members/ -[pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-plan +[pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-pricing-plan [cloudwatch]: https://aws.amazon.com/cloudwatch/ [cloudwatch-signup]: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/GettingSetup.html diff --git a/integrations/datadog.md b/integrations/datadog.md index 7cad45fca8..060690d0eb 100644 --- a/integrations/datadog.md +++ b/integrations/datadog.md @@ -143,7 +143,7 @@ comprehensive list of [metrics][datadog-postgres-metrics] collected. [datadog-agent-restart]: https://docs.datadoghq.com/agent/configuration/agent-commands/#start-stop-and-restart-the-agent [projects]: /use-timescale/:currentVersion:/security/members/ [datadog-api-key]: https://docs.datadoghq.com/account_management/api-app-keys/#add-an-api-key-or-client-token -[pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-plan +[pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-pricing-plan [run-queries]: /getting-started/:currentVersion:/run-queries-from-console/ [open-console]: https://console.cloud.timescale.com/dashboard/services [psql]: /integrations/:currentVersion:/psql/ diff --git a/use-timescale/backup-restore.md b/use-timescale/backup-restore.md index 4c81a15a70..92a7cba99a 100644 --- a/use-timescale/backup-restore.md +++ b/use-timescale/backup-restore.md @@ -1,24 +1,31 @@ --- -title: Back up and recover your Tiger services -excerpt: See how and when Tiger backs up your data, making sure you always have something to fall back on in case of disaster recovery +title: Back up and recover services +excerpt: Tiger Cloud backs up your data, making sure you always have something to fall back on for disaster recovery products: [cloud] keywords: [backups, restore] tags: [recovery, failures] --- -# Back up and recover your $SERVICE_SHORTs +import CLIFORKS from "versionContent/_partials/_devops-cli-service-forks.mdx"; -$CLOUD_LONG automatically handles backup for your $SERVICE_LONGs using the `pgBackRest` tool. You don't need to perform backups manually. What's more, with [cross-region backup][cross-region], you are protected when an entire AWS region goes down. +# Back up and recover $SERVICE_SHORTs -$CLOUD_LONG automatically creates one full backup every week, and -incremental backups every day in the same region as your $SERVICE_SHORT. +$CLOUD_LONG provides comprehensive backup and recovery solutions to protect your data, including automatic daily backups, +cross-region protection, and point-in-time recovery. -On [$SCALE and $PERFORMANCE][pricing-and-account-management] $PRICING_PLANs, you can check the list of backups for the previous 14 days in $CONSOLE_LONG. To do so, select your $SERVICE_SHORT, then click `Operations` > `Backup and restore` > `Backup history`. +## Automatic backups + +$CLOUD_LONG automatically handles backup for your $SERVICE_LONGs using the `pgBackRest` tool. You don't need to perform +backups manually. What's more, with [cross-region backup][cross-region], you are protected when an entire AWS region goes down. -Additionally, all [Write-Ahead Log (WAL)][wal] files are retained back to the oldest full backup. This means that you always have a full backup available for the current and previous week: +$CLOUD_LONG automatically creates one full backup every week, and incremental backups every day in the same region as +your $SERVICE_SHORT. Additionally, all [Write-Ahead Log (WAL)][wal] files are retained back to the oldest full backup. +This means that you always have a full backup available for the current and previous week: ![Backup in Tiger](https://assets.timescale.com/docs/images/database-backup-recovery.png) +On [$SCALE and $PERFORMANCE][pricing-and-account-management] $PRICING_PLANs, you can check the list of backups for the previous 14 days in $CONSOLE_LONG. To do so, select your $SERVICE_SHORT, then click `Operations` > `Backup and restore` > `Backup history`. + In the event of a storage failure, a $SERVICE_SHORT automatically recovers from a backup to the point of failure. If the whole availability zone goes down, your $SERVICE_LONGs are recovered in a different zone. In the event of a user error, you can [create a point-in-time recovery fork][create-fork]. @@ -101,6 +108,7 @@ You initiate a point-in-time recovery from a same-region or cross-region backup 1. Confirm by clicking `Create recovery fork`. A fork of the $SERVICE_SHORT is created. The recovered $SERVICE_SHORT shows in `Services` with a label specifying which $SERVICE_SHORT it has been forked from. + 1. Update the connection strings in your app Since the point-in-time recovery is done in a fork, to migrate your @@ -120,6 +128,11 @@ You initiate a point-in-time recovery from a same-region or cross-region backup +## Create a service fork + + + + [console]: https://console.cloud.timescale.com/dashboard/services [ha-replicas]: /about/use-timescale/:currentVersion:/ha-replicas/ [pricing-and-account-management]: /about/:currentVersion:/pricing-and-account-management/ diff --git a/use-timescale/configuration/customize-configuration.md b/use-timescale/configuration/customize-configuration.md index 4b1644c95e..1ba8aca724 100644 --- a/use-timescale/configuration/customize-configuration.md +++ b/use-timescale/configuration/customize-configuration.md @@ -62,4 +62,4 @@ width={1375} height={944} src="https://assets.timescale.com/docs/images/tsc-settings-confirm.webp" alt="Confirm Tiger configuration changes"/> -[plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-plan \ No newline at end of file +[plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-pricing-plan \ No newline at end of file diff --git a/use-timescale/fork-services.md b/use-timescale/fork-services.md new file mode 100644 index 0000000000..d235281abd --- /dev/null +++ b/use-timescale/fork-services.md @@ -0,0 +1,184 @@ +--- +title: Fork services +excerpt: With developer forks, spin up a branch, run your test, throw it away, or merge it back. +products: [cloud] +price_plans: [performance, scale, enterprise] +keywords: [backups, restore] +tags: [recovery, failures] +--- + +import IntegrationPrereqs from "versionContent/_partials/_integration-prereqs.mdx"; +import CLIFORKS from "versionContent/_partials/_devops-cli-service-forks.mdx"; + +# Fork $SERVICE_SHORTs + +Modern development is highly iterative. Developers and AI agents need safe spaces to test changes before deploying them +to production. Forkable $SERVICE_SHORTs make this natural and easy. Spin up a branch, run your test, throw it away, or +merge it back. + +A fork is an exact copy of a $SERVICE_SHORT at a specific point in time, with its own independent data and configuration, +including: +- The database data and schema +- Configuration +- An admin `tsdbadmin` user with a new password + +Forks are fully independent. Changes to the fork don't affect the parent $SERVICE_SHORT. You can query +them, run migrations, add indexes, or test new features against the fork without affecting the original service. + +Forks are a powerful way to share production-scale data safely. Testing, BI and data science teams often need access +to real datasets to build models or generate insights. With forkable $SERVICE_SHORTs, you easily create fast, zero-copy +branches of a production $SERVICE_SHORT that are isolated from production, but contain all the data needed for +analysis. Rapid fork creation dramatically reduces friction getting insights from live data. + +## Understand $SERVICE_SHORT forks + +You can use $SERVICE_SHORT forks for disaster recovery, CI/CD automation, and testing and development. For example, you +can automatically test a major $PG upgrade on a fork before applying it to your production $SERVICE_SHORT. + +$CLOUD_LONG offers the following fork strategies: + +- `now`: create a fresh fork of your database at the current time. + Use when: + - You need the absolute latest data + - Recent changes must be included in the fork + +- `last-snapshot`: fork from the most recent [automatic backup or snapshot][automatic-backups]. + Use when: + - You want the fastest possible fork creation + - Slightly behind current data is acceptable + +- `timestamp`: fork from a specific point in time within your [retention period][pricing]. + Use when: + - Disaster recovery from a known-good state + - Investigating issues that occurred at a specific time + - Testing "what-if" scenarios from historical data + +The retention period for point-in-time recovery and forking depends on your [pricing plan][pricing-plan-features]. + +### Fork creation speed + +Fork creation speed depends on your type of service you want to create: + +- Free: ~30-90 seconds. Uses a Copy-on-Write storage architecture with zero-copy between a fork and the parent. +- Paid: varies with the size of your $SERVICE_SHORT, typically 5-20+ minutes. Uses tradional storage architecture + with backup restore + WAL replay. + +### Billing + +You can fork a free $SERVICE_SHORT to a free or a paid $SERVICE_SHORT. However, you cannot fork a paid +$SERVICE_SHORT to a free $SERVICE_SHORT. + +Billing on storage works in the following way: + +- High-performance storage: + - Copy-on-Write: you are only billed for storage for the chunks that diverge from the parent $SERVICE_SHORT. + - Traditional: you are billed for storage for the whole $SERVICE_SHORT. +- Object storage tier: + - [Tiered data][data-tiering] is shared across forks using copy-on-write and traditional storage: + - Chunks in tiered storage are only billed once, regardless of the number of forks + - Only new or modified chunks in a fork incur additional costs + +For details, see [Replicas and forks with tiered data][tiered-forks]. + +## Prerequisites + + + +## Manage forks using $CLI_LONG + + + +## Manage forks using $CONSOLE_SHORT + +To manage development forks: + + + +1. In [$CONSOLE][console], from the `Services` list, ensure the $SERVICE_SHORT + you want to recover has a status of `Running` or `Paused`. +1. Navigate to `Operations` > `Service Management` and click `Fork service`. +1. Configure the fork, then click `Fork service`. + + A fork of the $SERVICE_SHORT is created. The forked $SERVICE_SHORT shows in `Services` with a label + specifying which $SERVICE_SHORT it has been forked from. + + ![See the forked service](https://assets.timescale.com/docs/images/tsc-forked-service.webp) + +1. Update the connection strings in your app to use the fork. + + + +## Integrate $SERVICE_SHORT forks in your CI/CD pipeline + +To fork your $SERVICE_LONG using GitHub actions: + + + +1. **Store your $CLOUD_LONG API key as a GitHub Actions secret** + + 1. In [$CONSOLE_LONG][rest-api-credentials], click `Create credentials`. + 2. Save the `Public key` and `Secret key` locally, then click `Done`. + 1. In your GitHub repository, click `Settings`, open `Secrets and variables`, then click `Actions`. + 3. Click `New repository secret`, then set `Name` to `TIGERDATA_API_KEY` + 4. Set `Secret` to your $CLOUD_LONG API key in the following format `:`, then click `Add secret`. + +1. **Add the [GitHub Actions Marketplace][github-action] to your workflow YAML files** + + For example, the following workflow forks a $SERVICE_SHORT when a pull request is opened, + running tests against the fork, then automatically cleans up. + + ```yaml + name: Test on a service fork + on: pull_request + + jobs: + test: + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v4 + + - name: Fork Database + id: fork + uses: timescale/fork-service@v1 + with: + project_id: ${{ secrets.TIGERDATA_PROJECT_ID }} + service_id: ${{ secrets.TIGERDATA_SERVICE_ID }} + api_key: ${{ secrets.TIGERDATA_API_KEY }} + fork_strategy: last-snapshot + cleanup: true + name: pr-${{ github.event.pull_request.number }} + + - name: Run Integration Tests + env: + DATABASE_URL: postgresql://tsdbadmin:${{ steps.fork.outputs.initial_password }}@${{ steps.fork.outputs.host }}:${{ steps.fork.outputs.port }}/tsdb?sslmode=require + run: | + npm install + npm test + - name: Run Migrations + env: + DATABASE_URL: postgresql://tsdbadmin:${{ steps.fork.outputs.initial_password }}@${{ steps.fork.outputs.host }}:${{ steps.fork.outputs.port }}/tsdb?sslmode=require + run: npm run migrate + ``` + + For the full list of inputs, outputs, and configuration options, see the [Tiger Data - Fork Service][github-action] in GitHub marketplace. + + + +[console]: https://console.cloud.timescale.com/dashboard/services +[ha-replicas]: /about/use-timescale/:currentVersion:/ha-replicas/ +[pricing-and-account-management]: /about/:currentVersion:/pricing-and-account-management/ +[wal]: https://www.postgresql.org/docs/current/wal-intro.html +[support]: https://www.timescale.com/contact/ +[pitr]: /use-timescale/:currentVersion:/backup-restore/point-in-time-recovery/ +[rapid-recovery]: /use-timescale/:currentVersion:/ha-replicas/#rapid-recovery +[cross-region]: /use-timescale/:currentVersion:/backup-restore#enable-cross-region-backup +[create-fork]: /use-timescale/:currentVersion:/backup-restore#recover-your-data-in-a-point-in-time-fork +[automatic-backups]: /use-timescale/:currentVersion:/backup-restore/ +[pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-pricing-plan +[data-tiering]: /use-timescale/:currentVersion:/data-tiering/ +[tiered-forks]: /use-timescale/:currentVersion:/data-tiering/tiered-data-replicas-forks/ +[github-action]: https://github.com/marketplace/actions/tiger-data-fork-service +[delete-action]: https://github.com/marketplace/actions/tiger-data-delete-service +[connection-details]: /integrations/:currentVersion:/find-connection-details/ +[upgrades]: /use-timescale/:currentVersion:/upgrades/ +[rest-api-credentials]: https://console.cloud.timescale.com/dashboard/settings \ No newline at end of file diff --git a/use-timescale/metrics-logging/aws-cloudwatch.md b/use-timescale/metrics-logging/aws-cloudwatch.md index 6368a212ee..2b3fb68ea2 100644 --- a/use-timescale/metrics-logging/aws-cloudwatch.md +++ b/use-timescale/metrics-logging/aws-cloudwatch.md @@ -40,5 +40,5 @@ This section shows you how to attach, monitor, edit, and delete a data exporter. [console-integrations]: https://console.cloud.timescale.com/dashboard/integrations [console-services]: https://console.cloud.timescale.com/dashboard/services [services-portal]: https://console.cloud.timescale.com/dashboard/services -[pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-plan +[pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-pricing-plan [projects]: /use-timescale/:currentVersion:/security/members/ \ No newline at end of file diff --git a/use-timescale/metrics-logging/datadog.md b/use-timescale/metrics-logging/datadog.md index 96c658bbb1..992c60ccca 100644 --- a/use-timescale/metrics-logging/datadog.md +++ b/use-timescale/metrics-logging/datadog.md @@ -41,5 +41,5 @@ This section shows you how to attach, monitor, edit, and delete a data exporter. [console-integrations]: https://console.cloud.timescale.com/dashboard/integrations [console-services]: https://console.cloud.timescale.com/dashboard/services [services-portal]: https://console.cloud.timescale.com/dashboard/services -[pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-plan +[pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-pricing-plan [projects]: /use-timescale/:currentVersion:/security/members/ diff --git a/use-timescale/page-index/page-index.js b/use-timescale/page-index/page-index.js index 443988e557..77f07d8aa5 100644 --- a/use-timescale/page-index/page-index.js +++ b/use-timescale/page-index/page-index.js @@ -606,9 +606,13 @@ module.exports = [ ], }, { - title: "Back up and recover your services", + title: "Back up and recover services", href: "backup-restore", }, + { + title: "Fork services", + href: "fork-services", + }, { title: "Jobs", href: "jobs", diff --git a/use-timescale/security/overview.md b/use-timescale/security/overview.md index 8741a73d9c..064267a7a5 100644 --- a/use-timescale/security/overview.md +++ b/use-timescale/security/overview.md @@ -107,5 +107,5 @@ $CLOUD_LONG is SOC 2 Type 2 compliant. This ensures that organizations can secur [vpc-peering]: /use-timescale/:currentVersion:/security/vpc [security-at-timescale]: https://www.timescale.com/security [ip-allowlist]: /use-timescale/:currentVersion:/security/ip-allow-list/ -[pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-plan +[pricing-plan-features]: /about/:currentVersion:/pricing-and-account-management/#features-included-in-each-pricing-plan [open-support-ticket]: https://console.cloud.timescale.com/dashboard/support \ No newline at end of file diff --git a/use-timescale/services/service-management.md b/use-timescale/services/service-management.md index 98500bbfa4..f8e6bad7f8 100644 --- a/use-timescale/services/service-management.md +++ b/use-timescale/services/service-management.md @@ -10,6 +10,8 @@ cloud_ui: - [create_services, fork, :serviceId] --- +import CLIFORKS from "versionContent/_partials/_devops-cli-service-forks.mdx"; + # $SERVICE_SHORT_CAP management In the `Service management` section of the `Operations` dashboard, you can fork @@ -46,8 +48,6 @@ data discrepancy between $SERVICE_SHORTs. -### Forking a $SERVICE_SHORT - 1. In $CONSOLE_LONG, from the `Services` list, ensure the $SERVICE_SHORT you want to form has a status of `Running` or `Paused`, then click the name of the $SERVICE_SHORT you want to fork. @@ -72,7 +72,12 @@ alt="Fork a Tiger service" -### Reset your $SERVICE_SHORT password +## Create a service fork using the $CLI_SHORT + + + + +## Reset your $SERVICE_SHORT password You can reset your $SERVICE_SHORT password from the `Operations` dashboard. This is the password you use to connect to your $SERVICE_SHORT, not the password for $CONSOLE. To reset your $CONSOLE_SHORT password, navigate to the `Account` page. @@ -86,14 +91,14 @@ digest algorithm 5) are cryptographic authentication mechanisms. $CONSOLE_LONG uses SCRAM by default. It is more secure and strongly recommended. The MD5 option is provided for compatibility with older clients. -### Pause a $SERVICE_SHORT +## Pause a $SERVICE_SHORT You can pause a $SERVICE_SHORT if you want to stop it running temporarily. When you pause a $SERVICE_SHORT, you are no longer billed for compute resources. However, you do need to continue paying for any storage you are using. Pausing a $SERVICE_SHORT ensures that it is still available, and is ready to be restarted at any time. -### Delete a $SERVICE_SHORT +## Delete a $SERVICE_SHORT You can delete a $SERVICE_SHORT to remove it completely. This removes the $SERVICE_SHORT and its underlying data from the server. You cannot recover a deleted