This group consists of fairly long technical posts regarding InterSystems Technology features and experience.
Every post in this group is a story of a developer or engineer who wants to share his experience related to InterSystems Data Platform with you.
Every post in this group contains either snippets of code or even ready to use projects with sources on Github or with working demos of InterSystems Technology.
Every post is reviewed by InterSystems specialists through a special reviewing procedure.
Subscribe to the group and you'll get weekly posts with essentials of experience on developing, testing, deploying, maintaining solutions that utilize InterSystems Data Platform technology: multimodel DBMS Caché, Platform for connected applications Ensemble, analytics technology DeepSee and unstructured data management technology - iKnow.
Yes, you can contribute to this group. If you want to share your experience, promote interesting development tool or a framework to InterSystems Developer Community in the form of a long article reviewed by InterSystems engineers - please contact me.
This post provides useful links and an overview of best practice configuration for low latency storage IO by creating LVM Physical Extent (PE) stripes for database disks on InterSystems Data Platforms; InterSystems IRIS, Caché, and Ensemble.
InterSystems Data Platform includes utilities and tools for system monitoring and alerting, however System Administrators new to solutions built on the InterSystems Data Platform (a.k.a Caché) need to know where to start and what to configure.
This guide shows the path to a minimum monitoring and alerting solution using references from online documentation and developer community posts to show you how to enable and configure the following;
Caché Monitor: Scans the console log and sends emails alerts.
System Monitor: Monitors system status and resources, generating notifications (alerts and warnings) based on fixed parameters and also tracks overall system health.
Health Monitor: Samples key system and user-defined metrics and compares them to user-configurable parameters and established normal values, generating notifications when samples exceed applicable or learned thresholds.
History Monitor: Maintains a historical database of performance and system usage metrics.
pButtons: Operating system and Caché metrics collection scheduled daily.
Remember this guide is a minimum configuration, the included tools are flexible and extensible so more functionality is available when needed. This guide skips through the documentation to get you up and going. You will need to dive deeper into the documentation to get the most out of the monitoring tools, in the meantime, think of this as a set of cheat sheets to get up and running.
By update
