-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow Prometheus Rules to Publish Rules to Azure Managed Prometheus #1185
Comments
Without this feature, the workaround is to run |
So, it turns out bicep is a terrible format for machines to write to and looks to be more for humans to write. No go SDK for Azure Bicep. I thought of writing to ARM and then have a step to deploy to Azure after that in my pipeline. Then I discovered there is an Azure SDK for Go. There are very few examples online for Azure SDK for Go, but I hacked together my first go code I've written into this draft PR integrating updating Azure Monitor Alerting rules for Prometheus directly from Pyrra. Let me know if this is of interest to anyone. |
This is of interest to me/my org. We are facing similar limitations around managing SLOs in azure monitor. |
@ericmustin Made any progress on this in your org? We stalled out on SLOs with other priorities taking over. If I were to revisit this today, I think I'd look at using PrometheusRuleGroup in Azure Service Operator. Hopefully there would be minimal modification needed to get the current yaml generator to generate in the format required for the Azure Service Operator. |
Possibly related? |
@bbrandt Fwiw I was on an NDA with the cloud provider in question, so I can't really get into specifics, but I believe they were exploring some more curated solutions and tooling in this space. I can't seem to see anything about it in public docs so unless that changes I would defer to your suggestions, which seem appropriate. |
I have forked the repo, reviewed CONTRIBUTING.md, and am now looking at #361 as an example.
I'd like to add a
./pyrra az
command with similar behavior to thegenerate
command, but outputs a .bicep file in a format compatible with Azure Managed Prometheus. The format would be similar to https://github.com/Azure/prometheus-collector/blob/main/AddonBicepTemplate/recommendedMetricAlerts.bicep or the example .bicep below that I generated from sloth --> az-prom-rules-converter utility -->az bicep decompile --file $FILE
.If demand for this is low, I recommend that I just maintain the
az
command in a fork of pyrra. It is quite likely since Google Cloud Observability and Amazon CloudWatch both have managed solutions for creating and managing SLO's, Azure is frantically trying to catch up and build their own managed solution. If a managed SLO solution appears in Azure the value of./pyrra az
would likely have no reason to exist. Stating that the need may be temporary.Example Input
Example Bicep Output
The text was updated successfully, but these errors were encountered: