How to change default servicemonitors interval

[yasharne]

Hi
As the number of nodes on the openshift cluster increased, our Prometheus instances could not handle the amount of load, so I wanted to decrease the interval of service monitors, I tried to increase the interval of node-exporter's service monitor, but as it is managed by the operator, it will get reverted to the default value.
Is it possible to change the interval?

[a-thorat]

@yasharne
I was able to change it under node-exporter ServiceMonitor and not got override as well.
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
labels:
app.kubernetes.io/component: exporter
app.kubernetes.io/managed-by: cluster-monitoring-operator
app.kubernetes.io/name: node-exporter
app.kubernetes.io/part-of: openshift-monitoring
app.kubernetes.io/version: 1.6.1
monitoring.openshift.io/collection-profile: full
name: node-exporter
namespace: openshift-monitoring
spec:
endpoints:
- bearerTokenSecret:
key: ''
interval: 20s

Also note
interval
string
Interval at which metrics should be scraped If not specified Prometheus' global scrape interval is used.

Have you tried to change it CR Prometheus-k8s in opneshift-monitoring?
scrapeInterval
string
Interval between consecutive scrapes.
Default: "30s"

Please let me know if this works for you.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.