HEX
Server: Apache
System: Linux scp1.abinfocom.com 5.4.0-216-generic #236-Ubuntu SMP Fri Apr 11 19:53:21 UTC 2025 x86_64
User: confeduphaar (1010)
PHP: 8.1.33
Disabled: exec,passthru,shell_exec,system
Upload Files
File: //usr/lib/python3/dist-packages/cloudinit/analyze/__pycache__/__init__.cpython-38.pyc
U

ӇgZ%�@s�ddlZddlZddlZddlmZmZddlmZddlmZm	Z	ddl
mZddd�Zdd	�Z
d
d�Zdd
�Zdd�Zdd�Zdd�Zedd�dd�Zedkr�e�Ze��Zej\ZZeee�dS)�N)�datetime�timezone)�IO)�dump�show)�
json_dumpscCsh|stjddd�}|jddd�}d|_|jdd	d
�}|jddd
dddd�|jddd
dddd�|jdtfd�|jddd
�}|jddd
dddd�|jddd
dddd�|jddd
dddd�|jdtfd�|jd d!d
�}|jddd
ddd"d�|jddd
dddd�|jd t	fd�|jd#d$d
�}|jddd
ddd"d�|jddd
dddd�|jd#t
fd�|S)%Nzcloudinit-analyzez,Devel tool: Analyze cloud-init logs and data)�prog�descriptionZSubcommandsZ
subcommand)�title�destTZblamez5Print list of executed stages ordered by time to init)�helpz-iz--infileZstore�infilez/var/log/cloud-init.logzspecify where to read input.)�actionr�defaultrz-oz	--outfile�outfile�-zspecify where to write output. )rrz.Print list of in-order events during executionz-fz--format�print_formatz%I%D @%Es +%dszspecify formatting of output.zspecify where to write output.rz%Dump cloud-init events in JSON formatzspecify where to read input. Zbootz2Print list of boot times for kernel and cloud-init)�argparse�ArgumentParserZadd_subparsersZrequiredZ
add_parser�add_argumentZset_defaults�
analyze_blame�analyze_show�analyze_dump�analyze_boot)�parserZ
subparsersZparser_blameZparser_showZparser_dumpZparser_boot�r�</usr/lib/python3/dist-packages/cloudinit/analyze/__init__.py�
get_parsers���������������rc
Cst|�\}}t��}|\}}}}t�|tj�}	t�|tj�}
t�|tj�}z,dd�t|�D�d}t�|dtj�}
Wntk
r�d}
tj	}YnXd}d}d}tj	|tj
|tj|i}||}||}|	|
|||||||
d	�	}|�||j
f|��t||�|S)
a�Report a list of how long different boot operations took.

    For Example:
    -- Most Recent Boot Record --
        Kernel Started at: <time>
        Kernel ended boot at: <time>
        Kernel time to boot (seconds): <time>
        Cloud-init activated by systemd at: <time>
        Time between Kernel end boot and Cloud-init activation (seconds):<time>
        Cloud-init start: <time>
    cSs(g|] }|ddkrd|dkr|�qS)�namez
init-localzstarting searchr	r)�.0�errr�
<listcomp>�s�z analyze_boot.<locals>.<listcomp>���Z	timestampz4Could not find init-local log-line in cloud-init.logz�Your Linux distro or container does not support this functionality.
You must be running a Kernel Telemetry supported distro.
Please check https://docs.cloud-init.io/en/latest/topics/analyze.html for more information on supported distros.
a*-- Most Recent Boot Record --
    Kernel Started at: {k_s_t}
    Kernel ended boot at: {k_e_t}
    Kernel time to boot (seconds): {k_r}
    Cloud-init activated by systemd at: {ci_sysd_t}
    Time between Kernel end boot and Cloud-init activation (seconds): {bt_r}
    Cloud-init start: {ci_start}
z�-- Most Recent Container Boot Record --
    Container started at: {k_s_t}
    Cloud-init activated by systemd at: {ci_sysd_t}
    Cloud-init start: {ci_start}
)	Zk_s_tZk_e_tZk_rZbt_rZk_eZk_sZci_sysdZ	ci_sysd_t�ci_start)�configure_iorZdist_check_timestamprZ
fromtimestamprZutc�_get_events�
IndexErrorZ	FAIL_CODEZCONTAINER_CODEZSUCCESS_CODE�write�format�clean_io)r�args�infh�outfhZkernel_infoZstatus_codeZkernel_startZ
kernel_endZ
ci_sysd_startZkernel_start_timestampZkernel_end_timestampZci_sysd_start_timestampZlast_init_localr#ZFAILURE_MSGZSUCCESS_MSGZ
CONTAINER_MSGZ
status_mapZkernel_runtimeZbetween_process_runtime�kwargsrrrrtsd���������
rc	Cs�t|�\}}d}t�dtj�}d}tt�t|�|��D]L\}}tt	|j
|�dd�}|�d|d�|�d�|�d�|�d�q6|�d	|d�t
||�d
S)azReport a list of records sorted by largest time delta.

    For example:
      30.210s (init-local) searching for datasource
       8.706s (init-network) reading and applying user-data
        166ms (modules-config) ....
        807us (modules-final) ...

    We generate event records parsing cloud-init logs, formatting the output
    and sorting by record data ('delta')
    z
     %ds (%n)z(^\s+\d+\.\d+)rT)�reverse�-- Boot Record %02d --
��
�%d boot records analyzed
N)r$�re�compile�	MULTILINE�	enumerater�show_eventsr%�sorted�filter�matchr'�joinr))	rr*r+r,Zblame_format�r�idx�recordZsrecsrrrr�s�rcCs�t|�\}}tt�t|�|j��D]B\}}|�d|d�|�d�|�d�|�d�|�d�q"|�d|d�t||�dS)aGenerate output records using the 'standard' format to printing events.

    Example output follows:
        Starting stage: (init-local)
          ...
        Finished stage: (init-local) 0.105195 seconds

        Starting stage: (init-network)
          ...
        Finished stage: (init-network) 0.339024 seconds

        Starting stage: (modules-config)
          ...
        Finished stage: (modules-config) 0.NNN seconds

        Starting stage: (modules-final)
          ...
        Finished stage: (modules-final) 0.NNN seconds
    r/r0zUThe total time elapsed since completing an event is printed after the "@" character.
z>The time the event takes is printed after the "+" character.

r1r2N)	r$r6rr7r%rr'r;r))rr*r+r,r=r>rrrr�s���rcCs0t|�\}}|�tt|��d�t||�dS)z%Dump cloud-init events in json formatr1N)r$r'rr%r))rr*r+r,rrrrsrcCs*d}t�|�\}}|s&tj|d�\}}|S)N)�rawdata)rZload_events_infilerZdump_events)r
r?Zevents�_rrrr%s
r%cCs�|jdkrtj}nBzt|jd�}Wn0tk
rRtj�d|j�t�d�YnX|jdkrftj	}nBzt|jd�}Wn0tk
r�tj�d|j�t�d�YnX||fS)z.Common parsing and setup of input/output filesrr<zCannot open file %s
r0�w)
r
�sys�stdin�open�OSError�stderrr'�exitr�stdout)r*r+r,rrrr$s

r$)�file_handles�returncGs(|D]}|tjtjfkrq|��qdS)zclose filehandlesN)rBrCrH�close)rIZfile_handlerrrr)1sr)�__main__)N)rr3rBrr�typingrZcloudinit.analyzerrZcloudinit.atomic_helperrrrrrrr%r$r)�__name__r�
parse_argsr*rrZaction_functorrrrr�<module>s&
eW%