Closed timalacey closed 3 weeks ago
Hi @timalacey , issue 1 is already fixed and will be released soon. Regarding issue 2, contentId
was designed as a way to facet by stream URL, but using an integer instead of a string, which is more convenient in terms of NRQL performance. But I would like to know more about your specific use case. Is there any property from the video object/metadata that could cover your needs better?
Issue 1
nrAddVideoAttributes()
overrides nrCustomAttributes, meaningcontentId
cannot be overwritten withnrSetCustomAttribute(m.nr, "contentId", "abcd"))
https://github.com/newrelic/video-agent-roku/blob/f72903e766363f18150d19dda39d3aacf51abc61/components/NewRelicAgent/NRAgent.brs#L268Issue 2 The default value for
contentId
relies on thestreamUrl
, making it astreamId
. https://github.com/newrelic/video-agent-roku/blob/f72903e766363f18150d19dda39d3aacf51abc61/components/NewRelicAgent/NRAgent.brs#L1064Context: we have multiple streams per asset. So we want contentId to refer to the assetId of the content, similar to contentTitle.