starred/hoppscotch

Fork 0

mirror of https://github.com/hoppscotch/hoppscotch.git synced 2026-04-26 01:06:00 +03:00

[GH-ISSUE #3364] tracing/logging on self hosted #1123

New issue

Open

opened 2026-03-16 18:44:24 +03:00 by kerem · 4 comments

kerem commented

2026-03-16 18:44:24 +03:00

Owner

Originally created by @mcmluk-monster on GitHub (Sep 18, 2023).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3364

Is there an existing issue for this?

I have searched the existing issues

Current behavior

I have setup a self hosted hoppscotch using the docker images currently (specifically the aio image). I've noticed if I use the public hoppscotch, there is logging that can be seen in the console. However, in my self-hosted setup I'm getting an undefined env variable as seen below:

Do I need to self host sentry and set that ENV, or will I need to build my own docker images? Or is there some other way I can enable logging?

Thanks for any help you can provide

Steps to reproduce

See description

Environment

Production

Version

Self-hosted

Originally created by @mcmluk-monster on GitHub (Sep 18, 2023). Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3364 ### Is there an existing issue for this? - [X] I have searched the existing issues ### Current behavior I have setup a self hosted hoppscotch using the docker images currently (specifically the aio image). I've noticed if I use the public hoppscotch, there is logging that can be seen in the console. However, in my self-hosted setup I'm getting an undefined env variable as seen below: ![image](https://github.com/hoppscotch/hoppscotch/assets/78389267/e81fc0b7-527b-49e5-995b-528bb8a0ca20) Do I need to self host sentry and set that ENV, or will I need to build my own docker images? Or is there some other way I can enable logging? Thanks for any help you can provide ### Steps to reproduce See description ### Environment Production ### Version Self-hosted

kerem added the

bug

need testing

labels

2026-03-16 18:44:24 +03:00

kerem commented

2026-03-16 18:44:35 +03:00

Author

Owner

@wirbe1 commented on GitHub (Sep 18, 2023):

You have to build your own images with correct env variables set for your docker environment in case of frontend images, however you can just set env variables for execution environment for backend image

@wirbe1 commented on GitHub (Sep 18, 2023): You have to build your own images with correct env variables set for your docker environment in case of frontend images, however you can just set env variables for execution environment for backend image

kerem commented

2026-03-16 18:44:40 +03:00

Author

Owner

@AndrewBastin commented on GitHub (Sep 21, 2023):

@mcmluk-monster Sentry tracing was an overlooked bit and should be moved out to individual platforms instead of the Hoppscotch Common Code (which is shared between Selfhost and hoppscotch.io) as its usage is currently hoppscotch.io specific.

Is there a requirement on your end for tracing/logging on SH ? Else our plan of action is to move the Sentry code out of the Common code into the hoppscotch.io platform.

@AndrewBastin commented on GitHub (Sep 21, 2023): @mcmluk-monster Sentry tracing was an overlooked bit and should be moved out to individual platforms instead of the Hoppscotch Common Code (which is shared between Selfhost and hoppscotch.io) as its usage is currently hoppscotch.io specific. Is there a requirement on your end for tracing/logging on SH ? Else our plan of action is to move the Sentry code out of the Common code into the hoppscotch.io platform.

kerem commented

2026-03-16 18:44:45 +03:00

Author

Owner

@radekpribyl commented on GitHub (Sep 21, 2023):

@AndrewBastin the intention is to have logging in place for the request / response processing. Not necessarily the Sentry piece. Especially when the request includes variables then it's handy to see how the final request looks like. Something similar to what is logged to the console at https://hoppscotch.io/ but not in the self-hosted version (see the screenshot below)

@radekpribyl commented on GitHub (Sep 21, 2023): @AndrewBastin the intention is to have logging in place for the request / response processing. Not necessarily the Sentry piece. Especially when the request includes variables then it's handy to see how the final request looks like. Something similar to what is logged to the console at https://hoppscotch.io/ but not in the self-hosted version (see the screenshot below) ![image](https://github.com/hoppscotch/hoppscotch/assets/5092233/03e00160-2bb8-4dcb-9029-d107a17fd014)

kerem commented

2026-03-16 18:44:50 +03:00

Author

Owner

@liyasthomas commented on GitHub (Sep 27, 2023):

Hi @radekpribyl, let me know if this comment helps you to view the entire final request object: https://github.com/hoppscotch/hoppscotch/issues/2651#issuecomment-1557056572.

We have a feature that allows you to "Generate code snippets" for various programming languages and frameworks:

Click on the drop-down right next to the "Send" button to open the options menu.
Click on "Show code" menu item.
Select "HTTP - HTTP 1.1 Request String" from the "Generate code" modal.

This displays the current request setup in HTTP 1.1 Request String syntax. Let us know if this suits your use case.

@liyasthomas commented on GitHub (Sep 27, 2023): Hi @radekpribyl, let me know if this comment helps you to view the entire final request object: https://github.com/hoppscotch/hoppscotch/issues/2651#issuecomment-1557056572. --- We have a feature that allows you to "Generate code snippets" for various programming languages and frameworks: 1. Click on the drop-down right next to the "**Send**" button to open the options menu. 2. Click on "**Show code**" menu item. 3. Select "**HTTP - HTTP 1.1 Request String**" from the "Generate code" modal. This displays the current request setup in HTTP 1.1 Request String syntax. Let us know if this suits your use case. ![Step (1)](https://github.com/hoppscotch/hoppscotch/assets/10395817/58fda089-e533-4af8-8640-cd10c260c839) ![Step (2)](https://github.com/hoppscotch/hoppscotch/assets/10395817/a9576d4d-bf9f-40fd-8951-686b20859e69)

kerem referenced this issue

2026-03-17 00:43:34 +03:00

[PR #1123] [MERGED] Translated some of Korean #3077