Commit time exporter should track deployed apps and not all the builds
See original GitHub issueThe Commit Time exporter should track and report only those apps that has running pods and not all the builds.
Currently creating e.g. binary build and annotating it causes commit time to show the commit timestamp, for example
Collected commit_timestamp{ namespace=bitbucket-binary, app=bitbucket-binary, commit=e2c4ef00468dfc10aad1bd2d4c9d470160a7f471, image_sha=sha256:7466229c5a9e241b6b32e48174e178ad8a5b0858a1d6617f27c9df87286b829d
} 1657806414.0
But the issue is that there may be 0 pods running such application, meaning pelorus is tracking builds and not deployed applications.
Issue Analytics
- State:
- Created a year ago
- Comments:7
Top Results From Across the Web
Environments and deployments - GitLab Docs
In a job script, you can specify a static environment URL. However, there may be times when you want a dynamic URL. For...
Read more >Configuration - Pelorus - Read the Docs
The commit time, deploy time, and failure exporters all rely on labels to indentify the application that is associated with an object. The...
Read more >Deployment Tracking - Datadog Docs
Use Datadog to track your deployments through version tags. ... shows all versions of the service that were active during the selected time...
Read more >Code components application lifecycle management (ALM)
Versioning lifecycle - You want to develop, deploy, and version-control your code components on a separate lifecycle to the other parts of your ......
Read more >Continuous deployment from Git using Cloud Build
You can use Cloud Build to automate builds and deployments to Cloud Run by ... to automatically build and deploy your code whenever...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The other reason you can’t reference running pods is because you might be comparing builds in one cluster (development) to pods in another (production) so the commit exporter won’t have that information
Closing as we’ve determined why we shouldn’t do this.