Skip to content
This repository has been archived by the owner on Jun 7, 2023. It is now read-only.

Are there any other requirements/configs in order to get the Fourier metrics? #186

Closed
m0sh1x2 opened this issue Jul 27, 2022 · 5 comments
Closed
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@m0sh1x2
Copy link

m0sh1x2 commented Jul 27, 2022

Hello,

I am trying to get the fourier metrics but at the moment only the Prophet ones are being generated.

Are there any other configurations that I have to set or any way to debug this?

Thanks,

Here are some example output metrics on a test container:

# HELP node_load1_prophet Forecasted value from Prophet model
# TYPE node_load1_prophet gauge
node_load1_prophet{container="node-exporter",endpoint="http-metrics",instance="_REDACTED_:9100",job="node-exporter",namespace="monitoring",pod="prom-prometheus-node-exporter-nwphj",service="prom-prometheus-node-exporter",value_type="yhat"} 0.4046080750387797
node_load1_prophet{container="node-exporter",endpoint="http-metrics",instance="_REDACTED_:9100",job="node-exporter",namespace="monitoring",pod="prom-prometheus-node-exporter-nwphj",service="prom-prometheus-node-exporter",value_type="yhat_lower"} -0.7237909896183755
node_load1_prophet{container="node-exporter",endpoint="http-metrics",instance="_REDACTED_:9100",job="node-exporter",namespace="monitoring",pod="prom-prometheus-node-exporter-nwphj",service="prom-prometheus-node-exporter",value_type="yhat_upper"} 1.5272604045815268
node_load1_prophet{container="node-exporter",endpoint="http-metrics",instance="_REDACTED_:9100",job="node-exporter",namespace="monitoring",pod="prom-prometheus-node-exporter-nwphj",service="prom-prometheus-node-exporter",value_type="anomaly"} 0.0
node_load1_prophet{container="node-exporter",endpoint="http-metrics",instance="_REDACTED_:9100",job="node-exporter",namespace="monitoring",pod="prom-prometheus-node-exporter-pf892",service="prom-prometheus-node-exporter",value_type="yhat"} 0.9695916895129116
node_load1_prophet{container="node-exporter",endpoint="http-metrics",instance="_REDACTED_:9100",job="node-exporter",namespace="monitoring",pod="prom-prometheus-node-exporter-pf892",service="prom-prometheus-node-exporter",value_type="yhat_lower"} -0.15150424867751713
node_load1_prophet{container="node-exporter",endpoint="http-metrics",instance="_REDACTED_:9100",job="node-exporter",namespace="monitoring",pod="prom-prometheus-node-exporter-pf892",service="prom-prometheus-node-exporter",value_type="yhat_upper"} 2.0849780861090497
node_load1_prophet{container="node-exporter",endpoint="http-metrics",instance="_REDACTED_:9100",job="node-exporter",namespace="monitoring",pod="prom-prometheus-node-exporter-pf892",service="prom-prometheus-node-exporte 
@m0sh1x2
Copy link
Author

m0sh1x2 commented Jul 29, 2022

I started learning python and ML, hope I can fix it soon.

Any help will be of great value in finding on how to make the Fourier metrics to start working

@sesheta
Copy link

sesheta commented Oct 27, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

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

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 27, 2022
@sesheta
Copy link

sesheta commented Nov 26, 2022

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

/lifecycle rotten

@sesheta sesheta added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 26, 2022
@sesheta
Copy link

sesheta commented Dec 26, 2022

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@sesheta
Copy link

sesheta commented Dec 26, 2022

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/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/test-infra repository.

@sesheta sesheta closed this as completed Dec 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

2 participants