Can't display forecast on Grafana and how to adjust Yhat upper and lower.

[floppy84]

Hi all,

Thanks for your great work about this tool. I try it since a month, and i really appreciate it.

My issue is probably not an issue, but i try to understand how to do this.

On my on premise grafana, i try to display the forecast value provided by prophet metrics:

But i am not able to display value predicted forcasted in futur.
Did i miss something ?

I have other issue, on previous graph you can see that data model seem to work pretty well but on the bellow not really , is there a way to adjust yhat ? or do we need to wait more time for acurate value ?

.

For information :
I also compared data, on Grafana cloud that provides ML feature. They use same prophet tool for this. They provide options for adjusting some values and forecast seem to be possible 👍

Here the setting that you can configure, is there a way for doing the same on my side ? :

[saswat0]

The issue here is not with Grafana, but with prometheus db. Prometheus cannot push metrics of the future (predicted metrics) for grafana to scrape from. The ML plugin that you're referring to runs inference on grafana's end (after getting the metrics from prometheus). If you wish to see these predicted values, then some other method of posting will have to adopted
I might be wrong. The maintainers can probably comment correctly

[floppy84]

Hi, ok well i use victoria db as time series database and grafana is connected to it. So i am not collecting data on prometheus TSDB for display data on grafana. Is there an easy way for told to victoriadb to allow to store predicted value in futur ? regards

[sesheta]

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]

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]

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

/close

[sesheta]

@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.