@ancient-wolf-19325 how should the

task_logs

section of helm values be configured to support custom uri's for dask logs (for the dask plugin)

To configure the

task_logs

section in Helm values for custom URIs for Dask logs, you need to specify the log templates using the templating parameters available for Flyte. According to the Flyte documentation, you can use parameters like

{{ .podName }}

,

{{ .namespace }}

, and

{{ .containerName }}

to create a templated URI for your logs. Here's an example configuration:

task_logs:
  plugins:
    logs:
      templates:
        - displayName: "Dask Logs"
          templateUris:
            - "https://your-log-service.com/logs?pod={{ .podName }}&namespace={{ .namespace }}&container={{ .containerName }}"

This configuration will generate log links using the specified template, allowing you to view logs for Dask tasks in your custom log service. Would you like more detail on any specific part of this configuration? Sources: - Configuring logging links in the UI 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

@ancient-wolf-19325 I have this exact setup but with a more recent flyte version (1.14.0) the dask log links no longer show up, only the kubernetes link

It seems likely that the issue with Dask log links not showing up in Flyte version 1.14.0 could be related to changes in how log links are configured or displayed in newer versions. My understanding is that Flyte's logging configuration might have been updated, affecting how custom log links are processed. To troubleshoot this, you might want to check the following: 1. Configuration Changes: Verify if there have been any changes in the configuration format or parameters for log links in the newer Flyte version. Reviewing the release notes for version 1.14.0 might provide insights into any changes that could affect log link configurations. 2. Dynamic Log Links: Ensure that dynamic log links are correctly configured and enabled. According to the Flyte documentation, dynamic log links need to be explicitly activated and configured using a

ClassDecorator

in

flytekit

. 3. Log Link Visibility: Check if there are any new settings related to the visibility or lifecycle of log links. The Flyte documentation mentions controlling in which task phases log links are shown, which might affect their visibility. Would you like more detailed guidance on any of these points? Sources: - Flyte documentation - Flyte documentation 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.