<?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: Getting 401 unauthorized  even after enabling SIM module in Appdynamics Container in Splunk AppDynamics</title>
    <link>https://community.splunk.com/t5/Splunk-AppDynamics/Getting-401-unauthorized-even-after-enabling-SIM-module-in/m-p/717928#M729</link>
    <description>&lt;P&gt;This took me a "minute" to figure this one out. Turns out that in my controller-info.xml, at host tag, I had included an unnecessary fwd slash.&amp;nbsp; That corrupted my whole rest api url resolution. Check if that is not the case with you. As a general rule, keep host-name clean, port clean, and ssl option clean.&lt;/P&gt;</description>
    <pubDate>Mon, 10 Jul 2023 14:23:06 GMT</pubDate>
    <dc:creator>Mondli_Mabaso1</dc:creator>
    <dc:date>2023-07-10T14:23:06Z</dc:date>
    <item>
      <title>Getting 401 unauthorized  even after enabling SIM module in Appdynamics Container</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Getting-401-unauthorized-even-after-enabling-SIM-module-in/m-p/717926#M727</link>
      <description>&lt;P&gt;Hi Team,&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am trying to run appdynamics machine agent as a container to monitor the existing app containers. I have gone through the issue discussion and added this line in my environment file.&amp;nbsp;&lt;/P&gt;&lt;P&gt;APPDYNAMICS_SIM_ENABLED=true&lt;/P&gt;&lt;P&gt;But still I recieve the error log:&lt;/P&gt;&lt;P&gt;c8ebf9f96874==&amp;gt; [system-thread-0] 24 Jun 2022 13:04:05,719 DEBUG RegistrationTask - Encountered error during registration.&lt;BR /&gt;com.appdynamics.voltron.rest.client.NonRestException: Method: SimMachinesAgentService#registerMachine(SimMachineMinimalDto) - Result: 401 Unauthorized - content:&lt;/P&gt;&lt;P&gt;at com.appdynamics.voltron.rest.client.VoltronErrorDecoder.decode(VoltronErrorDecoder.java:62) ~[rest-client-1.1.0.187.jar:?]&lt;BR /&gt;at feign.SynchronousMethodHandler.executeAndDecode(SynchronousMethodHandler.java:156) ~[feign-core-10.7.4.jar:?]&lt;BR /&gt;at feign.SynchronousMethodHandler.invoke(SynchronousMethodHandler.java:80) ~[feign-core-10.7.4.jar:?]&lt;BR /&gt;at feign.ReflectiveFeign$FeignInvocationHandler.invoke(ReflectiveFeign.java:100) ~[feign-core-10.7.4.jar:?]&lt;BR /&gt;at com.sun.proxy.$Proxy113.registerMachine(Unknown Source) ~[?:?]&lt;BR /&gt;at com.appdynamics.agent.sim.registration.RegistrationTask.run(RegistrationTask.java:147) [machineagent.jar:Machine Agent v22.5.0-3361 GA compatible with 4.4.1.0 Build Date 2022-05-26 01:20:55]&lt;BR /&gt;at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) [?:?]&lt;BR /&gt;at java.util.concurrent.FutureTask.runAndReset(Unknown Source) [?:?]&lt;BR /&gt;at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) [?:?]&lt;BR /&gt;at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) [?:?]&lt;BR /&gt;at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) [?:?]"&lt;/P&gt;&lt;P&gt;Need solution on this.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Jun 2022 13:19:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Getting-401-unauthorized-even-after-enabling-SIM-module-in/m-p/717926#M727</guid>
      <dc:creator>Christopher_Ant</dc:creator>
      <dc:date>2022-06-24T13:19:09Z</dc:date>
    </item>
    <item>
      <title>Re: Getting 401 unauthorized  even after enabling SIM module in Appdynamics Container</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Getting-401-unauthorized-even-after-enabling-SIM-module-in/m-p/717927#M728</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;A href="https://community.appdynamics.com/t5/user/viewprofilepage/user-id/158965"&gt;@Christopher.Antonyraj&lt;/A&gt;,&lt;/P&gt;
&lt;P&gt;Thanks for asking your question on the Community. I did some digging around and found these two AppD Doc pages. Please let me know if they help out at all.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.appdynamics.com/appd/22.x/latest/en/infrastructure-visibility/server-visibility" target="_blank" rel="noopener nofollow noreferrer"&gt;https://docs.appdynamics.com/appd/22.x/latest/en/infrastructure-visibility/server-visibility&lt;/A&gt;&lt;A href="https://docs.appdynamics.com/appd/22.x/latest/en/infrastructure-visibility/monitor-containers-with-docker-visibility" target="_blank" rel="noopener nofollow noreferrer"&gt;https://docs.appdynamics.com/appd/22.x/latest/en/infrastructure-visibility/monitor-containers-with-docker-visibility&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;If I find anything else, I'll share it with you here.&lt;/P&gt;</description>
      <pubDate>Mon, 27 Jun 2022 17:48:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Getting-401-unauthorized-even-after-enabling-SIM-module-in/m-p/717927#M728</guid>
      <dc:creator>iamryan</dc:creator>
      <dc:date>2022-06-27T17:48:51Z</dc:date>
    </item>
    <item>
      <title>Re: Getting 401 unauthorized  even after enabling SIM module in Appdynamics Container</title>
      <link>https://community.splunk.com/t5/Splunk-AppDynamics/Getting-401-unauthorized-even-after-enabling-SIM-module-in/m-p/717928#M729</link>
      <description>&lt;P&gt;This took me a "minute" to figure this one out. Turns out that in my controller-info.xml, at host tag, I had included an unnecessary fwd slash.&amp;nbsp; That corrupted my whole rest api url resolution. Check if that is not the case with you. As a general rule, keep host-name clean, port clean, and ssl option clean.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jul 2023 14:23:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-AppDynamics/Getting-401-unauthorized-even-after-enabling-SIM-module-in/m-p/717928#M729</guid>
      <dc:creator>Mondli_Mabaso1</dc:creator>
      <dc:date>2023-07-10T14:23:06Z</dc:date>
    </item>
  </channel>
</rss>

