In the next quarter, we're going to focusing some of our efforts on CD optimizations - building, testing and deploying our software quicker. In order to gauge this, we're finding the need to instrument Go actions and report on them. What we have done so far is to configure log analysis of the default go-server.log. This gives us the ability to report on duration for specific jobs, stages and pipelines. However, 1 thing that isn't reported in the log file is pipeline triggers, or pipeline labels. Without having an "upstream pipeline" or pipeline label, we have no way of tracking performance across pipelines.
I was wondering if any other Go users are monitoring their Go performance, and how you are doing it? Has anyone else come across this challenge, and what are possible solutions to create an association between pipeline instances?
Here's a sample of some logs (obfusticated): In the example below, "MyPipeline" triggers "MyDownstream", and I'm looking for any field that will allow me to create an association between the 2 events. Thanks
[Agent [xxxxx, 10.0.20.1, xxxx-xxxxx-xxxxx-xxxxx, yyyyy-yyyyy-yyyyy]] is reporting status and result [Completed, Passed] for [Build [MyPipeline/36/MyStage/5/myJob/162494]]
[Agent [xxxxx, 10.0.20.1, xxxx-xxxxx-xxxxx-xxxxx, yyyyy-yyyyy-yyyyy]] is reporting status and result [Completed, Passed] for [Build [MyDownstream/1/MyStage/1/myJob/162497]
Please sign in to leave a comment.