Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃悰 Supabase Edge Functions: My filesystem details are leaked by the module label when using autometrics-ts with Supabase Edge Functions #108

Open
brettimus opened this issue Jul 25, 2023 · 0 comments

Comments

@brettimus
Copy link
Collaborator

brettimus commented Jul 25, 2023

Environment information

Supabase Edge Functions (prod deployment)

What happened?

I deployed an edge function with Supabase, and configured autometrics-ts to work with a push gateway.

The module label contained the filesystem path on my local machine to the script containing the edge function.

function_calls_duration_sum{caller="",function="getRabbit",module="file:///Users/brettbeutell/fiber/to-err-is-panda/supabase/functions/rabbit/index.ts"} 0.004

Interestingly, if I serve the edge function runtime locally (while testing them out), then the module is specific to the docker container that's hosting the edge runtime, and the module label looks like /home/deno/...

Expected result

I would expect my filesystem details to not be present in the module label.

@brettimus brettimus changed the title 馃悰 My filestystem details are leaked by the module label when using autometrics-ts with Supabase Edge Functions 馃悰 Supabase Edge Functions: My filestystem details are leaked by the module label when using autometrics-ts with Supabase Edge Functions Jul 25, 2023
@brettimus brettimus changed the title 馃悰 Supabase Edge Functions: My filestystem details are leaked by the module label when using autometrics-ts with Supabase Edge Functions 馃悰 Supabase Edge Functions: My filesystem details are leaked by the module label when using autometrics-ts with Supabase Edge Functions Feb 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant