You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can successfully compile my dynatrace based spring boot application now. I can see it use the bindings to get the oneagent from the DT saas server.
My problem is at runtime, i don't think it is then successfully using the bindings to connect to dynatrace.
Do i need to set environment variables to make it connect to my dt server with the api key?
We are deploying in GCP cloud run
Any help gladly accepted - in cloud run it is pertty much impossible to examine the oneagent log - i did look at the container that was created and the one agent dynatrace-env.sh does not look set up
The text was updated successfully, but these errors were encountered:
I think these should really be set in the layer - any chance we can fix?
We specifically do not set these in the layer because they are secrets and you do not want to put secret information into a container image, as it will be very easy to leak that information.
You need to provide the same binding information at runtime. There is a small helper that will take the binding information and translate that to the DT_* env variables in memory.
You can set the environment variables directly at runtime if you prefer that approach. Using bindings is recommended, as these are typically a bit more secure (although that depends on your container orchestrator).
I can successfully compile my dynatrace based spring boot application now. I can see it use the bindings to get the oneagent from the DT saas server.
My problem is at runtime, i don't think it is then successfully using the bindings to connect to dynatrace.
Do i need to set environment variables to make it connect to my dt server with the api key?
We are deploying in GCP cloud run
Any help gladly accepted - in cloud run it is pertty much impossible to examine the oneagent log - i did look at the container that was created and the one agent dynatrace-env.sh does not look set up
The text was updated successfully, but these errors were encountered: