diff --git a/antora.yml b/antora.yml index 3f465af..db877f3 100644 --- a/antora.yml +++ b/antora.yml @@ -9,6 +9,7 @@ nav: asciidoc: attributes: company: 'DataStax' + support-url: 'https://www.ibm.com/mysupport/s/' astra-db: 'Astra DB' product: 'Astra Streaming' product-short: 'Astra' diff --git a/modules/ROOT/pages/astream-faq.adoc b/modules/ROOT/pages/astream-faq.adoc index 8bbfcb3..4aac502 100644 --- a/modules/ROOT/pages/astream-faq.adoc +++ b/modules/ROOT/pages/astream-faq.adoc @@ -126,7 +126,7 @@ See the following: === Can I migrate data from my existing {pulsar-short} cluster to {product}? Unless you are starting a project from scratch, you likely have message data that needs to be brought over to your {product} tenants. -For migration assistance, contact {support_url}[{company} Support]. +For migration assistance, contact {support-url}[IBM Support]. Every tenant in {product} comes with custom ports for Kafka and RabbitMQ workloads. {company} also offers a fully-compatible JMS implementation for your Java workloads. diff --git a/modules/developing/pages/astream-cdc.adoc b/modules/developing/pages/astream-cdc.adoc index 6e3d8c6..4d60e1e 100644 --- a/modules/developing/pages/astream-cdc.adoc +++ b/modules/developing/pages/astream-cdc.adoc @@ -206,7 +206,7 @@ If you don't have any {astra-stream} tenants, you must create a tenant in order Your {astra-stream} tenant must be in the same region as the table where you want to enable CDC. + CDC for {astra-db} is available only in xref:operations:astream-regions.adoc[regions that support {astra-stream}]. -If your database is deployed to an xref:astra-db-serverless:databases:regions.adoc[{astra-db} region] that doesn't yet support {astra-stream}, contact your {company} account representative or {support_url}[{company} Support]. +If your database is deployed to an xref:astra-db-serverless:databases:regions.adoc[{astra-db} region] that doesn't yet support {astra-stream}, contact your {company} account representative or {support-url}[IBM Support]. . Click *Create tenant*. + @@ -741,7 +741,7 @@ CDC for multi-region databases is only available for {db-serverless-vector} data . <> where you want to enable CDC. + -If your database is deployed to a region that doesn't support {astra-stream}, contact your {company} account representative or {support_url}[{company} Support]. +If your database is deployed to a region that doesn't support {astra-stream}, contact your {company} account representative or {support-url}[IBM Support]. . <> in your database, if you haven't done so already. diff --git a/modules/operations/pages/astream-limits.adoc b/modules/operations/pages/astream-limits.adoc index 66a8100..84172ed 100644 --- a/modules/operations/pages/astream-limits.adoc +++ b/modules/operations/pages/astream-limits.adoc @@ -3,13 +3,13 @@ {product} includes guardrails and limits to ensure best practices, foster availability, and promote optimal configurations for your databases. Unless otherwise noted, the following limits apply to shared clusters. -In general, xref:operations:astream-pricing.adoc#dedicated-clusters[Streaming Capacity Units] have more relaxed limits than shared clusters, and some limits can be changed by contacting {support_url}[{company} Support]. +In general, xref:operations:astream-pricing.adoc#dedicated-clusters[Streaming Capacity Units] have more relaxed limits than shared clusters, and some limits can be changed by contacting {support-url}[IBM Support]. == {product} guardrails Guardrails are provisioned in the default settings for {product}. You cannot directly change these guardrails. -For Streaming Capacity Units, some guardrails can be changed by contacting {support_url}[{company} Support]. +For Streaming Capacity Units, some guardrails can be changed by contacting {support-url}[IBM Support]. [cols="1,1,1"] |=== diff --git a/modules/operations/pages/astream-pricing.adoc b/modules/operations/pages/astream-pricing.adoc index 8da32f2..d9ada58 100644 --- a/modules/operations/pages/astream-pricing.adoc +++ b/modules/operations/pages/astream-pricing.adoc @@ -58,7 +58,7 @@ With shared clusters, you can create tenants in any of the xref:astream-regions. Streaming Capacity Units are open to almost any public cloud region. For this reason, Streaming Capacity Units offer more flexibility for xref:operations:astream-georeplication.adoc[georeplication]. -If your preferred region isn't already available, you can contact your {company} account representative or {support_url}[{company} Support] to request it. +If your preferred region isn't already available, you can contact your {company} account representative or {support-url}[IBM Support] to request it. == See also diff --git a/modules/operations/pages/astream-regions.adoc b/modules/operations/pages/astream-regions.adoc index ea2e58f..f377bbf 100644 --- a/modules/operations/pages/astream-regions.adoc +++ b/modules/operations/pages/astream-regions.adoc @@ -87,4 +87,4 @@ Your ElasticSearch and Snowflake deployments can be in different regions than yo == Request a region -If your preferred region isn't available, contact your {company} account representative or {support_url}[{company} Support]. \ No newline at end of file +If your preferred region isn't available, contact your {company} account representative or {support-url}[IBM Support]. \ No newline at end of file diff --git a/modules/operations/pages/create-delete-tenants.adoc b/modules/operations/pages/create-delete-tenants.adoc index dc35a53..298f2df 100644 --- a/modules/operations/pages/create-delete-tenants.adoc +++ b/modules/operations/pages/create-delete-tenants.adoc @@ -19,7 +19,7 @@ If you're new to {product}, try the xref:getting-started:index.adoc[{product} qu . Enter a name for the streaming tenant. . Select a xref:operations:astream-regions.adoc[cloud provider and region that supports {astra-stream}]. Not all {astra-db} regions support {product}. -If your preferred region isn't available, contact your {company} account representative or {support_url}[{company} Support]. +If your preferred region isn't available, contact your {company} account representative or {support-url}[IBM Support]. . Click *Create tenant*. API:: diff --git a/modules/operations/pages/monitoring/stream-audit-logs.adoc b/modules/operations/pages/monitoring/stream-audit-logs.adoc index 66bda8c..299324d 100644 --- a/modules/operations/pages/monitoring/stream-audit-logs.adoc +++ b/modules/operations/pages/monitoring/stream-audit-logs.adoc @@ -4,7 +4,7 @@ Stream your xref:astra-db-serverless:administration:view-account-audit-log.adoc[ To enable audit log streaming, you must do one of the following: - * Provide the **Full Name** of your {product} topic and the streaming tenant's `client.conf` file to {support_url}[{company} Support] or your {company} account representative. + * Provide the **Full Name** of your {product} topic and the streaming tenant's `client.conf` file to {support-url}[IBM Support] or your {company} account representative. * POST your configuration to the {devops-api-ref-url}#tag/Organization-Operations/operation/configureTelemetry[{product-short} {devops-api} telemetry endpoint]. == Create an {product} topic for audit logs @@ -29,13 +29,13 @@ You can use topics to organize audit logs by event type or other criteria. . To finalize the configuration, do one of the following: + -* Send your topic's full name and the `client.conf` file to {support_url}[{company} Support] or your {company} account representative, and then {company} will complete the setup. +* Send your topic's full name and the `client.conf` file to {support-url}[IBM Support] or your {company} account representative, and then {company} will complete the setup. * <> [#use-the-devops-api] == Configure audit log streaming with the {devops-api} -You can use the {devops-api-ref-url}#tag/Organization-Operations/operation/configureTelemetry[{product-short} {devops-api} telemetry endpoint] to configure audit log streaming instead of providing the configuration details to {company} Support. +You can use the {devops-api-ref-url}#tag/Organization-Operations/operation/configureTelemetry[{product-short} {devops-api} telemetry endpoint] to configure audit log streaming instead of providing the configuration details to IBM Support. . In the {astra-ui-link} header, click icon:grip[name="Applications"], and then select *Admin*. diff --git a/modules/operations/pages/private-connectivity.adoc b/modules/operations/pages/private-connectivity.adoc index d83dc47..24473fd 100644 --- a/modules/operations/pages/private-connectivity.adoc +++ b/modules/operations/pages/private-connectivity.adoc @@ -30,7 +30,7 @@ To use a private link service or private endpoint for {product}, do the followin * Microsoft Azure Private Link: Azure subscription IDs * Google Cloud Private Service Connect: GCP project IDs -. Contact {support_url}[{company} Support] to request private connectivity for {product}. +. Contact {support-url}[IBM Support] to request private connectivity for {product}. === Private connections for inbound traffic