<!-- 
RSS generated by JIRA (8.3.4#803005-sha1:1f96e09b3c60279a408a2ae47be3c745f571388b) at Sat Feb 10 16:30:29 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-965] Add log channel just for all the Cmd{In,Queued,Done} keys.</title>
                <link>https://pfspipe.ipmu.jp/jira/browse/INSTRM-965</link>
                <project id="10300" key="INSTRM">Instrument control development</project>
                    <description>&lt;p&gt;tron has logs of all traffic gong through it, one per actor, etc. For the command channels, that includes keys describing the commands when they come in to tron, whether they get dispatched to the target actors, and when/how they finish.&lt;/p&gt;

&lt;p&gt;Add a single log channel for all of these. As it stands we either have to look in the archiver or in the per-commander log files. &lt;/p&gt;</description>
                <environment></environment>
        <key id="14361">INSTRM-965</key>
            <summary>Add log channel just for all the Cmd{In,Queued,Done} keys.</summary>
                <type id="3" iconUrl="https://pfspipe.ipmu.jp/jira/secure/viewavatar?size=xsmall&amp;avatarId=10518&amp;avatarType=issuetype">Task</type>
                                            <priority id="10000" iconUrl="https://pfspipe.ipmu.jp/jira/images/icons/priorities/medium.svg">Normal</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="cloomis">cloomis</assignee>
                                    <reporter username="cloomis">cloomis</reporter>
                        <labels>
                            <label>logging</label>
                    </labels>
                <created>Thu, 30 Apr 2020 15:50:30 +0000</created>
                <updated>Thu, 7 Oct 2021 13:59:12 +0000</updated>
                                                                            <component>tron_tron</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                <comments>
                            <comment id="22255" author="cloomis" created="Wed, 6 Oct 2021 05:27:37 +0000"  >&lt;p&gt;We need nice &lt;b&gt;access&lt;/b&gt; to this info. My suggestion of adding a log file is actually for strange people like me: I grep log files. More sensibly, some access shell scripts and or library routines would be better.&lt;/p&gt;</comment>
                            <comment id="22269" author="rhl" created="Thu, 7 Oct 2021 13:59:12 +0000"  >&lt;p&gt;This ticket is a request for a second and possibly more convenient way to save information that is already in the opdb.  We should only address it if the extraction of this information from opdb is essentially impossible.  We may (as the comment notes) need to add a convenience layer.&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|zzs1fs:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10002" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
                        <customfieldname>Story Points</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>1.0</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                        </customfields>
    </item>
</channel>
</rss>