Cycling SMAT

[Jared Parish]

Regarding SMAT / SMAT DB cycling.  As of CIS 20.1, am I under the understanding that cycling smat db files are still script based?

However, from documentation and forum posts, it appears that SMAT DB history management is built in functionality.

If cycling is still script based, what ways are people accomplishing that in 2021?  hcischeduler? cron? Alerts? Something else?

Thank you community.

- Jared Parish

Topic

[Paul Stein]

Jared – it is built in to the GUI under Site Preferences on the SMAT tab.

Select checkmark to enable smat history and configure options accordingly

[Paul Stein]

Forgot to mention – threshold is set under process menu

[Jared Parish]

Hi Paul!

I wonder what the consensus is doing: threshold or time based?  Seems like, functionality wise, CIS wants us to use size based cycling.

- Jared Parish

[Gene Millard]

We use alerts to cycle most of our sites daily.

We have one site that is automatically cycled by the size of the smat file because they would get very large.

The Guthrie Clinic
Sayre, PA

[Robert Kersemakers]

At the moment we are use SMAT files on CL6.2 where SMAT is cycled daily/weekly so we can retain a certain number of days/weeks of SMAT. We normally search for a certain message in SMAT via command line (grep) to determine which (unencrypted) SMAT we need and then use GUI to get to the message.

We are migrating to CL19.1 with SMATDB and will still be doing daily/weekly SMAT cycling. Although when searching a message we will need to use SMATDB GUI and will need to search through all SMAT for a message. Not sure how quick this will be.

I can see that if searching is quick, there is no need to know how long you are retaining SMAT and you could cycle save on size. For now we will continue to cycle save on time.

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[MiteshBhatt]

We have SMATDB Files growing. We dont have SMAT files.

the Option in the GUI in v6.2.3 in site preference (SMAT) has “Enable SMAT History” and sent Max. SMAT files to 10, with size of 0.1 Gig and Age as 7 days.

Still our SMATDB files have data from Dec 2020 (today is 9.28.21) and are 30Gig each and growing.

Are we doing something wrong? Do we need cron/script on top of this above setting?

If cron/script is needed then whats the purpose of the above CLE inbuilt setting ?

 

Can someone help!

[Rob Abbott]

Hi Mitesh, I suggest you contact support and they can have a look at this.

 

As an FYI in 19.1 and below the trigger for cycling is size-based.  In 20.1 we added the ability to cycle on a schedule.

 

Rob Abbott
Cloverleaf Emeritus

[MiteshBhatt]

I created a another thread- here’s the link for the same.

Thank you for replying!

Cloverleaf SMATDB files growing (v6.2.3.x)

[Author]

Replies