<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Thu Feb 08 08:35:55 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>[GODRIVER-1212] Client/topology socket stats</title>
                <link>https://jira.mongodb.org/browse/GODRIVER-1212</link>
                <project id="14289" key="GODRIVER">Go Driver</project>
                    <description>&lt;p&gt;mgo provides a mechanism to return various stats (&lt;a href=&quot;https://godoc.org/labix.org/v2/mgo#Stats&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://godoc.org/labix.org/v2/mgo#Stats&lt;/a&gt;), particularly around number of in-use and idle sockets.  I think you could get total sockets if you implemented a custom Dialer, but I don&apos;t think you could differentiate idle sockets.&lt;/p&gt;

&lt;p&gt;mgo also tracks some stats on ops sent and docs received, but I think the existing CommandMonitor interface is flexible enough that&apos;d it&apos;d be better to just use that.  ConnectionOption could be similarly extended to support a &quot;WithServerPoolMonitor&quot; or something like that.&lt;/p&gt;</description>
                <environment></environment>
        <key id="882781">GODRIVER-1212</key>
            <summary>Client/topology socket stats</summary>
                <type id="2" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14711&amp;avatarType=issuetype">New Feature</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="13202">Works as Designed</resolution>
                                        <assignee username="manny.eppinger@mongodb.com">Emmanuel Eppinger</assignee>
                                    <reporter username="bartle">David Bartley</reporter>
                        <labels>
                    </labels>
                <created>Fri, 2 Aug 2019 03:17:05 +0000</created>
                <updated>Fri, 27 Oct 2023 13:16:32 +0000</updated>
                            <resolved>Fri, 9 Aug 2019 14:53:02 +0000</resolved>
                                                                                        <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="2363666" author="manny.eppinger" created="Thu, 8 Aug 2019 21:18:27 +0000"  >&lt;p&gt;Hi David,&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;That was talked about as something that will probably be implemented in the future as part of our metrics epic. For now the best bet is to use the connection pool events if those give you enough information.&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;Thanks and let us know if you have any other questions &lt;img class=&quot;emoticon&quot; src=&quot;https://jira.mongodb.org/images/icons/emoticons/smile.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;

&lt;p&gt;Emmanuel&lt;/p&gt;</comment>
                            <comment id="2358642" author="bartle" created="Mon, 5 Aug 2019 21:50:31 +0000"  >&lt;p&gt;Yeah, I think we could use ConnectionCheckedOutEvent and ConnectionCheckedInEvent to drive some counters.  It still might be useful to have an implementation that just increments counters like mgo if it seems like something that would be generally useful to folks.&lt;/p&gt;</comment>
                            <comment id="2358444" author="jeff.yemin" created="Mon, 5 Aug 2019 20:11:30 +0000"  >&lt;p&gt;Hi &lt;a href=&quot;https://jira.mongodb.org/secure/ViewProfile.jspa?name=bartle&quot; class=&quot;user-hover&quot; rel=&quot;bartle&quot;&gt;bartle&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;In scope &lt;a href=&quot;https://jira.mongodb.org/browse/GODRIVER-622&quot; title=&quot;Implement Connection Monitoring and Pooling spec&quot; class=&quot;issue-link&quot; data-issue-key=&quot;GODRIVER-622&quot;&gt;&lt;del&gt;GODRIVER-622&lt;/del&gt;&lt;/a&gt; we are implementing connection pool events, on top of which an application could easily build its own connection pool statistics.&#160;&#160;&lt;/p&gt;

&lt;p&gt;Please let us know if that will meet your needs.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10012">
                    <name>Related</name>
                                            <outwardlinks description="related to">
                                        <issuelink>
            <issuekey id="629358">GODRIVER-622</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_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hv7oj3:</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>