You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- name: azure_my_sql_network_incoming_bytes
description: "Network incomming bytes on the server"
resourceType: MySql
azureMetricConfiguration:
metricName: network_in
aggregation:
type: Total
resources: # Optional, required when no resource discovery is configured
- serverName: stage-db
#type: Simple
- name: azure_my_sql_network_outgoing_bytes
description: "Network outgoing bytes on the server"
resourceType: MySql
azureMetricConfiguration:
metricName: network_out
aggregation:
type: Total
resources: # Optional, required when no resource discovery is configured
- serverName: stage-db
type: Simple
when I applied it (I'm using helm chart, but it doesn't matter here) I saw that configuration checking finished with error, here is part of log
looks like there are 2 errors in the docs:
field type is mandatory
Simple is the incorrect type of server, it should be Single
For the Flexible server all working fine
Working configuration for me
- name: azure_my_sql_network_outgoing_bytes
description: "Network outgoing bytes on the server"
resourceType: MySql
azureMetricConfiguration:
metricName: network_out
aggregation:
type: Total
resources: # Optional, required when no resource discovery is configured
- serverName: stage-db
type: Single
The text was updated successfully, but these errors were encountered:
app version 2.11
When I tried to declare a classic scrape (without discovery) for MySQL single server, I used this manual
https://docs.promitor.io/v2.11/scraping/providers/mysql/
Here is part of my scrape configuration
when I applied it (I'm using helm chart, but it doesn't matter here) I saw that configuration checking finished with error, here is part of log
looks like there are 2 errors in the docs:
type
is mandatorySimple
is the incorrect type of server, it should beSingle
For the
Flexible
server all working fineWorking configuration for me
The text was updated successfully, but these errors were encountered: