You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
Version: Deno 2.2.2
Using the unstable OpenTelemetry feature, the data for my outgoing
fetch
request is being exported like this:However, the logs indicate a less-than-ideal result (which is indeed the case):
So it would be nice if the
transaction.result
indicated this as an error, instead ofSuccess
. Theurl.full
field does not contain the hostname, nor does theurl.original
field.The text was updated successfully, but these errors were encountered: