Promitor Scraper Agent has encountered an unexpected error #2017
-
ReportWe changed the promitor version to 2.0.0., because we had problems monitoring flexible server instance for Postgresql. Expected BehaviorA running promitor service Actual Behaviorpod/promitor-784f66c89d-z6m8w 0/1 CrashLoopBackOff 5 (2m39s ago) 5m40s Steps to Reproduce the Problem... ComponentScraper Version2.0.0 ConfigurationConfiguration: apiVersion: kustomize.config.k8s.io/v1beta1 resources:
configMapGenerator:
images:
Logs2022-04-25T06:39:50.508556579Z ██████╗ ██████╗ ██████╗ ███╗ ███╗██╗████████╗ ██████╗ ██████╗ PlatformMicrosoft Azure Contact Details |
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 2 replies
-
Hi, would you mind adding some more information on how you deploy please? Also, since you are upgrading I highly recommend going to v2.6.1. |
Beta Was this translation helpful? Give feedback.
-
We followed the information on https://docs.promitor.io/walkthrough/scrape-promitor-with-prometheus-on-azure-kubernetes-service.html The problem I got in version 1.5.0 was the message: And this message is correct because we are using flexible postgres servers. The info in azure for this kind of resource is: I implemeted the setting type: Flexible according the info from https://docs.promitor.io/configuration/v2.x/metrics/postgresql, but that doesn't seem to work. So I tried to have an update of promitor to see if that solved my problem. The metrics-decleration.yaml looks like this: version: v1
|
Beta Was this translation helpful? Give feedback.
-
I have now used version 2.6.1, but get the same error message. [12:55:34 INF] Booting up Promitor v2.6.1 running .NET .NET 6.0.3 - Thank you for using Promitor! I can stil run Version 1.5.0 but than I get the ResourceNotFound error |
Beta Was this translation helpful? Give feedback.
-
And what Helm configuration are you using? |
Beta Was this translation helpful? Give feedback.
-
Hello Tom, we don't use helm for deployment. We use kustomize |
Beta Was this translation helpful? Give feedback.
-
Would you mind sharing your configuration then please? |
Beta Was this translation helpful? Give feedback.
-
These are the two config files I use for promitor |
Beta Was this translation helpful? Give feedback.
-
Given you are upgrading to a new major version, you should align your configuration with the introduced breaking changes as announced in https://blog.tomkerkhove.be/2021/01/06/announcing-promitor-2-0-bringing-azure-monitor-metrics-where-you-need-them/ This migration guide should be able to help you: https://docs.promitor.io/walkthrough/migrate-from-1.x-to-2.x The problem you are having (at least) is that you are not defining any metric sinks. So what I would suggest is:
Feel free to let me know how it goes |
Beta Was this translation helpful? Give feedback.
Given you are upgrading to a new major version, you should align your configuration with the introduced breaking changes as announced in https://blog.tomkerkhove.be/2021/01/06/announcing-promitor-2-0-bringing-azure-monitor-metrics-where-you-need-them/
This migration guide should be able to help you: https://docs.promitor.io/walkthrough/migrate-from-1.x-to-2.x
The problem you are having (at least) is that you are not defining any metric sinks.
So what I would suggest is:
Feel free to let me know how it goes