We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi During automatic resource conversion by operator seems like data inside attachMetadata is lost
attachMetadata
Following ServiceMonitor
apiVersion: monitoring.coreos.com/v1 kind: ServiceMonitor metadata: name: node-exporter namespace: monitoring spec: attachMetadata: node: true endpoints: - metricRelabelings: - action: drop regex: /var/lib/kubelet/pods.+ sourceLabels: - mountpoint port: metrics scheme: http scrapeTimeout: 10s jobLabel: app.kubernetes.io/name selector: matchLabels: app.kubernetes.io/instance: node-exporter app.kubernetes.io/name: node-exporter
results in following VMServiceScrape
apiVersion: operator.victoriametrics.com/v1beta1 kind: VMServiceScrape metadata: name: node-exporter namespace: monitoring spec: endpoints: - attach_metadata: {} metricRelabelConfigs: - action: drop regex: /var/lib/kubelet/pods.+ sourceLabels: - mountpoint port: metrics scheme: http scrapeTimeout: 10s jobLabel: app.kubernetes.io/name namespaceSelector: {} selector: matchLabels: app.kubernetes.io/instance: node-exporter app.kubernetes.io/name: node-exporter
as you can see now attach_metadata is an empty object
attach_metadata
no errors observed in VMOperator logs
The text was updated successfully, but these errors were encountered:
Must be fixed at v0.43.0 release
Sorry, something went wrong.
Haleygo
No branches or pull requests
Hi
During automatic resource conversion by operator seems like data inside
attachMetadata
is lostFollowing ServiceMonitor
results in following VMServiceScrape
as you can see now
attach_metadata
is an empty objectno errors observed in VMOperator logs
The text was updated successfully, but these errors were encountered: