Sorry i might be slightly confused. When i watch the DT video and follow the guide ( https://www.youtube.com/watch?v=Qy4Ge8HIzEk) They just enter the URL. When i do this for my production environment it works fine. When i do it for my test environment, it does not work.
So it seems it’s not in VSCode where i added the path to my keys / certificates that is the issue.
However it seems more to be an issue with VSCode (DT Extension) That will not accept a Self signed certificate when connecting to the environment.
So you’re using the VS Code Dynatrace extension. The issue is most likely that you don’t have the correct certificate generated for this environment. When you switch between environments within the extension, you also need to add the key and the URL go through the entire setup process again. That should resolve your problem. As it stands, it looks like you’re trying to use a production certificate in the test environment.
HI @ArneV
Therefore, I suggest setting up the extension for this repository again.
It looks like an incorrect URL is being used as if the tenant ID were wrong.
Well it’s not a wrong URL. It’s a correct URL, howver VSCode / Dynetrace extension cannot / Will not work for a SSL certifthat is self signed. In the browser it was marked with exception used to go to webpage, so a clear indication that the SSL somehow was not compleatly good.
We had however the certification chain for this self signed certificate, when this also was uploaded to DT it worked.
How i can connect to my DT environment / See the extensions / Upload my development.
Unfortunately the YouTube videos showing how to build a SQL Extension seems to be wrong with the current version.