<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:20:52 JST 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>PFS-JIRA</title>
    <link>https://pfspipe.ipmu.jp/jira</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.3.4</version>
        <build-number>803005</build-number>
        <build-date>13-09-2019</build-date>
    </build-info>


<item>
            <title>[INSTRM-38] Add timebase (NTP/PTP) monitoring</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-38</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;We need to make sure that drops in NTP service to any part of the instrument or any divergences are noted and reported.&lt;/p&gt;</description>
                <environment></environment>
        <key id="11384">INSTRM-38</key>
            <summary>Add timebase (NTP/PTP) monitoring</summary>
                <type id="3" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10518&amp;avatarType=issuetype">Task</type>
                                            <priority id="3" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/priorities/major.svg">Major</priority>
                        <status id="1" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/statuses/open.png" description="The issue is open and ready for the assignee to start work on it.">Open</status>
                    <statusCategory id="2" key="new" colorName="blue-gray"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="cloomis">cloomis</reporter>
                        <labels>
                    </labels>
                <created>Fri, 16 Dec 2016 17:35:33 +0000</created>
                <updated>Fri, 31 Mar 2023 16:41:12 +0000</updated>
                                                                                <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="12167" author="arnaud.lefur" created="Thu, 18 May 2017 10:34:24 +0000"  >&lt;p&gt;I don&apos;t if my understanding is correct, but basically on the PFS network we have one machine which is synchronised with the outside world every (hours ? days ?) . Then every clients on our network synchronise with that machine right ?.&lt;/p&gt;

&lt;p&gt;What do you want to monitor exactly ? the time drift ? if the ntp server is unreachable ?&lt;/p&gt;</comment>
                            <comment id="12184" author="atsushi.shimono" created="Fri, 19 May 2017 02:12:37 +0000"  >&lt;p&gt;From system health monitoring point of view, we should monitor both whether NTP sync is working at each control system or not, and also how large their drift is.&lt;br/&gt;
This might not be monitored from actor layer, but at least shall be handled by OS monitoring (or layer above than it).&lt;/p&gt;</comment>
                            <comment id="12267" author="arnaud.lefur" created="Fri, 16 Jun 2017 09:53:40 +0000"  >&lt;p&gt;I&apos;ve installed &lt;b&gt;ntplib&lt;/b&gt; on our anaconda distribution. I&apos;ve tested a bit and it seems to answer our expectations.&lt;/p&gt;</comment>
                            <comment id="32427" author="arnaud.lefur" created="Fri, 17 Mar 2023 20:56:09 +0000"  >&lt;p&gt;&lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=hiro&quot; class=&quot;user-hover&quot; rel=&quot;hiro&quot;&gt;Yoshida, Hiroshige&lt;/a&gt; Does subaru alert on ntp failures?&lt;/p&gt;</comment>
                            <comment id="32509" author="cloomis" created="Fri, 31 Mar 2023 16:41:12 +0000"  >&lt;p&gt;This actually just hit us. Because we rebooted several BEEs yesterday it happened to be obvious: they have no batteries and so came up 21 years off. But since the instrument NTP server was gone all of the other system clocks would have started drifting, along with the dates of and in the various image files and logs. It might not take too many days for the agc and agcc computers to drift off by a few seconds, which could have been deeply confusing. &lt;/p&gt;

&lt;p&gt;Is this a place for prometheus, etc? And/or a second NTP server? Thoughts, &lt;a href=&quot;https://pfspipe.ipmu.jp/jira/secure/ViewProfile.jspa?name=hiro&quot; class=&quot;user-hover&quot; rel=&quot;hiro&quot;&gt;Yoshida, Hiroshige&lt;/a&gt;?&lt;/p&gt;
</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                <customfield id="customfield_10500" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                            <customfield id="customfield_10010" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|ii019z:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>