Custom tracePropagationTargetsSelf not working in self hosted version.

[snjv94]

I am trying to get the trace logs on my self hosted version of Hyperdx.
But, even after changing the tracePropagationTargetsSelf to my custom open-telemetry URL (mapped to 4318 port on the server) is not working in any way. The default log collector request are going on

Here is the code that I am using the plane javascript.

Due to lack of documentation for Self Hosted version, I am not able to get it working.
Any idea what I am doing wrong here?

[wrn14897]

Hi @snjv94 , great question. We will need to improve the browser sdk doc. So you will need to pass the otel collector URL to init the HyperDX instance like

HyperDX.init({
  apiKey: <YOUR_API_KEY>,
  consoleCapture: true,
  maskAllInputs: true,
  maskAllText: true,
  service: <YOUR_SERVICE_NAME>,
  tracePropagationTargets: [/localhost/i],
  url: <YOUR_OTEL_COLLECTOR_URL>, // http://localhost:4318 if you do docker compose up
});

FYI, in the next release, we will centralize all these URLs into .env file

[snjv94]

Thanks for the quick reply @wrn14897.

I was able to figure it out about the URL parameter from the core JS file call in

<script src="//www.unpkg.com/@hyperdx/browser@0.18.4/build/index.js"></script>

Though it would helpful if detail documentation is there.

Also one more add on question.

Is it possible to get the all the ajax requests logs along with there payload and headers in Hyperdx?
Right now I am able to see the document request but not the Fetch/XHR requests.

I have added the option "advancedNetworkCapture: true," but still not able to see anything.

[wrn14897]

Thanks for the quick reply @wrn14897.

I was able to figure it out about the URL parameter from the core JS file call in

<script src="//www.unpkg.com/@hyperdx/browser@0.18.4/build/index.js"></script>

Though it would helpful if detail documentation is there.

Also one more add on question.

Is it possible to get the all the ajax requests logs along with there payload and headers in Hyperdx? Right now I am able to see the document request but not the Fetch/XHR requests.

I have added the option "advancedNetworkCapture: true," but still not able to see anything.

Hi @snjv94,

Glad you figured out the URL thing and agree with the documentation improvement. Already put the tag on the ticket.
Yes, "advancedNetworkCapture" supposes to capture Fetch/XHR request payload/headers.
Could you give us more details about the framework and environments to help us debug ?