# DB connection information

**URL:** <https://discuss.elastic.co/t/db-connection-information/314793>\
**Category:** Logstash\
**Tags:** jdbc\
**Created:** [September 20, 2022, 4:39pm UTC](https://discuss.elastic.co/t/db-connection-information/314793 "2022-09-20T16:39:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![KiranMohan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kiranmohan/32/47214_2.png) [@KiranMohan](https://discuss.elastic.co/u/KiranMohan)\
**Post date:** [September 20, 2022, 4:39pm UTC](https://discuss.elastic.co/t/db-connection-information/314793/1 "2022-09-20T16:39:35Z")

</div>

It seems Logstash (7.10) Input JDBC plugin is leaking DB connections in one of the production servers.  
**Is it possible to trace the DB connection information?**

The underlying Sequel library has an option to log\_connection\_info (See [sequel/opening\_databases.rdoc at jeremyevans/sequel (github.com)](https://github.com/jeremyevans/sequel/blob/master/doc/opening_databases.rdoc)). So I added the following in pipeline conf file but it seems to have no effect.

```auto
jdbc {
        sequel_opts => {
            log_connection_info => true
        }

```

May be Sequel "logger" option also needs to be set but I am not sure of how to do that in the pipeline conf file.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [October 18, 2022, 4:40pm UTC](https://discuss.elastic.co/t/db-connection-information/314793/2 "2022-10-18T16:40:14Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.