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

App and retraining never start #171

Closed
laburnumT opened this issue Dec 25, 2021 · 5 comments
Closed

App and retraining never start #171

laburnumT opened this issue Dec 25, 2021 · 5 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@laburnumT
Copy link

Hi all,

I attempted to use the prometheus anomaly detector to detect anomalies in my metrics. I set it up to track just one metric (quite a few targets though). However both times I ran the program it seemed to train just fine, but it seems to hang after finishing the initial training run. I don't get the message "Initializing Tornado Web App", nor the "Will retrain model every x minutes". Nothing happens after the retraining period passes, and no metrics ever get exposed on :8080/metrics.

Running the program, but on just one instance of the metrics (which concludes in ~3 minutes), works without issue, and none of the above mentioned problems/symptoms occur. One theory I have is that the training took longer than the retraining interval, but I do not know why that would be an issue.

I have attached a copy of the logs (without the direct training data, but I can upload that if necessary).

obfus.log

@sesheta
Copy link

sesheta commented Mar 25, 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

1 similar comment
@sesheta
Copy link

sesheta commented Jun 23, 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 Jun 23, 2022
@sesheta
Copy link

sesheta commented Jul 23, 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 Jul 23, 2022
@sesheta
Copy link

sesheta commented Aug 22, 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 Aug 22, 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 Aug 22, 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