You are viewing limited content. For full access, please sign in.

Question

Question

LFDS Audit - Are there any guides on what the details mean?

asked on September 17, 2019

Good morning,

 

I recently came across LFDS Audit tool and decided to run it - but unfortunately I lack the knowledge to understand how it works.

 

For example the audit gave me details about our colleagues in the southern hemisphere but did not give any details about our colleagues in the northern hemisphere. Now this was confusing to me as my colleagues in the northern hemisphere use Laserfiche everyday, but the ones in the southern hemisphere do not, yet LFDS Audit was giving me all the details of my colleagues in the southern hemisphere.

 

Can anyone clarify why this is? I'm referring to the Event Data column below (I redacted the details as I wasn't sure if it provides sensitive information).

0 0

Answer

SELECTED ANSWER
replied on September 18, 2019 Show version history

LFDS auditing is about what changes have occurred within LFDS, both by administrators and by system processes.

This includes:

  • Manually adding or editing a user
  • AD Group Sync adding or editing users
  • Deleting a group
  • Renewing the master license
  • Adding access rights for the database

 

Most actions that a user can perform within LFDS are audited. Regular Laserfiche use outside of LFDS is not going to show up here --- access a document, submitting a form, creating a metadata template, etc. are not part of LFDS and thus are not audited here.

 

Looking at your event type column, these events are about creating and editing users within LFDS. As such, it doesn't mean that those specific people are active; instead, it means someone is administering those users --- probably setting them up so the users can be onboarded soon.

In the next release of LFDS, our audit reports will also optionally show login events, and we will have the ability to toggle off specific events so that you are only monitoring the events you want to track.

1 0
replied on September 19, 2019

Thanks Brianna! That has helped clarify it a lot more. You don't have a guide lying around somewhere do you when I come round to looking at this again in 3 months time? winklaugh

0 0
replied on September 19, 2019 Show version history

Unfortunately, we don't have a good resource to provide at this time, but it's definitely on our to-do list smiley

2 0

Replies

replied on October 15, 2019

Hi Brianna,

I have just stumbled on the LFDS Audit also (never seen mentioned in any CCP training) and it appears to be a great tool for troubleshooting LFDS sync issues.

 

It keeps separate logs in Programdata folder which can be trimmed to a certain date range like last 30 or 90 days to manage the space the logs use.

 

I also tested the log filtering which looks to work for Event and Administrator classes but did not have any effect for Date as all records were always displayed irrespective of any date option used eg. Today or Custom Range.

Is LF aware of this a bug in 10.3.1 and has it been corrected in latest LFDS release?

 

many thanks

Warren Cook

1 0
replied on October 21, 2019 Show version history

I'm glad to hear you are finding the audit feature useful for AD sync troubleshooting!

Filtering by date works for me on 10.3.1.45 (and 10.4, for that matter), so I recommend opening a support case if this issue is persistent or occurs frequently.

Do you see this issue with all of the Date filter options, or only one? (E.g., only when using the custom date range)

Edit: We do have a bug with an upcoming fix related specifically to date formats aside from US. The fix should improve date localization handling in general, so it could be related to what you are seeing.

0 0
replied on October 21, 2019

Hi Brianna,

With AU date format (dd/mm/yyyy) we can often see date issues that US do not.

All Date filter selections including Custom listed all events. eg selecting 'Yesterday' would list all events (my LFDS logs had accumulated to several weeks) 

It sounds like the localization handling fix should correct the date filter operation when available.

 

many thanks 

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.