What happens when Jopr database goes down

[dfilgueiras80]

If the database used by JOPR goes down (crash), can Jopr send alerts ? Ex: "My Database goes down!!!"

I will install the Jopr to use an Oracle database. My application use that databse too, and I want to know when this datatabase goes down.

Car JOPR alert in this scenario ? How can I configure JORP server to alert right way ?

[dfilgueiras80]

"dfilgueiras80" wrote:
If the database used by JOPR goes down (crash), can Jopr send alerts ? Ex: "My Database goes down!!!"

I will install the Jopr to use an Oracle database. My application use that databse too, and I want to know when this datatabase goes down.

Car JOPR alert in this scenario ? How can I configure JORP server to alert right away ?

[ips]

No, Jopr relies on the database for triggering alerts and just about all other functionality. I'd recommend setting up some other process to monitor the Jopr database - even a small script that pings the DB and is executed periodically via cron would do the trick.

[mazz]

we should add some kind of alerting mechanism when this happens.

Even if its something small like, "send an email to [e-mail] when the Jopr detects a Db backend failure".

This obviously would have to be outside of the normal alert subsystem, because of the backend DB is down, the alert subsystem won't be able to do its job.

[ips]

Yeah, that would be cool. As far as what configuration would be needed, I think we'd want to add a new property to rhq-server.properties which is a list of email addresses to send these low-level DB-down alerts to, e.g.:

rhq.server.fatal-alerts.to-addresses = [e-mail], [e-mail]

The SMTP host and port for normal alerts are already configured via rhq-server.properties. We could reuse those for the low-level alerts.