A friend of my parents started a software company in the eighties. I started there to learn and write programs in Mumps even before my university studies in Informatics.
The computers were big in size and small in power or memory compared to today. But we could make applications on a single server for 16 concurrent users with a total of 256Kb memory and a disk of 30Mb. (Digital PDP-11 with DSM-11)
Since then, I always stayed in the same technology, going from Mumps (DSM, MSM, DTM) to Caché and finally Iris.
I worked for private software companies, joined InterSystems as Sales engineer, and finally started my own company, writing programs in various industries like industrial production sites, e-commerce platforms and hospitals.
Needless to say I got a ton of experience in more than 30 years, both in technology as working with people all over the world, still enjoying myself and never regret the day i started my first mumps program.
Any idea how to hide these health check logs in the audit events, so only 'real' login failure attempts are shown ?
You can also use the open exchange solution from Lorenzo Scalese :
https://openexchange.intersystems.com/package/IO-Redirect
If the routine ^%ETRSDK was located in the default % namespace, your errortrap routine was probably erased in a Caché Upgrade (only %Z routines will remain there after an upgrade)
You can use
Try {
//your code
} catch err {
//handle the error
}
See https://docs.intersystems.com/iris20251/csp/docbook/DocBook.UI.Page.cls?...
Friendly Regards,
Danny