Skip to content
This repository has been archived by the owner on Apr 5, 2019. It is now read-only.

Persistent Statuses #45

Open
jamcat22 opened this issue Feb 10, 2013 · 1 comment
Open

Persistent Statuses #45

jamcat22 opened this issue Feb 10, 2013 · 1 comment

Comments

@jamcat22
Copy link

If I change the status and add a message on Feb. 4 lets say, then don't on Feb. 5, the current status will still say down but Feb 5. says Up. Also, if a service says down, but as mentioned above it wasn't the day you posted the status, if you click on the current down symbol, it gives a check mark saying nothing is wrong.

@deanml
Copy link

deanml commented May 20, 2014

I have similar problems as posted on the wiki where after using the api to post an event, the service page still shows the current status to be whatever is was before the posted event. Double posting events seem to be a workaround to the problem in part. I've played around with caching and many other mechanisms in my code but have not had any success.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants