Status report of OBIEE services ( Start/Stop activity)

User_E9OMM

Hi,

Scenario :

Consider any particular day.

On that day, for 3 times OBIEE services had to restart. 

In the morning at 10AM, OBIEE was made to stop and it was up right after 5 min, that is at 10.05AM

In the afternoon, due to certain reasons it went down at round 3PM and we had to start OBI services and it was up by 3.10PM

Similarly in the night at around 9PM, OBI services stopped running due a failure and it took around 20 min to start the application, that is by 9.20PM it was up.

Now here, OBIEE was not available for a period of (5+10+20 = 35 Min)

Question - Is there a way where we can capture this downtime (by using any script or any existing feature in OBIEE) ?

Any automated way ? Our main job is to capture these details and create a weekly OBIEE services status dashboard.

Presently we are doing it manually. We check the log file and capture the downtime. Also sometimes by observing the computer clock.

Regards

AM

Gianni Ceresa

Hi,

I guess you first have to clearly define what you want to monitor: OBIEE can be up and running but queries not going anywhere and logins refused, this can be considered downtime in a way. Or you maybe take the simple approach of "bi server processes" UP = up, one or more down = downtime.

Based on this definition of what is "downtime" the way to automate this checks are different and also depends on the version (which you do not mention at all).

Of course you can't really ask OBIEE to tell you when it's down (as it's down), so this kind of information is generally collected by an external tool/solution which is also supposed to alert you or restart the processes.

You can also have a simple script scheduled by cron to run every minute and checking if OBIEE is up or down. At any status change it will enter a row in a database or something like that and this is the source of your dashboard.

User_E9OMM

Thanks Gianni.

Let me correct the word "Downtime". By Downtime, I mean how much time OBIEE was down or not available for analysis.

But a script ( with cron scheduler) that you have mentioned, is something we are looking it.

We want a scheduler script that can monitor how much time the OBIEE was not available for querying and insert the record into the db table which we can further utilise for creating analysis in OBIEE.

Regards

AM

[Deleted User]

1877648 wrote:Let me correct the word "Downtime". By Downtime, I mean how much time OBIEE was down or not available for analysis.

Important distinction as .../analytics/saw.dll not responding will also mean "down" then since a running OBIS without OBIPS is useless

Gianni Ceresa

With this kind of definition you will ideally need to test a login and executing an analysis. Perfectly doable by script, but of course will require a bit more than just "process up or down".

And also be ready to have a possible gap between what you detect as downtime and what users can report as downtime : if one of your sources database is down the result is OBIEE up and working fine on other sources, but your users will report you that as a downtime.

OBIEE is always guilty for any database issue because users see OBIEE on their screen ...