<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:24:44 UTC 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>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[DRIVERS-2106] Include local ephemeral port in APM command callbacks</title>
                <link>https://jira.mongodb.org/browse/DRIVERS-2106</link>
                <project id="10980" key="DRIVERS">Drivers</project>
                    <description>&lt;p&gt;Requested by James Blackburn in Python birds of feather session at MongoDB World 2016. (&lt;a href=&quot;https://docs.google.com/document/d/1Lr1Zh3WGm3-Y91ZQ00vgNS7zFi-lvLPejKqmus9lxuQ&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;Notes here&lt;/a&gt;.) Useful to correlate APM callback invocations on the client with server log messages.&lt;/p&gt;</description>
                <environment></environment>
        <key id="299061">DRIVERS-2106</key>
            <summary>Include local ephemeral port in APM command callbacks</summary>
                <type id="14901" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14700&amp;avatarType=issuetype">Spec Change</type>
                                            <priority id="4" iconUrl="https://jira.mongodb.org/images/icons/priorities/minor.svg">Minor - P4</priority>
                        <status id="10038" iconUrl="https://jira.mongodb.org/images/icons/subtask.gif" description="">Backlog</status>
                    <statusCategory id="2" key="new" colorName="default"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="jesse@mongodb.com">A. Jesse Jiryu Davis</reporter>
                        <labels>
                    </labels>
                <created>Wed, 6 Jul 2016 19:13:01 +0000</created>
                <updated>Wed, 8 Mar 2023 19:49:06 +0000</updated>
                                                                <component>Command Logging and Monitoring</component>
                                        <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="4005384" author="kevin.albertson" created="Tue, 17 Aug 2021 21:14:23 +0000"  >&lt;blockquote&gt;
&lt;p&gt;I think we can do all three. Ephemeral port is always available and can be included now, lsid for MongoDB 3.6+, and add connectionId once &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-10637&quot; title=&quot;Provide a mechanism to expose the connectionId so that drivers can log it&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-10637&quot;&gt;&lt;del&gt;SERVER-10637&lt;/del&gt;&lt;/a&gt; is resolved.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;We are not planning to expose the ephemeral server port because exposing the server connectionID on command monitoring events seems redundant.&lt;/p&gt;

&lt;p&gt;The lsid already is available in the full command exposed in the CommandStartedEvent. We could consider adding the lsid to CommandFailedEvent and CommandSucceededEvent, but we do not plan to do this on DRIVERS-1141.&lt;/p&gt;

&lt;p&gt;DRIVERS-1141 proposes only exposing the server-side connectionID to satisfy the requirements of MHOUSE-2311.&lt;/p&gt;</comment>
                            <comment id="1780994" author="jeff.yemin" created="Mon, 22 Jan 2018 17:50:10 +0000"  >&lt;p&gt;The lsid is useful but isn&apos;t as ubiquitous in server log files as the connectionId.&lt;/p&gt;</comment>
                            <comment id="1780984" author="behackett" created="Mon, 22 Jan 2018 17:42:04 +0000"  >&lt;p&gt;I think we can do all three. Ephemeral port is always available and can be included now, lsid for MongoDB 3.6+, and add connectionId once &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-10637&quot; title=&quot;Provide a mechanism to expose the connectionId so that drivers can log it&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-10637&quot;&gt;&lt;del&gt;SERVER-10637&lt;/del&gt;&lt;/a&gt; is resolved. &lt;/p&gt;</comment>
                            <comment id="1780836" author="jesse" created="Mon, 22 Jan 2018 16:39:57 +0000"  >&lt;p&gt;We can now log the logical session id (&quot;lsid&quot;) in APM callbacks. It should be included by default in the command-started event data with no special work from us. Once all drivers and servers are upgraded, does lsid provide the functionality we wanted from ephemeral port or connectionId?&lt;/p&gt;</comment>
                            <comment id="1780771" author="jeff.yemin" created="Mon, 22 Jan 2018 16:13:42 +0000"  >&lt;p&gt;Even more useful would be to include the server&apos;s connection id, as that&apos;s included in every log message, whereas the ephemeral port is only included in the log message for connection establishment.  Given connection pooling in drivers, that log message has often rolled off the current log that is provided to TSEs.&lt;/p&gt;

&lt;p&gt;The Java driver both logs this and includes it in command monitoring, and it&apos;s saved TSEs&apos; time more than once.&lt;/p&gt;

&lt;p&gt;See also &lt;a href=&quot;https://jira.mongodb.org/browse/SERVER-10637&quot; title=&quot;Provide a mechanism to expose the connectionId so that drivers can log it&quot; class=&quot;issue-link&quot; data-issue-key=&quot;SERVER-10637&quot;&gt;&lt;del&gt;SERVER-10637&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10011">
                    <name>Depends</name>
                                                                <inwardlinks description="is depended on by">
                                        <issuelink>
            <issuekey id="235814">DRIVERS-273</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="87748">SERVER-10637</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                                                                                                            <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10951" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Driver Changes</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10748"><![CDATA[Needed]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hr6kev:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>9223372036854775807</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                        </customfields>
    </item>
</channel>
</rss>