Monitoring is a process of controlling and management of performance and availability of software applications.
Modern platforms usually treat observability as three core signals:
OpenTelemetry (OTel) is the standard way to produce and ship all three signals.
How many times have we migrated an IRIS Instance to another machine, maybe even another version, and after a few days realized we forgot that one SSL Configuration critical for a Business Operations to work? Or maybe a credential, or a lonely class in a package by itself?
The simple solution is to make a checklist¹. A checklist of the entities we have to move. But simple checklists on Word documents are often forgotten, or just ignored.
There are nfs disk commands (including nfsiostat) included with SystemPerformance, but disabled by default. Enable them by running:
$$Enablenfs^SystemPerformance()
Doing so will add the following nfs commands, for example, on Linux:
/usr/sbin/nfsstat -cn/usr/sbin/nfsiostat [interval] [count]Ensure the commands are installed and runnable from the OS :)
This can be subsequently disabled via $$Disablenfs^SystemPerformance()
Adding an arbitrary OS tool creates a "user" command under ^IRIS.
Hello everyone, thanks for reading this question.
I am currently working with Ens.Alerting.ManagedAlert in an interoperability production and I am using the alert suppression mechanism to avoid generating duplicate alerts within a defined time window (for example, 30 minutes).
The configuration works correctly in terms of preventing duplicate alerts from being generated, but I have a question regarding observability.
When an alert is suppressed during the configured time window, I can see log messages such as:
"Managed alert not created for AlertRequest with ID 'XXXX' due to rule 'Rules.