-
Notifications
You must be signed in to change notification settings - Fork 3
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
Update handler to produce a full trace with child spans #10
Conversation
… in the default recipe to provide a lot more detail in the Signed-off-by: Davin Taddeo <davin@davintaddeo.com>
…hef Client version 17. Signed-off-by: Davin Taddeo <davin@honeycomb.io>
Signed-off-by: Davin Taddeo <davin@honeycomb.io>
…e obviously examples. Signed-off-by: Davin Taddeo <davin@honeycomb.io>
As a note. I've only tested this with Chef/CINC client version 17.10 so far. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks really good, thanks @tdarwin 👍🏻
I've left some feedback to remove an unused func, remove commented out code and styling things.
@MikeGoldsmith Thanks for all the suggestions and tweaks and nit-picks. I'll put out another commit soon to clean stuff up. might not be until Friday when I'm back from this conference. |
Signed-off-by: Davin Taddeo <davin@honeycomb.io>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good, thanks @tdarwin 👍🏻
Which problem is this PR solving?
The current version of the handler does not produce what Honeycomb recognizes as a trace, so there is no waterfall view of processes, access to use the node object in queries, and very minimal bubble up capabilities.
Short description of the changes
This updates the product to be a full trace, where the compile, converge, and handler phases are all shown as child spans, and the converge phase is broken down into spans per cookbook, recipe, and resource.
All objects have access to a subset of the node object that make bubble-up and querying more interesting, and users are provided with a mechanism to ensure that node attributes/objects that they care about can be included in that data as well.
Notes
There's some funky code to make this work as a handler that's part of a cookbook, but it does. If I were committing this as something I wanted to be part of Chef itself, there would be cleaner ways to do certain things.
Resulting Images
Here are some screen captures of this handler in action in waterfall mode, query + heatmap, and bubble-up: