Hello everybody,

after updating from 2018.2.1 to 2021.1 we observe a change in the behaviour of the Messagebank Enterprise Monitor.

In 2018.2.1, when clicking on a specific line inside the configured systems the system dashboard opened, giving insights about queue counts and error conditions.

In 2021.1. when doing the same thing, the login screen of the designated server instance shows up, but does not allow to login (any try, even with valid %All credentials results in a reload of the page). I even created a new user, remebering the password hash issue mentioned in https://docs.intersystems.

SAM - Hacks and Tips for set up and adding metrics from non-IRIS targets

SAM (System Altering and Monitoring) comes with as a 'batteries included' docker-compose container set that is ready to start monitoring IRIS instances with a default dashboard as soon as it starts up. The initial configuration is good to understand SAM functionality and start basic monitoring of your IRIS systems. However, out of the box, there are some setting s that you will need to change when you start to monitor many systems and collect a lot of metric data.

InterSystems Global Summit (or Virtual Summit this year) is traditionally a time of big announcements, and I'm sure our friends from InterSystems have quite a lot of new and exciting things to share with us this year. Here at Banksia Global, we have a big announcement for you as well. Please meet our new website built to make IRIS-based software distribution a breeze: ZpmHub.com!

UPDATE:
It turns out it was just me being a dummy, and the snmpd was correctly telling me there is no value associated with that exact key. I should have used snmpwalk instead of snmpget to display the whole tree.
Original Post follows:
Hello!
I'm trying to set up SNMP monitoring on Caché, using documentation and this article
I'm running net-snmp on Red Hat Enterprise Linux Server release 7.3 (with CentOS repositories), and Caché version 2017.1
It looks like snmpd is running as AgentX master, and Caché subagent is running too
/opt/cache/mgr/SNMP.

I believe most of you have encounted this problem: a healthconnect/ensemble user get a slow response and ask measurement on how long it takes ensmeble to process this request, the ensemble 'activity data' gives no clue of the delay.

The reason is HealthConnect message measurement was based on ensemble message, which can’t give a correct answer on when ensmeble recevie the request and what time it send back response. when there is delay on inbound/outbound adpter, or csp gateway, there is no way to find out the delay from "activity data" . 

I am asked by a customer how to deal with this problem.

When you have been using cubes for business intelligence in a namespace for some time, you may find that there are many cubes in the namespace, only some of which are actively being used. However, it can be difficult to tell which cubes users are or are not querying, and maintaining unused cubes can be costly both in terms of storage and of computation to keep them up to date. This article provides some suggestions and examples for monitoring which cubes are in active use, and for removing cubes that you determine are no longer necessary.

Hey Developers,

Please welcome the new video on InterSystems Developers YouTube:

⏯ System Alerting & Monitoring

Hi Community,

System Alerting and Monitoring (SAM) in InterSystems IRIS data platform helps you efficiently monitor and manage your systems. This video shows some solutions it offers for specific challenges faced by developers and operators:

⏯ The Value of System Alerting & Monitoring (SAM)

InterSystems IRIS Business Intelligence provides the Cube Registry as an interface for managing and scheduling build and synchronize tasks for your cubes. The Cube Event Monitor is a new tool on Open Exchange to help you keep track of those events' status and performance, the number of records being updated, and any build errors (errors when processing individual records) that have occurred.

Hi Community,

See how to use System Alerting & Monitoring (SAM) to view and customize metrics for a cluster of systems running InterSystems IRIS:

⏯ Viewing & Customizing Metrics with SAM

What is the best way to get the size and other storage details of individual Globals in a namespace? 

Thanks,

Mary

Prometheus is one of the monitoring systems adapted for collecting time series data.

Its installation and initial configuration are relatively easy. The system has a built-in graphic subsystem called PromDashfor visualizing data, but developers recommend using a free third-party product called Grafana. Prometheus can monitor a lot of things (hardware, containers, various DBMS's), but in this article, I would like to take a look at the monitoring of a Caché instance (to be exact, it will be an Ensemble instance, but the metrics will be from Caché). If you are interested – read along.

Hello Developers!

Previously, I shared with you all a handy operational analytics dashboard you can build to visualize key message processing metrics, such as number of inbound/outbound messages, average processing times, etc.

This time around, I’d like to walk you through an enhanced log monitor using a workflow many of you are already familiar with – working with alerts as messages inside a production, creating routing rules to filter and route alerts, and using pre-built components like the email adapter to send notifications at a granular level.

Whenever the Windows SNMP Service restarts, the snmpdbg log says the following. 

16:58:25 :Debug tracing enabled for SNMP agent
16:58:25 :SnmpExtensionInit called, pid=4432, tid=12276
16:58:25 :CreateEvent for CacheSNMPTrap suceeded
16:58:25 :register Cache OID 1.3.6.1.4.1.16563.1
16:58:25 :Get all Cache configs ... 16:58:25 :found 1 configs
16:58:25 :Add ENSEMBLE config to list ... 
16:58:25 :RegOpenKey for SOFTWARE\InterSystems\Cache\Configurations\ENSEMBLE\Properties

Whenever the Windows SNMP Service restarts, the snmpdbg log says the following. 

13:08:59 :Attempting initial TCP connection(s) with 1 Cache instances ...
13:08:59 :Get connection with ENSEMBLE on port 1972
13:08:59 :Connection refused on port 1972, check if Cache instance ENSEMBLE is started.
13:08:59 :Cache iscsnmp.dll initialized for 1 configs

Ensemble and all productions are running. I've set up Caché SNMP agent on many other servers in our company and those are working fine. However this one server won't budge. 

Does anyone have any idea what the problem may be here? 

Regards,

Glenn

Hi, Community!

You know that your productions need to be monitored. But what should you be monitoring, and how?

Let me invite you to join Michael Brady, Technical Trainer with InterSystems Learning Services, to learn about message volume monitoring tools, what really happens when you purge a message and how you can monitor your disk space from afar.

This webinar is valuable for anyone managing Ensemble or HealthShare productions.

It will take place on Thursday, May 4, 2017 10:30 am Eastern Daylight Time (New York, GMT-04:00) 

Hi, 

I created a task from Management portal  Task manager to use the Ens.Util.Tasks.Purge task . Task set up includes email notification setup for Completion email and error email.

This task is giving an error  and no email is generated: 

I tested all other task types available from Ens.Util.task but all are giving the same error.

Not sure if this Is this a bug or some missing configuration in the task setup ? Anyone noticed any similar issue or any idea how to fix this ? 

Thank you for your help.

Regards,

Mary

Hi,

As part of our continuous efforts to expand and improve the InterSystems IRIS Data Platform, we’ve set up a brief survey around SQL monitoring. Your feedback will help us in designing and developing the right tools for the job and improve the platform’s overall ease-of-use. Please use the link below to access the survey, which should only take around 5 minutes to complete.

Hello,

I just watched the recording of Michael Brady's presentation on Ensemble Disk Free Space Monitoring. Is the sample code for the Task definition class still available? How can I obtain a copy?

Thanks

Hi Developers!

As you know the application errors live in ^ERRORS global. They appear there if you call:

d e.Log() 

in a Catch section of Try-Catch.

With @Robert Cemper's approach, you can now use SQL to examine it.

Inspired by Robert's module I introduced a simple IRIS Analytics module which shows these errors in a dashboard:

Hey Developers,

Check out the latest video on FHIR API Management:

⏯ FHIR API Management: Basic Configuration

⏯ FHIR API Management: FHIR Dev Portal

⏯ FHIR API Management: Logging and Monitoring

⏯ FHIR API Management: Security

GA releases are now available for the first version (v1.0) of InterSystems System Alerting and Monitoring (InterSystems SAM for short)
  
InterSystems SAM v1.0 provides a modern monitoring solution for InterSystems IRIS based products. It allows high-level views of clusters and single-node drilled down metrics-visualization together with alerts notifications.  This first version provides visualization for more than one hundred InterSystems IRIS kernel metrics, and users can extend the default-supplied Grafana template to their liking.
 
V1.0 is meant to be a simple and intuitive baseline.

Hi All,

With this article, I would like to show you how easily and dynamically System Alerting and Monitoring (or SAM for short) can be configured. The use case could be that of a fast and agile CI/CD provisioning pipeline where you want to run your unit-tests but also stress-tests and you would want to quickly be able to see if those tests are successful or how they are stressing the systems and your application (the InterSystems IRIS backend SAM API is extendable for your APM implementation). 

Hi, 

During the implementation of iris-history-monitor using ZPM, I'm bumping on the following scenario:

My Installer.cls has a call for the Custom Sensors Class method.  The Custom information looks like a charm as I described in this article: 

IRIS History Monitor using custom built-in REST API /api/monitor/metrics

But, now I'm trying to replicate the same behavior using the module.xml to work with ZPM.

<?xml version="1.0" encoding="UTF-8"?>
<Export generator="Cache" version="25">
  <Document name="iris-history-monitor.

Preview releases are now available for the first version (v1.0) of InterSystems System Alerting and Monitoring (InterSystems SAM for short).
  
InterSystems SAM v1.0 provides a modern monitoring solution for InterSystems IRIS-based products. It allows high-level views of clusters and single-node drilled down metrics-visualization together with alerts notifications.  This first version provides visualization for more than one hundred InterSystems IRIS kernel metrics, and users can extend the default-supplied Grafana template to their liking.
 
V1.0 is meant to be a simple and intuitive baseline. Please help us make it great by trying it and sending us feedback!

SAM can display information from InterSystems-based instance starting with version 2019.4
 
SAM is only available in container format. You will need the SAM Manager container plus a small set of additional open-source components (Prometheus and Grafana) that are added automatically by the composition file.

SAM components and the SAM Manager Community Edition are available from

• The WRC Preview page: as “SAM Components” and “SAM Manager” 
• Externally at the SAM components Github repo & the SAM Manager on Docker Hub if you want to download it before the docker-compose runs (this last link might not be available for few hours but the container is pullable)

If you are traveling or prefer a voice-based  Q&A description on what SAM is, here is a podcast we have prepared for you: 

Note (October 2022): yape has been deprecated and replaced by YASPE, there is no more development on yape.

Note (June 2019): A lot has changed, for the latest details go here

Note (Sept 2018): There have been big changes since this post first appeared, I suggest using the Docker Container version, the project and details for running as a container are still in the same place  published on GitHub so you can download, run - and modify if you need to.

One of the topics that comes up often when managing Ensemble productions is disk space:

The database (the CACHE.DAT file) grows in a rate that was unexpected; or the Journal files build up at a fast pace; or the database grows continuously though the system has a scheduled purge of the Ensemble runtime data.

It would have been better if these kind of phenomena would have been observed and accounted for yet at the development and testing stage rather than on a live system.

For this purpose I created a basic framework that could aid in this task.

Hi everyone,

The project IRIS History Monitor received an update, using ZPM and the built-in REST API /api/monitor/metrics.

Hi all.

A long time ago I enabled Activity Monitoring to be able to save myself headaches in the future when looking at the performance of various message routes through our productions.  It's served it's purpose of answering questions on how many messages we process a week etc but I had not had the chance to really dig down into the stats for specific message types or destinations to pin point issues.

That time has come, as I have an outbound that periodically queues up without much rhyme or reason.

Hi Community!

The new video from Global Summit 2019 is already on InterSystems Developers YouTube:

⏯ System Alerting and Monitoring Made Easy