Hello!
This is not a bug! ^^
Is it possible that when the local instance doesn’t send a heartbeat to g+, we receive a message (an email, for example) to notify us?
1 Like
That’s a good idea!
You’re not the first to ask either 
That said, it needs to be done smartly so you don’t get spammed, and especially if someone deliberately disconnects Gladys, they shouldn’t receive continuous alerts for two weeks 
2 Likes
So why not have a single, unique email. That way the user, even if it’s intentional, would receive confirmation of their Gladys Plus service being taken offline, right?
1 Like
Like at work : https://icinga.com/demo/dashboard 
1 Like
A bit like netdata cloud does (monitoring). It’s an email with a delay to avoid being spammed.
1 Like
Yes!
So does that seem feasible and not too costly for you to integrate this kind of feature into Gladys Plus?
It’s doable, though it should be prioritized against other features related to Gladys Plus, because it’s not a trivial development either
Roughly, including the specs, development, testing, and release, about 2 days of work, I think.
Maybe we could move it to « Feature requests » to keep a record of the request?
1 Like
I’ll take care of it asap
Edit: oh well I didn’t say anything! Thanks @Tlse-vins
I wanted to see all the Gladys Plus feature requests in competition.
I only found one, and it’s the same as this one that I’d already voted for…
Anyway, I have the impression that some feature requests get forgotten after a certain time ^^’
There’s Alexa integration too!
I do my best; but if a request isn’t asked for often enough, I don’t prioritize it.
So we can close this request