Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Create a Telemetry Event to Track Custom Data Execution #891

Closed
boumenot opened this issue Sep 19, 2017 · 2 comments
Closed

Create a Telemetry Event to Track Custom Data Execution #891

boumenot opened this issue Sep 19, 2017 · 2 comments
Milestone
2.2.19

Comments

@boumenot
Copy link
Member

There is no event to track the execution of Custom Data. Executing a script for Custom Data may take a very long time, and we have no insight into this. Please consider creating a event to track this, and the total execution time.

Does provisioning need to be gated by the execution of a script injected into Custom Data?
@brendandixon
Copy link
Contributor

@boumenot We'll consider this for the next release. Any preferences on the event raised and accompanying values? Also, cloud-init provisioned VMs will require another mechanism since the agent, in that case, does not execute the custom data.

@brendandixon brendandixon added this to the 2.2.19 milestone Oct 11, 2017
@boumenot
Copy link
Member Author

I do not have a strong preference. My first though is simply CustomData. I don't have anything to add to the message. The use of this event is more for tracking purposes, and to understand if CustomData is being by our customers.

I already have work items queued up for @paulmey. 😝

This was referenced Oct 17, 2017
Closed
Closed
Merged
brendandixon added a commit that referenced this issue Oct 18, 2017
@brendandixon
Merge pull request #913 from brendandixon/master
bf99c1d 
[#897] -- 'Target handler state' wall of errors
[#896] -- End of Line Comments are Not Supported nor Handled
[#891] -- Create a Telemetry Event to Track Custom Data Execution
[#884] -- Cleanup Old Goal State and Extension Cache
[#876] -- The agent should use a scaling back-off when retrying HTTP requests
[#869] -- The agent should report OS information in the correct JSON format.

Updated version to 2.2.18.1
Replaced errno.EREMOTEIO with fixed value (since the constant is not present in all Python 2.7 versions)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.2.19
Development

No branches or pull requests
2 participants
@boumenot @brendandixon