sonic-buildimage/files/build_templates/telemetry.service.j2

[Unit]
Description=Telemetry container
Requires=database.service
After=database.service swss.service syncd.service
Before=ntp-config.service
BindsTo=sonic.target
After=sonic.target
StartLimitIntervalSec=1200
StartLimitBurst=3

[Service]
User={{ sonicadmin_user }}
ExecStartPre=/usr/local/bin/{{docker_container_name}}.sh start
ExecStart=/usr/local/bin/{{docker_container_name}}.sh wait
ExecStop=/usr/local/bin/{{docker_container_name}}.sh stop
Restart=always
RestartSec=30
[telemetry]: SONiC system telemetry Support (#1526) * SONiC system telemetry Support Signed-off-by: Jipan Yang <jipan.yang@alibaba-inc.com> * Update package name from telemetry to sonic-telemetry Signed-off-by: Jipan Yang <jipan.yang@alibaba-inc.com> 2018-03-27 15:39:04 -05:00			`[Unit]`
			`Description=Telemetry container`
[telemetry]: change the service dependency from swss to database (#3072) Signed-off-by: Jipan Yang <jipan.yang@alibaba-inc.com> 2019-06-24 14:36:16 -05:00			`Requires=database.service`
[services] improve startup time by changing startup order (#3656) * [services] improve startup time by given precedence to critical services (syncd.service) Signed-off-by: Stepan Blyschak <stepanb@mellanox.com> 2019-10-31 11:18:26 -05:00			`After=database.service swss.service syncd.service`
[boot] Refactor: All services which start Docker containers start before ntp-config service (#2335) 2018-12-03 18:01:44 -06:00			`Before=ntp-config.service`
[services] introduce sonic.target (#5705) - Why I did it Group all SONiC services together and able to manage them together. Will be used in config reload command as much simpler and generic way to restart services. - How I did it Add services to sonic.target - How to verify it Together with Azure/sonic-utilities#1199 config reload -y Signed-off-by: Stepan Blyshchak <stepanb@nvidia.com> 2021-02-25 06:26:24 -06:00			`BindsTo=sonic.target`
			`After=sonic.target`
[Services] Restart Telemetry service upon unexpected critical process exit. (#3768) Signed-off-by: Yong Zhao <yozhao@microsoft.com> 2019-11-18 18:56:44 -06:00			`StartLimitIntervalSec=1200`
			`StartLimitBurst=3`
[telemetry]: SONiC system telemetry Support (#1526) * SONiC system telemetry Support Signed-off-by: Jipan Yang <jipan.yang@alibaba-inc.com> * Update package name from telemetry to sonic-telemetry Signed-off-by: Jipan Yang <jipan.yang@alibaba-inc.com> 2018-03-27 15:39:04 -05:00
			`[Service]`
			`User={{ sonicadmin_user }}`
[services] kill container on stop in warm/fast mode (#10511) To optimize stop on warm boot, added kill for containers Use service "kill" in the shutdown path for fast and warm reboot. For all other reload methods, service "stop" is used. This is done to save time in shutdown path, and to overall improve the time spent in warm and fast reload. How - Use service_mgmt.sh to trigger common logic to initiate kill (fast/warm) or stop (cold) for database.sh, radv.sh, snmp.sh, telemetry.sh, mgmt-framework.sh Signed-off-by: Stepan Blyschak <stepanb@nvidia.com>, Vaibhav H D <vaibhav.dixit@microsoft.com> 2022-04-18 16:27:48 -05:00			`ExecStartPre=/usr/local/bin/{{docker_container_name}}.sh start`
			`ExecStart=/usr/local/bin/{{docker_container_name}}.sh wait`
			`ExecStop=/usr/local/bin/{{docker_container_name}}.sh stop`
[Services] Restart Telemetry service upon unexpected critical process exit. (#3768) Signed-off-by: Yong Zhao <yozhao@microsoft.com> 2019-11-18 18:56:44 -06:00			`Restart=always`
			`RestartSec=30`