New RunLLM response generated: >>>*# Question* 👋 quick cloudwatch plugin question -- I've turn on the cloudwatch container insights plugin (it's an addon from EKS, fairly simple to turn on) -- I've changed the logging template URL to match the new pattern that cloudwatch is expecting but I'm confused by what I'm seeing:

<https://console.aws.amazon.com/cloudwatch/home?region=us-east-1#logEventViewer:group=/aws/containerinsights/prod-next-datologyai-k8s/application;stream={{> .hostname }}.var.log.containers.{{ .podName }}_{{ .namespace }}_{{ .containerName }}-{{ .containerId }}.log

Based on the docs hostname should be something supported as a template flag https://docs.flyte.org/en/latest/user_guide/productionizing/configuring_logging_links_in_the_ui.html#configure-logging -- but in practice this is the URL that flyte generates:

{{ .hostname }}.var.log.containers.f391c9f2cc04b4f4eb42-n1-0-dn8-0-dn1-0-dn1-0_datology-development_f391c9f2cc04b4f4eb42-n1-0-dn8-0-dn1-0-dn1-0-e8b24149abd504d7b278f3c927d2748ea6df7f431e268c6e1024445f5e4bd763.log

# Answer The

.hostname

variable is not currently supported in Flyte's logging template, despite being mentioned in the documentation. This discrepancy has been noted in several discussions and issues, such as this GitHub issue and this community discussion. Would you like more details on how to work around this issue or configure your logging template differently? Sources: - this GitHub issue - this community discussion Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1722451645.773039 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.