-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide a Honeycomb context to applications run inside the workflow #6
Comments
to record my answers from slack: I'm using the default serialisation from beeline(-ruby): for the dataset and api key config, I'm using the default environment variables used in |
I've been able to attach the traces from a command to the trace from buildevents. All the data is there, we just have to polish this a bit / define a standard way to propagate context through the environment. The API key and dataset are already present in the environment since buildevents needs this as well. API key = My PoC implementation: https://github.com/kvrhdn/tfe-run/blob/honeycomb/main.go#L29 End result, this workflow run: https://github.com/kvrhdn/tfe-run/runs/639591915?check_suite_focus=true |
I've iterated a bit more on this, I now create a 'trace propagation context' string in
I export this to the environment as You can import it really easy using most beelines since this normally parse from HTTP headers. Advantages of this system:
Disadvantages:
A workaround would be to not use |
I'm closing this issue here since I'm in favor of implementing this in buildevents itself, see honeycombio/buildevents#74. |
Applications run during the workflow might be "Honeycomb-aware", i.e. they can send traces their own traces to Honeycomb. By providing these application additional context from
gha-buildevents
, it might be possible to create one detailed trace.Prior art:
HTTP_X_HONEYCOMB_TRACE
.See: rspec_honeycomb_formatter.rb
Post on slack: https://honeycombpollinators.slack.com/archives/CKWR1DRMM/p1588255603033700?thread_ts=1588179870.032600&cid=CKWR1DRMM
The text was updated successfully, but these errors were encountered: