nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

Track failures of scheduled agents and BIP reports

Debadrita Ghosh-Oracle

Hi,

OBIEE had a few system tables like s_nq_job, XMLP_SCHED_JOB etc. through which status of failed agent/BIP jobs could be tracked and reported to users automatically. Is there any feature in OAC with which these can be tracked? Using Monitor Deliveries option is a manual job.

Thanks

Debadrita Ghosh

Find more posts tagged with

Agents

BI Publisher

Scheduling or Agents

Accepted answers

All comments

Gianni Ceresa

Have a look at OCI Logging, it could give you a way to get what you look for. I believe it's most "details" you can get, don't expect access to those tables when using OAC.

Another option could be to just look at what API calls is made by the monitor deliveries page and write a script to get data out of it and then do what you need to do with it.

https://docs.oracle.com/en/cloud/paas/analytics-cloud/acoci/administer-services.html#GUID-EFE621A5-85F4-459D-96C2-0AEF3B837145

https://blogs.oracle.com/analytics/post/access-oac-logs-with-oracle-cloud-infrastructure-logging

GayathriAnand-Oracle

For OAC Agents, you can use Usage Tracking to find the details of a specific agent, error message, etc.

For BI Publisher catalog objects auditing check the following doc : https://docs.oracle.com/en/cloud/paas/analytics-cloud/acabi/audit-data-publisher-catalog-objects.html#GUID-6E05FC42-D2CF-4658-B9A1-595968CC8FA6

TetyanaH-Oracle

Good video in earlier community post on configuring OCI Logging in OAC:

Monitor OAC through the OCI Logging Service — oracle-products

Debadrita Ghosh-Oracle

Hi @GayathriAnand-Oracle ,

Thanks a lot for the ideas. The BI Publisher audit meets our requirements. For the Agents scenario, usage tracking can't really distinguish between scheduled jobs and normal reports, but it's still better than nothing! Thanks again.

Debadrita Ghosh-Oracle

Hi @Gianni Ceresa ,

Thank you for the ideas. OCI logging may not really be suitable for our needs as we only want to track the scheduled agents that have failed to run on the current date. Please correct me if I'm wrong here.

As for APIs, I could not find any documented API for the 'Monitor Deliveries' functionality in OAC. Can we still use the API being called from the page? It would be very helpful if you could provide some document or insight on how to do this, as I'm new to APIs.

Thanks

Debadrita Ghosh

Gianni Ceresa

APIs aren't always documented, in OAC not even 10% of the APIs are documented (actually the documented APIs are different APIs than the one the tool really use when you click through the GUI).

But an API is just calling a URL and getting something back: what you do with it and how, it's up to you. Of course it could change or be removed with the next upgrade, but that's a risk you implicitly accept by adopting OAC: it's a black box, the features that aren't directly available you have to find them yourself with risk things change every 2 months.

The OCI Logging approach is the one that sounded like the cleanest one: because you have no access to OAC behind the scenes tables or logs, that info is being made available through that service. I didn't use it so far, but it lists many things that are being captured by it. The BIP scheduler and agents scheduler logs should also be there.

If they aren't, you should raise an idea to add them there, because that seems to be the official way to get access to that king of "logging" info for everything else.

GayathriAnand-Oracle

If you are looking to monitor just the agents, usage tracking is still the best possible option until our publicly documented APIs expand scope and become available.