For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Jad_Tabbara__JT's avatar
Jad_Tabbara__JT
Icon for Nimbostratus rankNimbostratus
Jul 20, 2017

Changing the default ASM DB log size and the default number of entries

Hello,   Is it possible to change/reduce the default ASM DB log size and the default number of entries.   We are running BIG-IP 12.1.2 and I found on devcentral two answers from F5 saying that...
ASM Advanced WAF
security
Ashwin_Venkat's avatar
Ashwin_Venkat
Icon for Employee rankEmployee
Jul 21, 2017

JT,

 

While it is possible to increase the amount of requests that can be stored in the mysql db (either the number of requests or the size of the db itself), it's not something that we'd recommend as it can cause performance impact (particularly with the GUI in loading all the requests). If you see more requests being logged than the specified limit, then we'd recommend going with using remote storage.

 

Ashwin

 

  • Jad_Tabbara__J1's avatar
    Jad_Tabbara__J1
    Icon for Cirrostratus rankCirrostratus
    Jul 24, 2017

    Hello Ashwin,

     

    Thanks for you answer. Based on links that I shared in my question. other "F5 members" have already clarified the fact that it is not recommended to increase theses values.

     

    But my question was to decrease it. Indeed, my hope is to change these values for example from 2 GB to 1 GB and from 3 million events to 1.5.

     

    Please share the procedure.

     

    Regards

     

  • Jad_Tabbara__J1's avatar
    Jad_Tabbara__J1
    Icon for Cirrostratus rankCirrostratus
    Jul 31, 2017

    Hello Ashwin,

     

    Please could you share how to do it ?

     

    Thanks

     

  • Jerry_Lees's avatar
    Jerry_Lees
    Icon for Employee rankEmployee
    Jul 10, 2018

    I realize this is old, but could you clarify why you would like to decrease the size? Most people end up wanting to increase thee numbers when they ask about database sizes.

     

    I can't think of a reason to make it smaller other than a system is running low on disk space, honestly, that's a completely different problem too. One that an additional 1Gb isn't going to solve long term.

     

  • Jad_Tabbara__J1's avatar
    Jad_Tabbara__J1
    Icon for Cirrostratus rankCirrostratus
    Jul 10, 2018

    Hello Jerry,

     

    We noticed that incident management from the ASM GUI is very slow (RAM cosumption high) as soon as we have a large number of incidents. By decreasing the size from 2 GB to 1 GB or from 3 million entry to 1.5 million, I wanted to have a faster "admin" experience using the ASM GUI.

     

    This was one of the need. Also we didn't wanted to retain to old incidents, since they are also sent to a SIEM, we wanted to keep only 1 year

     

    Regards

     

  • Jerry_Lees's avatar
    Jerry_Lees
    Icon for Employee rankEmployee
    Jul 10, 2018

    Hmmm, that's a tough one to troubleshoot without access to the system or configuration (don't post here). What version and hotfix? Also, did you open a support case? Are there any errors/events in the asm or ltm logs around this time? Is it just Request Event viewing or everything in the GUI (i.e. viewing Virtual Servers)?

     

    If it's related to database size, I'm certain there would be a fix, if it isn't I'm certain you'd want to know, especially if it's still occurring.