ancient-wolf-19325
08/20/2024, 2:39 PM{{ .podName }}, {{ .namespace }}, {{ .containerName }}, etc., which can be used to generate unique URLs for logs.
Here's an example configuration for Azure Monitor Logs:
task_logs:
plugins:
logs:
templates:
- displayName: AzureMonitor
templateUris:
- "https://portal.azure.com/#blade/Microsoft_Azure_Monitoring_Logs/LogsBlade/~/query?query=ContainerLog_CL%7C%20where%20ContainerName_s%20%3D%3D%20'{{.containerName}}'%20and%20PodName_s%20%3D%3D%20'{{.podName}}'%20and%20Namespace_s%20%3D%3D%20'{{.namespace}}'"
messageFormat: "json"
If the template URI approach does not work, you might need to extend the existing log plugin logic. This involves modifying the Flyte codebase to support Azure Monitor Logs specifically.
Would you like more details on extending the log plugin logic?
Sources:
- https://discuss.flyte.org/t/9562233/i-have-two-questions-1-how-can-i-monitor-the-std-out-and-std/
Slack Link
https://flyte-org.slack.com/archives/CP2HDHKE1/p1724164751.534299 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.