/todo broken links

dagster-io · Dec 19, 2024 · 4c5fc5f · 4c5fc5f
1 parent dbbab7f
commit 4c5fc5f
Showing 1 changed file with 8 additions and 4 deletions.
diff --git a/.../dagster-plus/deployment/management/managing-compute-logs-and-error-messages.md b/.../dagster-plus/deployment/management/managing-compute-logs-and-error-messages.md
@@ -11,7 +11,8 @@ This guide is applicable to Dagster+.
 
 In this guide, we'll cover how to adjust where Dagster+ compute logs are stored and manage masking of error messages in the Dagster+ UI.
 
-By default, Dagster+ ingests [structured event logs and compute logs](/concepts/logging#log-types) from runs and surfaces error messages from [code locations](/guides/deploy/code-locations/) in the UI.
+{/* By default, Dagster+ ingests [structured event logs and compute logs](/concepts/logging#log-types) from runs and surfaces error messages from [code locations](/guides/deploy/code-locations/) in the UI. */}
+By default, Dagster+ ingests [structured event logs and compute logs](/todo) from runs and surfaces error messages from [code locations](/todo) in the UI.
 
 Depending on your organization's needs, you may want to retain these logs in your own infrastructure or mask error message contents.
 
@@ -25,7 +26,8 @@ Dagster's compute logs are handled by the configured [`ComputeLogManager`](/api/
 
 If using the Kubernetes agent, you can instead forward logs to your own S3 bucket by using the [`S3ComputeLogManager`](/api/python-api/libraries/dagster-aws#dagster_aws.s3.S3ComputeLogManager).
 
-You can configure the `S3ComputeLogManager` in your [`dagster.yaml` file](/dagster-plus/deployment/agents/customizing-configuration):
+{/* You can configure the `S3ComputeLogManager` in your [`dagster.yaml` file](/dagster-plus/deployment/agents/customizing-configuration): */}
+You can configure the `S3ComputeLogManager` in your [`dagster.yaml` file](/todo):
 
 ```yaml
 compute_logs:
@@ -55,7 +57,8 @@ computeLogs:
 
 If your organization has its own logging solution which ingests `stdout` and `stderr` from your compute environment, you may want to disable compute log upload entirely. You can do this with the <PyObject module="dagster._core.storage.noop_compute_log_manager" object="NoOpComputeLogManager" />.
 
-You can configure the `NoOpComputeLogManager` in your [`dagster.yaml` file](/dagster-plus/deployment/agents/customizing-configuration):
+{/* You can configure the `NoOpComputeLogManager` in your [`dagster.yaml` file](/dagster-plus/deployment/agents/customizing-configuration): */}
+You can configure the `NoOpComputeLogManager` in your [`dagster.yaml` file](/todo):
 
 ```yaml
 compute_logs:
@@ -72,7 +75,8 @@ computeLogs:
 
 ### Other compute log storage options
 
-For a full list of available compute log storage options, refer to the [Compute log storage docs](/deployment/dagster-instance#compute-log-storage).
+{/* For a full list of available compute log storage options, refer to the [Compute log storage docs](/deployment/dagster-instance#compute-log-storage). */}
+For a full list of available compute log storage options, refer to the [Compute log storage docs](/todo).
 
 ---