You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will make it easy for CI users to trace and analyze their CI jobs
without requiring additional work or scripting on their part. They can
just look at tracing information on their tracing provider.
@@ -582,6 +583,11 @@ var AgentStartCommand = cli.Command{
582
583
EnvVar: "BUILDKITE_TRACING_SERVICE_NAME",
583
584
Value: "buildkite-agent",
584
585
},
586
+
cli.BoolFlag{
587
+
Name: "trace-log-groups",
588
+
Usage: "Automatically creates tracing spans for log groups when tracing is enabled.",
589
+
EnvVar: "BUILDKITE_TRACE_LOG_GROUPS",
590
+
},
585
591
cli.StringFlag{
586
592
Name: "job-verification-key-path",
587
593
Usage: "Path to a file containing a verification key. Passing this flag enables job verification. For hmac-sha256, the raw file content is used as the shared key",
@@ -800,9 +806,13 @@ var AgentStartCommand = cli.Command{
800
806
})
801
807
802
808
// Sense check supported tracing backends, we don't want bootstrapped jobs to silently have no tracing
0 commit comments