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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[otel] transaction result incorrect on timed-out fetch #28377

Open
Tracked by #28446
EtienneBruines opened this issue Mar 3, 2025 · 0 comments
Open
Tracked by #28446

[otel] transaction result incorrect on timed-out fetch #28377

EtienneBruines opened this issue Mar 3, 2025 · 0 comments
Labels

Comments

@EtienneBruines
Copy link

EtienneBruines commented Mar 3, 2025

Version: Deno 2.2.2

Using the unstable OpenTelemetry feature, the data for my outgoing fetch request is being exported like this:

transaction.result | Success

However, the logs indicate a less-than-ideal result (which is indeed the case):

[ERROR] Error fetching Wazuh auth token: TypeError: error sending request for url (https://172.16.9.181:55000/security/user/authenticate): client error (Connect): tcp connect error: Connection timed out (os error 110): Connection timed out (os error 110)
    at async mainFetch (ext:deno_fetch/26_fetch.js:189:12)
    at async fetch (ext:deno_fetch/26_fetch.js:454:11)
    at async Wazuh.authenticate (file:///app/wazuh.ts:63:24)
    at async Wazuh.fetchAgents (file:///app/wazuh.ts:112:9)
    at async Wazuh.fetchAllAgents (file:///app/wazuh.ts:178:26)
    at async file:///app/main.ts:20:18

So it would be nice if the transaction.result indicated this as an error, instead of Success. The url.full field does not contain the hostname, nor does the url.original field.

@littledivy littledivy added the otel label Mar 4, 2025
@lucacasonato lucacasonato mentioned this issue Mar 10, 2025
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants