-
Notifications
You must be signed in to change notification settings - Fork 48
Extended databricks operator to report metrics into Prometheus #104
Conversation
storey247
commented
Nov 12, 2019
- Extended workflow of controllers to report upstream call times and counts
- Identified a couple of issues with linting and patched as found
- Refactored some code to make it more readable
Azadehkhojandi
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome work and I learnt a lot by reviewing your pr.
Could you please cherry-pick only changes related to metrics and apply the minor changes I requested?
|
/azp list |
|
CI/CD Pipelines for this repository: |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@Azadehkhojandi thanks for the great feedback, I've tidied things up now and actioned the feedback you requested. The PR should now only contain the commits relevant to the metrics work I did (apologies for the confusion). Looking forward to your feedback |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
e152cb6 to
8960a26
Compare
8960a26 to
bfbe50c
Compare
bfbe50c to
0fe919d
Compare
0fe919d to
9608cad
Compare
|
After our discussion earlier this week I have rebased this PR on latest master and dropped out most of the kustomize changes (which are essentially incorporated into the kubebuilder upgrade now in master) with a couple of minor tweaks left in to enable prometheus to connect. I've tested this locally by doing the following in the devcontainer
|
Extended databricks operator to report metrics into Prometheus (Azure#104)
