Github secrets for integration with dynatrace site reliability guardian

[Manosirigosdyn7]

Hello i've searched everything and nowhere says where i can create secrets foe the integration with github in order to get notified for every change i do in the code from dynatrace. It says we need to complete these secerets in githab  DYNATRACE_URL_GEN3: ${{ secrets.DYNATRACE_URL_GEN3 }}
          ACCOUNT_URN: ${{ secrets.ACCOUNT_URN }}
          DYNATRACE_CLIENT_ID: ${{ secrets.DYNATRACE_CLIENT_ID }}
          DYNATRACE_SECRET: ${{ secrets.DYNATRACE_SECRET }}
          DYNATRACE_SSO_URL: ${{ secrets.DYNATRACE_SSO_URL }}

where do we find each one? Especially DYNATRACE_URL_GEN3

Thanks

[JohannesBraeuer]

Hello @Manosirigosdyn7 

I need a bit more details to help you. 

• Can you please point me to the documentation that describes how to complete the secrets in GitHub? I`m curious where this information is published because it looks that it is misleading. 
• The secret details (CLIENT_ID, SECRET, URN, etc.) you are looking for are required for an OAuth communication. This is however not needed for a GitHub integration. We recommend using GitHub Webhooks instead. Are you planning to integrate GitHub into Dynatrace using Webhooks? https://docs.github.com/en/webhooks 

BR, Johannes

[Manosirigosdyn7]

Hello Johannes,

what we want is the following:

when for example we make a new commit on github, we want an event to be sent to dynatrace and trigger a workflow. We tried this : https://github.com/Dynatrace/dynatrace-automation-tools

Thanks

[JohannesBraeuer]

Hello @Manosirigosdyn7 
Thanks. No I understand the use case. 

Instead of using the dynatrace-automation-tools, would it be an option for you to ingest the GitHub webhooks on the https://{your-environment-id}.live.dynatrace.com/platform/ingest/v1/events.sdlc endpoint? 

• Documentation: https://docs.dynatrace.com/docs/get-started/platform-engineering/pipeline-observability-sdlc-events/... 
• GitHub configuration: In GitHub, you need to configure a Webhook as follows: 

Advantage: You don`t need to change your GitHub workflows. 

Would this approach work for you?