nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

File Age Monitor Issue - odd sawtooth pattern...

mstolle

I have a few file age monitors all of which demonstrate the same odd behavior. This is making my alerts less than accurate. Anyone seen anything like this?

NPM 9.5.0 SP4

APM 3.1

Find more posts tagged with

Accepted answers

mstolle

This did the trick. With the new DLL in place, the sawtooth does not repeat. Looks like a winner.

All comments

jiri.tomek

Hello mstolle,
what files do you monitor? Your chart is really strange but file age can be modified so maybe that files you are monitoring are used by some software that does strange things with file's date.

If you are sure that file modification time doesn't change this way, please open a support ticket for this issue.

mstolle

Jiri,

They are text files. They are created on a separate system at the end of a particular daily processing job, and are only created if the processing job was successful. This job only runs once a day each week day. Once the job successfully completes, they are FTPd to the server where I am monitoring their age. So effectively they are files that are simply overwritten once a day and are not accessed dynamically.

I'll open a ticket and see where that takes me.

Thanks for your help.

polymishelp

We are seeing the same issue here. I've tested on different servers with different files and they all jump by 24 hours between 6PM-Midnight every day. However, if I test it against the server running Orion it does not exhibit those symptoms.

I opened a ticket several days ago but do not have a resolution yet.

mstolle

Case # 148751 Opened 17-Mar.

julrich

I am experiencing the same EXACT problem with the file age monitor. Between 6pm and midnight all my file age monitors across multiple servers, jumps up 24 hours, and comes back down after midnight.

I have SW case 148522 opened, and the technician just told me that this has been identified as a system wide issue and is being looked at by the developers now.

I am eagerly waiting for a patch:)

For anyone who is using this component as a check to make sure a file is being constantly updated, i do have a suggestion to stop the false alarms.

I am alarming if a file hasn't been updated within an hour, so I just put in the alerting rule to not alert if the file age goes over 24 hours. Before doing this, I would get a false alarm every day at 6pm