Skip to main content
Closed

IAM-SF: Make process flows logging optional

Related products:Intelligent Application Manager
  • November 22, 2021
  • 4 replies
  • 72 views
Victor Klaren
Jasper
Anne Buit
Robert Jan de Nie
+28
  • Victor Klaren
    Victor Klaren
  • Jasper
    Jasper
  • Anne Buit
    Anne Buit
  • Robert Jan de Nie
    Robert Jan de Nie
  • Andre te Raa
  • Jeroen van den Belt
    Jeroen van den Belt
  • Kevin Horst
    Kevin Horst
  • Roland van Aggele
  • René
  • Harm Horstman
    Harm Horstman
  • Erik Brink
    Erik Brink
  • Frank Wijnhout
    Frank Wijnhout
  • Ricardo
  • Robbert van Tongeren
    Robbert van Tongeren
  • Mark van den Berg
    Mark van den Berg
  • Mark Jongeling
    Mark Jongeling
  • Frank Glazenburg
  • BasBrugman
  • John Lunenburg
    John Lunenburg
  • Geurt
    Geurt
  • Freddy
    Freddy
  • kenterweeme
  • Sandro Burger
  • Martin
  • J. de Lange
    J. de Lange
  • Diana Kuipers
  • Maarten
  • Mark Kroes
  • ruudzijl
  • Marius Korff
    Marius Korff
  • Guido Bijl
    Guido Bijl
  • rbiram
    rbiram
  • Slavoljub Milojkovic

ArnoW
Apprentice

After upgrading to 2021.3 our SQL server get flooded by process flows schedule logging. After a week there are more than 600K records. Would be nice if we can make these schedule logs optional.

We even had some problems, see; 

 

Did this topic help you find an answer to your question?

4 replies

Mark Jongeling
Administrator
Forum|alt.badge.img+23

Hi Arno,

Coming with the 2022.1 release, you will be able to automatically let the process flow schedule log to be emptied leaving a number of log entries that can be set in IAM > Global settings.

We already released a hotfix for 2021.3 making sure all schedule logs will be emptied up to 200 items every minute. This limits the amount of storage it takes to store the log items. With the 2022.1 version, you will be able to set it to 1 for example. That will leave (at least) 1 record in the Schedule log every 5 minutes* as the dedicated system flow that runs every 5 minutes.*

* = subject to change

We cannot make logging optional as Indicium requires this logging to exist. The log is used by Indicium to see if a Scheduled system flow run is already picked up or not. If there wouldn’t be any log items, multiple Indicium’s or even the same Indicium could potentially run system flows parallel even though that is not allowed. This could lead to major problems so we do require at least 1 record to exist.

Does this suffice Arno?


Mark Jongeling
Administrator
Forum|alt.badge.img+23
Updated idea statusNewNeeds feedback

ArnoW
Apprentice
  • Author
  • Apprentice
  • 7 replies
  • January 3, 2022

Fixed by a recently created hotfix. 


Mark Jongeling
Administrator
Forum|alt.badge.img+23
Updated idea statusNeeds feedbackClosed

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings