Datadog Real User Monitoring breaks node express client server on IE11
See original GitHub issueUsing the @datadog/browser-rum package with Node apollo web client fails on IE11.
Seeing multiple requests to https://run-http-intake.logs.datadoghq.com on IE11 that are different than Chrome. Unable to login to the application on IE11. Working theory is that datadogRUM is blocking other application requests on IE11. When datadogRUM is removed, the application is working correctly.
Chrome and IE11 requests:
- Request Method: POST RequestURL: https://rum-http-intake.logs.datadoghq.com/v1/input/pub{id}?_dd.application_id={id}&ddsource=browser&&ddtags=sdk_version:1.25.2.env:local&batch_time={timestamp}
Only IE11 request:
Request Method: CONNECT RequestURL: https://rum-http-intake.logs.datadoghq.com Proxy-Connection: Keep-Alive
Using the init method from the documentation like:
import { datadogRum } from '@datadog/browser-rum'
datadogRum.init({
applicationId: '<DATADOG_APPLICATION_ID>',
clientToken: '<DATADOG_CLIENT_TOKEN>',
site: '<DATADOG_SITE>',
env: process.env.ENVIRONMENT,
silentMultipleInit: true,
sampleRate: 100,
trackInteractions: false,
useSecureSessionCookie: true,
})
Please let me know what additional information I should find to help with this issue. IE11 issues are no fun. Thank you!
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6
Top Results From Across the Web
Datadog Real User Monitoring breaks node server on IE11
Using the @datadog/browser-rum package from RUM Browser Monitoring, with Node apollo web client fails on IE11.
Read more >RUM Browser Monitoring - Datadog Docs
Datadog Real User Monitoring (RUM) enables you to visualize and analyze the ... Browser SDK supports all modern desktop and mobile browsers including...
Read more >Monitoring Node.js Using Datadog APM
By alerting on symptoms, it was easy to spot that something was broken, but not necessarily what or why. With the server handling...
Read more >Sumo Logic Service Release Notes
Latest features and bug fixes for Sumo Logic apps, alerts, security, search, observability, data collectors, and more.
Read more >Front-end Developer Handbook 2019 - Cody Lindley
Learn Node.js. A short word of advice on learning. Learn the actual underlying technologies, before learning abstractions. Don't learn jQuery, learn the DOM ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @carlpeaslee,
Thanks for all these details! I have been able to reproduce the issue on IE 11 on your demo application.
The issue is due to a mismatch between browser-rum and browser-logs version. I would advise you to either:
I have tested with browser-rum@1.12.9 and the issue does not happen anymore.
@bcaudan this fixed our issue. Thanks for your help.