Allow custom tags for Browser and RUM on the initialization
See original GitHub issueThe current applications that we monitor we make extensive use of tags to be able to aggregate and filter the logs in the way the teams get easier debugging.
Running the browser log it is possible to see default tags being added based on the params of passed on the init method. As can be confirmed here https://github.com/DataDog/browser-sdk/blob/3b25ae0f92842f37be0a343dbd5d690fe973889f/packages/core/src/configuration.ts#L192-L196.
I was wondering if would be ok to have an optional parameter to the interface UserConfiguration
to allow custom tags during the init of the browser logs and RUM.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:10
- Comments:8
Top Results From Across the Web
RUM Browser Monitoring - Datadog Docs
Define the environment name and service name for your application to use unified service tagging for RUM & Session Replay. Set a version...
Read more >Specify custom metadata - Amazon CloudWatch
Explains how to specify custom attributes in the metadata that the CloudWatch RUM web client collects.
Read more >Set up agentless Real User Monitoring | Dynatrace Docs
Use blocking script tags to ensure that your RUM JavaScript will be executed exactly where you place it. If you need a script...
Read more >Filter your data by tags in Splunk RUM
Search for indexed tags · url name · operation · HTTP Method and status code · custom event name · browser and version...
Read more >Page view triggers - Tag Manager Help - Google Support
The Consent Initialization trigger is used for tags that set or update the user consent state for your site, such as a Consent...
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 Free
Top 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
maintainer update: behavior disabled since v4
For the record, as long as this feature isn’t carried out on datadog side, you can “hack” it by including the custom tags into one of the initialization options like this:
Which of course is a bug in the first place, as the commas in those options should probably get escaped.
Hi @rodrigopinto
There is ongoing work to merge the attributes and tags concepts so we are not willing to introduce this kind of API for now. However, as you are using logs, you can configure a remapper to set an env tag from the env attribute.