<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: RUM - OpenKit in iOS in Real User Monitoring</title>
    <link>https://community.dynatrace.com/t5/Real-User-Monitoring/RUM-OpenKit-in-iOS/m-p/204121#M4689</link>
    <description>&lt;P&gt;IMHO the biggest problems that might show up here are legal issues - imagine you have a 3rd-party SDK phoning home in your app you did not know - so this needs approval from your customers and also a way to turn it off. From technical perspective it should work, but pretty sure is not convenient. On iOS you would need the C based OpenKit and if you have a modern app - so no more Objective-C but only Swift you probably also want to write yourself a wrapper to the C APIs. And there won't be any auto-instrumentation. The manual instrumentation of the library should not be a problem with what Dynatrace OneAgent for iOS does - unless you also start instrumenting web request, which will brake the customers linking to service calls if their backend also is monitored, as there can only be one x-dynatrace header on a web request.&lt;BR /&gt;So from technical perspective it should be possible but from privacy issues I would strongly vote against it.&lt;/P&gt;</description>
    <pubDate>Mon, 06 Feb 2023 06:32:00 GMT</pubDate>
    <dc:creator>Patrick_H</dc:creator>
    <dc:date>2023-02-06T06:32:00Z</dc:date>
    <item>
      <title>RUM - OpenKit in iOS</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/RUM-OpenKit-in-iOS/m-p/204076#M4687</link>
      <description>&lt;P&gt;Hello, is it possible to use OpenKit on iOS?&lt;BR /&gt;(We have an sdk that will be used by different mobile apps but it is possible that these apps are already instrumented with Dynatrace, so I understand that the classic instrumentation would cause problems and OpenKit seems a similar solution)&lt;/P&gt;</description>
      <pubDate>Fri, 03 Feb 2023 23:54:51 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/RUM-OpenKit-in-iOS/m-p/204076#M4687</guid>
      <dc:creator>Stepu</dc:creator>
      <dc:date>2023-02-03T23:54:51Z</dc:date>
    </item>
    <item>
      <title>Re: RUM - OpenKit in iOS</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/RUM-OpenKit-in-iOS/m-p/204084#M4688</link>
      <description>&lt;P&gt;Interesting question. As a first reply, I would say it might work, but then it's not a usual use-case. You have to verify if one of the OpenKit languages is usable by you. In a last resort, you might also be able to implement it using the Dynatrace API, but it's way more difficult than using the mobile SDK in the first place.&lt;/P&gt;</description>
      <pubDate>Sat, 04 Feb 2023 11:23:07 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/RUM-OpenKit-in-iOS/m-p/204084#M4688</guid>
      <dc:creator>AntonioSousa</dc:creator>
      <dc:date>2023-02-04T11:23:07Z</dc:date>
    </item>
    <item>
      <title>Re: RUM - OpenKit in iOS</title>
      <link>https://community.dynatrace.com/t5/Real-User-Monitoring/RUM-OpenKit-in-iOS/m-p/204121#M4689</link>
      <description>&lt;P&gt;IMHO the biggest problems that might show up here are legal issues - imagine you have a 3rd-party SDK phoning home in your app you did not know - so this needs approval from your customers and also a way to turn it off. From technical perspective it should work, but pretty sure is not convenient. On iOS you would need the C based OpenKit and if you have a modern app - so no more Objective-C but only Swift you probably also want to write yourself a wrapper to the C APIs. And there won't be any auto-instrumentation. The manual instrumentation of the library should not be a problem with what Dynatrace OneAgent for iOS does - unless you also start instrumenting web request, which will brake the customers linking to service calls if their backend also is monitored, as there can only be one x-dynatrace header on a web request.&lt;BR /&gt;So from technical perspective it should be possible but from privacy issues I would strongly vote against it.&lt;/P&gt;</description>
      <pubDate>Mon, 06 Feb 2023 06:32:00 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Real-User-Monitoring/RUM-OpenKit-in-iOS/m-p/204121#M4689</guid>
      <dc:creator>Patrick_H</dc:creator>
      <dc:date>2023-02-06T06:32:00Z</dc:date>
    </item>
  </channel>
</rss>

