Scraping a virtual machine with promitor helm chart #2107
-
Hello! I've recently started using promitor so I might be going about this the wrong way. I'm using the promitor helm charts for the scraper and resource discovery. I've successfully scraped my SQL instances with this approach. However, I'm having some issues adding additional resources to be scraped (The resource discovery seems to work). When I'm installing the helm chart for the agent scraper I'm getting the following error:
The only difference here is that the virtual machine I am trying to scrape (as opposed to the SQL database) is in another subscription and resource group entirely. So I suspect this is where the issue is - and I configured something the wrong way. Here are the values from my scraper and resource discovery charts:
Am I missing something? I expect this to be able to continue scraping my SQL instances, in addition to scraping the virtual machines in the other resource group and subscription. Note: I tried adding the resourceGroupName and subscriptionId directly to the scraper configuration (the two lines I commented out) - but it fails the same. I did also find this thread - but the links to the example linked in there is not working.. Any nudge in the right direction is appreciated. Thanks. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 8 replies
-
Hi, This exception typically means that the configuration is invalid and there's a bug open for this, but I thin the problem is here: ## Metric Declaration YAML
azureMetadata:
tenantId: redacted
subscriptionId: redacted
resourceGroupName: redacted
cloud: "Global"
metricDefaults:
aggregation:
interval: 00:05:00
scraping:
schedule: "*/5 * * * *"
metrics:
# Get cpu percent metric from sql database
- name: azure_sql_database_cpu_percent_discovery
description: "The CPU percentage used by an Azure SQL Database."
resourceType: SqlDatabase
labels:
app: promitor
customer: customer
resource: sql
azureMetricConfiguration:
metricName: cpu_percent
aggregation:
type: Average
resourceDiscoveryGroups:
- name: sql-databases
- name: azure_virtual_machine_percentage_cpu
description: "Average percentage cpu usage on an Azure virtual machine"
resourceType: VirtualMachine
- resourceGroupName: redacted
- subscriptionId: redacted
labels:
app: promitor
customer: customer
resource: vm
azureMetricConfiguration:
metricname: Percentage CPU
aggregation:
type: Average
resourceDiscoveryGroups:
- name: virtual-machines Did you try it running like this? |
Beta Was this translation helpful? Give feedback.
Hi,
This exception typically means that the configuration is invalid and there's a bug open for this, but I thin the problem is here:
## Metric Declaration YAML azureMetadata: tenantId: redacted subscriptionId: redacted resourceGroupName: redacted cloud: "Global" metricDefaults: aggregation: interval: 00:05:00 scraping: schedule: "*/5 * * * *" metrics: # Get cpu percent metric from sql database - name: azure_sql_database_cpu_percent_discovery description: "The CPU percentage used by an Azure SQL Database." resourceType: SqlDatabase labels: app: promitor customer: customer resource: sql azureMetricConfiguration: metricName: cp…