Cool things Event Studio can do

[mikewalker]

Automatic Analysis
- by pre-defining analysis items to monitor, thresholds to advise on, and data conditions to trap, common analysis tasks can be saved and automated so they notify relevant points-of-contact when an issue is found

Business Workflow Processing
- updating (multiple) databases when a data condition is trapped by running stored procedures
eg. consider the following scenario:

• a Helpdesk database logs employee requests for new computer items (eg monitor, RAM),
• a purchasing database logs the details of the order
• a shipping database logs details of where the items are located in the "chain"

An IT administrator could configure Event Studio to monitor & update these systems as required by the business procedure, and also notify relevant stakeholders at appropriate intervals of the process lifecycle.

Data Integrity and Error Checking / Reconciliation
- if a source system's data changes after a DW update build, Event Studio could perform a reconciliation to advise an administrator which records/numbers have since been changed, and by whom

Just a bit of a braindump, for the record

[Rocks]

What about setting up an email alert to send to an admin if a scheduled export job fails, or to send an email when it finishes, etc. etc.?

How would you do this?

[mikewalker]

I'd imagine you could query the C8 audit tables in EventStudio, and setup an agent to watch for any jobs (type = export) which have properties akin to Status = Finished or Status = Failed.

I'll look at the audit tables and if the info is in there will post a solution back here.

Cheers

[mikewalker]

Found some relevant data in the COGIPF_ACTION table of the Audit database (Note: you need to have already setup the auditing database; see admin guide for instructions on how to do this).

When you have the audit database setup, run this query:

Code: [Select]

select distinct
cogipf_localtimestamp,
cogipf_operation,
cogipf_target_type,
cogipf_target_path,
cogipf_status
from
cogipf_action
where

/* cogipf_localtimestamp <= '2007-06-28'
and cogipf_localtimestamp >= '2007-06-27'
and */
cogipf_target_path like '/Administration/Export/%'

order by
cogipf_localtimestamp desc


This will give you the basic data needed for an EventStudio agent to monitor.

The agent could be configured to run daily, or every hour, and query the COGIPF_ACTION table for any 'Export' records in the last hour.

It could then conditionally email an admin, or run a report, based on the 'Status' value of each record.

[bmilespal]

How would you tell Event Studio to update a SQL Server table after a condition is met?

[mikewalker]

Easy.

1. Create a stored procedure to UPDATE the table required.

2. Import the stored procedure into Framework Manager as an "updateable" stored procedure.

3. Re-publish package, including the stored procedure.

4. Load EventStudio, create your Agent criteria, then choose "Update Database" from the actions list. You should be able to select your newly imported stored procedure.

[FatCat]

I am looking for a cool way to show on a portal tab that a cube has been updated.

What I have done is have a portal page point to a report.  In the report are html items that have links to cube views.

This method allows users from a portal view to have a one click launch to open analysis studio.  Technically they are just opening a blank cube view but they do not know the difference.

Anyways next to the html item I want to be able to display if the cube was updated.
I currently have an event studio alert that queries the cube every 30 minutes and if there is a diff it sends out a cube complete e-mail.

I am thinking that if this event is either triggered or suppressed it should be logged somewhere and I can use that as an indicator on my html page.


Thoughts?

[mikewalker]

Maybe this thread will help you:

http://support.cognos.com/knowledgebase/googlesearch?load_kb_document=1&dr=kb1&uniqueid=135852

[saulcruz]

hey there, is there a way to send the event results (example 8 clients that spend more than 100,000 a day) in a table and execute a table valued stored procedure. Right now the SP is executed 8 times.