brenti
Sailor

FAM 8.2 Alerts not working

Jump to solution

Hi

I'm currently encountering a problem with our FAM compliance alerts (they not coming through). We get FAM permission activities from the activity monitoring functionality used when onboarding a target application. Anyone on the forum know what could be causing the problem?

I don't see any errors or problems in the Event Manage, other core apps and the dccache file is sitting on 7GB usage.

Any assistance or guidance will be appreciated.

Regards,

Brent

0 Kudos
Reply
1 Solution

Accepted Solutions
brenti
Sailor

Hi Ranjith

Thanks so much your response. It's appreciated!

We have alert rules configured and have restarted Event Manager. Forensic activities took a while to catch up, but it eventually did (think it was due audit/events that are present in Elasticsearch.

With regard to the dccache file. Is there a limitation based on how big that file can grow (does it impact any functionality or performance while it's processing?

Restarting the Event Manager resolved the problem. it took very long to show us the relevant stats or results.

Thanks for input and help.

View solution in original post

0 Kudos
Reply
2 Replies
ranjith_koppu
SailPoint Employee
SailPoint Employee

If you are receiving activities from the target application, then FAM should be able to alert on them. Do you have alerts configured by creating alert rules or turning on alerts in the Resources --> Alerts ?

Regardless, once you have some alerts defined, its best to restart the Event Manager service. This service is responsible for sending out alerts.

BTW, the dccache is the cache that holds data classification categories for business resources (folders) so that this information can be added to the activities on the folders/files present inside the business resources.

0 Kudos
Reply
brenti
Sailor

Hi Ranjith

Thanks so much your response. It's appreciated!

We have alert rules configured and have restarted Event Manager. Forensic activities took a while to catch up, but it eventually did (think it was due audit/events that are present in Elasticsearch.

With regard to the dccache file. Is there a limitation based on how big that file can grow (does it impact any functionality or performance while it's processing?

Restarting the Event Manager resolved the problem. it took very long to show us the relevant stats or results.

Thanks for input and help.

0 Kudos
Reply