<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/doc/rtd/topics/analyze.rst, branch rolling</title>
<subtitle> (mirror of https://github.com/vyos/vyos-cloud-init.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=rolling</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=rolling'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/'/>
<updated>2019-09-18T08:48:33+00:00</updated>
<entry>
<title>docs: added output examples to analyze.rst</title>
<updated>2019-09-18T08:48:33+00:00</updated>
<author>
<name>Joshua Powers</name>
<email>josh.powers@canonical.com</email>
</author>
<published>2019-09-18T08:48:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=bc9f91caacb5190174470fca10b922129362f904'/>
<id>urn:sha1:bc9f91caacb5190174470fca10b922129362f904</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Cloud-init analyze module: Added ability to analyze boot events.</title>
<updated>2019-07-15T21:50:33+00:00</updated>
<author>
<name>Sam Gilson</name>
<email>t-sagils@microsoft.com</email>
</author>
<published>2019-07-15T21:50:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=a24550aee4c7282cd3624bf63f9501444e517678'/>
<id>urn:sha1:a24550aee4c7282cd3624bf63f9501444e517678</id>
<content type='text'>
This branch introduces a new command line feature for cloud-init.
Currently, the cloud-init module has the capability to analyze events in
cloud-init.log in three ways: 'show', 'blame', 'dump'.
These changes add a fourth capability, called 'boot'.
Running the command 'cloud-init analyze boot' will provide the user three
timestamps.
1) Timestamp for when the kernel starts initializing.
2) Timestamp for when the kernel finishes its initialization.
3) Timestamp for when systemd activates cloud-init.
This feature enables cloud-init users to analyze different boot phases.
This would aid in debugging performance issues related
to cloud-init startup or tracking regression.
</content>
</entry>
</feed>
