# Internal Historian - QuestDB, not listed in Database Query Browser

**URL:** <https://forum.inductiveautomation.com/t/internal-historian-questdb-not-listed-in-database-query-browser/109238>\
**Category:** Ignition 8.3 Early Access\
**Created:** [August 1, 2025, 6:37am UTC](https://forum.inductiveautomation.com/t/internal-historian-questdb-not-listed-in-database-query-browser/109238 "2025-08-01T06:37:59Z")\
**Posts on this page:** 7\
**Page:** 2

<div class="post-metadata">

**Author:** ![Kyle.Chase](https://avatars.discourse-cdn.com/v4/letter/k/3bc359/32.png) [@Kyle.Chase](https://forum.inductiveautomation.com/u/Kyle.Chase)\
**Post date:** [August 5, 2025, 3:07pm UTC](https://forum.inductiveautomation.com/t/internal-historian-questdb-not-listed-in-database-query-browser/109238/21 "2025-08-05T15:07:46Z")

</div>

Can you share your compose file? That module should be available by default.

You will need to add the options @michael.flagler mentioned above.

---

<div class="post-metadata">

**Author:** ![Kyle.Chase](https://avatars.discourse-cdn.com/v4/letter/k/3bc359/32.png) [@Kyle.Chase](https://forum.inductiveautomation.com/u/Kyle.Chase)\
**Post date:** [August 5, 2025, 3:11pm UTC](https://forum.inductiveautomation.com/t/internal-historian-questdb-not-listed-in-database-query-browser/109238/22 "2025-08-05T15:11:04Z")

</div>

We are planning on making continuous improvements to the internal historian. Migrating the Audit Event and Alarm Journal data is on the long term roadmap.

---

<div class="post-metadata">

**Author:** ![David\_Folkner](https://avatars.discourse-cdn.com/v4/letter/d/bb73d2/32.png) [@David\_Folkner](https://forum.inductiveautomation.com/u/David_Folkner)\
**Post date:** [August 5, 2025, 4:10pm UTC](https://forum.inductiveautomation.com/t/internal-historian-questdb-not-listed-in-database-query-browser/109238/23 "2025-08-05T16:10:13Z")

</div>

100% my fault. used an old compose. Looks like the module list has changed significantly. It was just disabled due to the enabled modules flag.

---

<div class="post-metadata">

**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\
**Post date:** [August 5, 2025, 6:05pm UTC](https://forum.inductiveautomation.com/t/internal-historian-questdb-not-listed-in-database-query-browser/109238/24 "2025-08-05T18:05:02Z")

</div>

Can you show the database drivers listed under `/app/connections/databases/settings/drivers-jdbc` ?

 ![SCR-20250805-lrrn](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/d/1d324c079c0fffae374a20ff700d7882426e9d0b.png)

EDIT: whoops, I didn't see your follow-up reply.. Please disregard. Glad you got it working! 🎉

---

<div class="post-metadata">

**Author:** ![royd.van.doesburg](https://avatars.discourse-cdn.com/v4/letter/r/d07c76/32.png) [@royd.van.doesburg](https://forum.inductiveautomation.com/u/royd.van.doesburg)\
**Post date:** [September 2, 2025, 12:05pm UTC](https://forum.inductiveautomation.com/t/internal-historian-questdb-not-listed-in-database-query-browser/109238/25 "2025-09-02T12:05:15Z")

</div>

Hello Kyle,

Is it somehow possible to expose port 8812 to another server? As I can now only read (and further analyze) the data from the localhost.

Or is there any other way to read the data from a different machine.

---

<div class="post-metadata">

**Author:** ![Kyle.Chase](https://avatars.discourse-cdn.com/v4/letter/k/3bc359/32.png) [@Kyle.Chase](https://forum.inductiveautomation.com/u/Kyle.Chase)\
**Post date:** [September 2, 2025, 2:55pm UTC](https://forum.inductiveautomation.com/t/internal-historian-questdb-not-listed-in-database-query-browser/109238/26 "2025-09-02T14:55:50Z")

</div>

No, it is not possible to expose port 8812 externally.

---

<div class="post-metadata">

**Author:** ![royd.van.doesburg](https://avatars.discourse-cdn.com/v4/letter/r/d07c76/32.png) [@royd.van.doesburg](https://forum.inductiveautomation.com/u/royd.van.doesburg)\
**Post date:** [September 4, 2025, 1:07pm UTC](https://forum.inductiveautomation.com/t/internal-historian-questdb-not-listed-in-database-query-browser/109238/27 "2025-09-04T13:07:00Z")

</div>

Actually, I did get it to work by setting up a proxy. It is now possible to read the QuestDB historian data from a different server. Altough this looks like a nice sollution, we’ll have to wait and see how this impacts the performance of the read-actions.

[Previous page](https://forum.inductiveautomation.com/t/internal-historian-questdb-not-listed-in-database-query-browser/109238.md?page=1)