AnsweredAssumed Answered

Admin Errors Queue Depth

Question asked by Marta Benedetti on Jan 13, 2021
Latest reply on Jan 18, 2021 by Marta Benedetti

Like • Show 1 Like1
Comment • 4

Hi community,

I'm using RSA IGL 7.1.1 and admin errors keep coming.

Right now IGL is used only for for user, accounts and entitlement collection, no custom tasks and provisioning.

I've never changed these variables.

WF_QUEUE_DEPTH_DURATION_WARNING
WF_QUEUE_DEPTH_DURATION_ERROR
WF_QUEUE_DEPTH_DURATION_CRITICAL

I see a lot of admin errors like: OK: Monitor[jobq#Normal] has taken 0 ms to process an item.

Since it says it has taken 0 ms, I wonder why this is an admin error.

What should I do to avoid these admin errors?

Thanks

Marta

Ian Staines

Jan 13, 2021 10:46 AM

Correct Answer

These are not errors, they are WARN level log messages.

If you do not want to see them you can raise the level as per the following article.

000036324 - New feature for RSA Identity Governance & Lifecycle 7.1: Workflow System Status

This statistical data is reset when the server is restarted. There are some artifacts in the logging process that may cause false positives for some statistics when the server is recently started. This is resolved in later versions of the product.

See the reply in context

1 person had this question

Outcomes

Ian Staines

Jan 13, 2021 10:46 AM

These are not errors, they are WARN level log messages.

If you do not want to see them you can raise the level as per the following article.

000036324 - New feature for RSA Identity Governance & Lifecycle 7.1: Workflow System Status

2 people found this helpful

Actions

Marta Benedetti Jan 15, 2021 9:23 AM

Hi Ian Staines,

thanks for the article.

If I look in aveksaServer.log though those messages I see under Amin Error are INFO, not WARN

The article suggest to set a higher lever in the variable WF_QUEUE_DEPTH_DURATION_WARNING: I wonder if this change will prevent from logging the INFO log message.

Check from aveksaServer.log looks like I should set 8000 as the new threshold.

Thank you

Marta

Actions

Ian Staines

@ Marta Benedetti on Jan 15, 2021 1:12 PM

Yes sorry my mistake INFO.

What is the business requirement to prevent these log messages? They are useful to Customer Support for some types of issues.

Actions

Marta Benedetti @ Ian Staines on Jan 18, 2021 3:31 AM

There is no business requirement right now, the customer just need to know why these messages appears.

The problem is that since the message is something like "has taken 0 ms to process an item" it looks like everything is ok, so I wonder if there is a way to hide this message.

If I am wrong though, I'd like to know how I can discover the problem that is causing these messages.

Thank you

Marta

Actions

4 Replies

Ian Staines Jan 13, 2021 10:46 AM
Unmark Correct
Correct Answer
These are not errors, they are WARN level log messages.

If you do not want to see them you can raise the level as per the following article.

000036324 - New feature for RSA Identity Governance & Lifecycle 7.1: Workflow System Status

This statistical data is reset when the server is restarted. There are some artifacts in the logging process that may cause false positives for some statistics when the server is recently started. This is resolved in later versions of the product.
2 people found this helpful
Like • Show 2 Likes2
Actions
Marta Benedetti Jan 15, 2021 9:23 AM
Mark Correct
Correct Answer
Hi Ian Staines,

thanks for the article.
If I look in aveksaServer.log though those messages I see under Amin Error are INFO, not WARN

The article suggest to set a higher lever in the variable WF_QUEUE_DEPTH_DURATION_WARNING: I wonder if this change will prevent from logging the INFO log message.
Check from aveksaServer.log looks like I should set 8000 as the new threshold.

Thank you
Marta
Like • Show 0 Likes0
Actions
- Ian Staines @ Marta Benedetti on Jan 15, 2021 1:12 PM
  Mark Correct
  Correct Answer
  Yes sorry my mistake INFO.
  
  What is the business requirement to prevent these log messages? They are useful to Customer Support for some types of issues.
  Like • Show 0 Likes0
  Actions
  - Marta Benedetti @ Ian Staines on Jan 18, 2021 3:31 AM
    Mark Correct
    Correct Answer
    There is no business requirement right now, the customer just need to know why these messages appears.
    The problem is that since the message is something like "has taken 0 ms to process an item" it looks like everything is ok, so I wonder if there is a way to hide this message.
    If I am wrong though, I'd like to know how I can discover the problem that is causing these messages.
    
    Thank you
    Marta
    Like • Show 0 Likes0
    Actions

Admin Errors Queue Depth

Outcomes

Related Content

Recommended Content