Message-ID: <gh-pgjdbc-pgjdbc-2478-c1156584151@github.com>
From: "sehrope (@sehrope)" <noreply+sehrope@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 15 Jun 2022 14:59:22 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #2478: Collect and report metrics from the driver side
In-Reply-To: <gh-pgjdbc-pgjdbc-2478@github.com>
References: <gh-pgjdbc-pgjdbc-2478@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: sehrope
X-GitHub-Comment-Id: 1156584151
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 2478
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/2478#issuecomment-1156584151
Content-Type: text/plain; charset=utf-8

+1 to exposing our own interfaces and let the end user bridge that to their own collector. That would give us the ability to make it match whatever level of low level detail we'd like to provide.

Perhaps we could even mark the interface itself as "experimental" to have the first couple releases maintain the flexibility / luxury of changing the interface if real world usage changes. Breaking things after they're in the field is never a good thing, but for something entirely new like this keeping that option might be worthwhile.