When implementing BRUM (via HTML/JS code injection into the code of an application) we can set configuration options for the apiKey, spa2, etc. However if there is a need to pass in additional meta data, that could be retrieved when running a query: SELECT * FROM browser_records It isn't super clear from these docs ( https://docs.appdynamics.com/display/PRO21/Add+Custom+User+Data+to+a+Page+Browser+Snapshot ) what the correct data structure is: PS There are also a bunch of missing closing parens ")" in the "Conventional Ajax Requests" sample code. I think I've correctly understood that when sending data back, it needs to be organized into these buckets depending on the datatype we are trying to pass back in. Here's the updated code sample with the correct parens, and comments for each data "bucket". <script type="text/javascript" charset="UTF-8"> window['adrum-config'] = { xhr: { payloadParams: [{method: 'POST'}] }, userEventInfo: { "Ajax" : function(context){ if(context.data && context.data.indexOf("purchase") > -1){ // The URLSearchParams API does not work on IE/Edge var payload = new URLSearchParams(context.data); return { userData: { //String properties username: payload.get("username"), email: payload.get("email"), phone: payload.get("phone") }, userDataLong: { //Long properties customerId: Number(payload.get("customer_id")), totalPurchases: Number(payload.get("total_purchases")) }, userDataDouble: { //Double properties purchaseTotal: Number(payload.get("total")) }, userDataBoolean: { //Boolean properties discounted: Boolean(payload.get("discounted")), vipMember: Boolean(payload.get("member")) }, userDataDate: { //Date properties purchaseTime: Date.now() } } } } }; </script> <script src="//cdn.appdynamics.com/adrum/adrum-latest.js" type="text/javascript" charset="UTF-8"></script> Ok, so now for my particular case, all users are logged in (enterprise app), so we'd like to pass in 2 identifiers that let's us know which user, and which company a giving request is for. This will be particularly helpful with tracking down some users with rouge or broken browser extensions that are making various ajax requests while the user navigates our application. I'm looking to capture this additional property on Ajax, PageView, and VPageView. Does what I've coded below "smell" right? (ignoring all other aspects of the adrum-config) window['adrum-config'] = { userEventInfo: { "Ajax" : function(context){ return { userData: { user: sessionStorage.get("user"), cust: sessionStorage.get("company") } } }, "PageView" : function(context){ return { userData: { user: sessionStorage.get("user"), cust: sessionStorage.get("company") } } }, "VPageView" : function(context){ return { userData: { user: sessionStorage.get("user"), cust: sessionStorage.get("company") } } }, } }; ...or do I need to also specify all method verbs I want to track this on?... e.g. GET/POST/PUT/HEAD/... ... View more

We inject the adrum script into our application pointing to the CDN version of "adrum-latest.js". This of course loads the latest version of the script from the CDN. We noted that as of version 20.8.0.3230 (up to the latest: https://cdn.appdynamics.com/adrum/adrum-20.9.0.3268.js) we are getting the following "this.thenCore is not a function" error in all Chrome or Chromium based browsers (The new Edge, Brave, Vivaldi, Opera)... but Firefox, old Edge and Internet Explorer were fine (didn't check in Safari yet). As such we have two questions: 1.) What is a version number from about 2 weeks ago when things appeared to be working for us so that we can link to the older version to verify the issue (and the diff between the versions) 2.) Has anyone else encountered this issue? or know what in our code might trigger this issue? ... View more