Feedback channel for CI/CD Pipeline Observability

[JohannesBraeuer]

Within the last few months, we set the foundation for Dynatrace CI/CD pipeline observability, which empowers you to monitor and analyze your organization's software engineering practices and delivery processes. These insights help streamline CI/CD pipelines, enhance developer productivity, and optimize your Internal Development Platform (IDP). Please read Observability throughout the software development lifecycle increases delivery performance for more details.

The official start of the preview: March, 2025

Join our preview program to gain early access to new features and provide valuable feedback to help shape the future of CI/CD Pipeline Observability with Dynatrace.

Preview is available for:

* GitLab- [Getting started](link-to-docu-page)

In preparation are:

* ArgoCD

* Azure DevOps Pipeline

* GitHub

Preview Overview

This preview provides guidelines for configuring Dynatrace and the external IDP tool to collect relevant data points. These guidelines represent best practices defined by Dynatrace but can be adapted to meet your specific requirements. Alongside data ingestion, the preview offers ready-made dashboards that empower you to gain deeper insights into your CI/CD pipelines.

Below are examples of GitLab dashboards. 

GitLab Pipeline Pulse:

GitLab Merge Request Insights:

 

Preview Characteristics

In general, the preview has the following characteristics:

• A Monaco package is provided to facilitate Dynatrace configuration.
• The Dynatrace setup includes OpenPipeline configuration and dashboards.
• A comprehensive how-to guide is available for configuring the third-party tool.
• The preview follows a data push approach, meaning the third-party tool sends the data rather than Dynatrace pulling it.
• The OpenPipeline configuration normalizes proprietary data into Software Development Lifecycle Events.
• Ready-made dashboards are provided to offer insights into CI/CD pipeline activities.

 

Share your Feedback

We welcome your feedback on the preview program, which can include but is not limited to the following areas:

• Did you encounter any issues with the preview?
• Are the provided dashboards relevant to your needs? What insights are missing?
• Which IDP tools that define your CI/CD pipelines are crucial for you to gain more insights into?
• Does the data ingestion approach (e.g., Webhooks) work well with your setup?
• Do you require a more comprehensive overview of your software delivery processes as reported by the DORA metrics?
• Any other comments or suggestions.

Your feedback is essential in helping us improve and deliver a more effective observability solution, ensuring it delivers maximum value to your software engineering and delivery processes. Your feedback will directly influence our product's evolution, making it more effective for all users. Thank you for your participation!

[lubrman]

hi @JohannesBraeuer  

Do you know if there are any plans for comprehensive observability monitoring for Bitbucket? Just like GitHub or GitLab, Bitbucket also has the ability to run workflows. It could be interesting to monitor the workflow execution directly within the code repository, rather than relying solely on tracing via Jenkins — although that is, of course, also great.
I know that Bitbucket currently doesn't support OpenTelemetry or other significant observability solutions. So the only option for now is probably either to enrich the data with OpenTelemetry manually, or to use the Dynatrace ingest API and export the data there using an external script — is that correct?


script:
- >
curl -X POST "https://{environmentid}.live.dynatrace.com/api/v1/events"
-H "Authorization: Api-Token $DT_API_TOKEN"
-H "Content-Type: application/json"
-d '{
"eventType": "CUSTOM_DEPLOYMENT",
"attachRules": {
"tagRule": [
{
"meTypes": ["SERVICE"],
"tags": [{"context": "CONTEXTLESS", "key": "app", "value": "my-app"}]
}
]
},
"deploymentName": "Bitbucket Pipeline Build #$BITBUCKET_BUILD_NUMBER",
"ciBackLink": "$BITBUCKET_GIT_HTTP_ORIGIN",
"customProperties": {
"branch": "$BITBUCKET_BRANCH",
"commit": "$BITBUCKET_COMMIT"
}
}'