Hello,

I am currently having the experience activating prometheus for iris db.

This environment that I speak uses IKO as a base.

I need to put 3 notes in the iris service area.

Are they:

annotations:
   prometheus.io/path: "/monitor/metrics"
   prometheus.io/port: "52772"
   prometheus.io/scrape: "true"

I'm not finding this possibility in the IKO documentation.

Has anyone had this experience and can help us with this challenge?

 Below is the current configuration we made, however, it did not create the annotations we need

This is a self contained class that can be run from the Intersystems Task Scheduler which records peak usage details for databases and licenses built up throughout the day and retaining 30 days history.

To schedule the task to run every hour:  

d ##class(Metrics.Task).Schedule()

You can also specify your own start time, stop time, and run interval:

d ##class(Metrics.Task).Schedule(startTime, stopTime, intervalMins)

Metrics are stored in ^Metrics in the namespace that the class resides in/is run from.

I'm trying to develop monitoring API for the following requirements:

InterSystems Data Platforms and performance - Part 5 Monitoring with SNMP

Hey Developers,

We're pleased to invite you to join the next InterSystems IRIS 2020.1 Tech Talk: DevOps on June 2nd  at 10:00 AM EDT! 

In this InterSystems IRIS 2020.1 Tech Talk, we focus on DevOps. We'll talk about InterSystems System Alerting and Monitoring, which offers unified cluster monitoring in a single pane for all your InterSystems IRIS instances. It is built on Prometheus and Grafana, two of the most respected open source offerings available.

Hi:

Currently we are using an older Healthshare instance but I am not opposed to using IRIS as we will upgrade eventually. 

Currently for monitoring productions we have a Montior screen. We have both the Queues page and a Deepsee dashboard which has current status of our services. The issue with the Deepsee method we currently have with traffic lights is 1) the page is a bit slow to load the metrics 2) any new services from the team  a new widget needs created and although this is easy enough to do it just is time consuming. 

Hi Community,

We're pleased to invite you to the upcoming webinar in Spanish called "SAM: Monitoring InterSystems IRIS with Grafana and Prometheus".

Date & Time: June 15, 4:00 PM CEST

Speaker: @Pierre-Yves Duquesnoy, Sales Engineer, InterSystems Iberia

Hello IRIS Community,

Do you have cases using datadog to monitor intersystems products?

InterSystems is pleased to announce the release System Alerting & Monitoring (SAM) version 1.1.

What is SAM?

SAM marries IRIS’s standards-based Monitoring API and Log Monitor with familiar industry standard tools like Grafana and Prometheus to create a basic monitoring and alerting solution for IRIS clusters.

For more on SAM, see the System Alerting and Monitoring Guide.

What’s new in SAM 1.1?

From time to time, we get the previous question in support, something or someone is using more licenses than expected, and we need to find what. 

We have two scenarios. The first scenario is when we realize that the licenses are exhausted when the application does not work or when we try to connect through the terminal and get the "lovely"

<LICENSE LIMIT EXCEEDED> message: 

Since Caché 2017 the SQL engine has included new set of statistics. These record the number of times a query is executed and the time it takes to run.

This is a gold mine for anyone monitoring and trying to optimize the performance of an application that includes many SQL statements but it isn’t as easy to access the data as some people want.

This article and the associated sample code explains how to use this information and how to routinely extract a summary of daily statistics and keep a historic record of the SQL performance of your application.

What is recorded?

The current version of SAM creates Prometheus metric endpoints which appear to be handled correctly by the current prometheus scraper, however the metrics do not confirm to the current prometheus standard.  The standard states: 

• Prometheus' text-based format is line oriented. Lines are separated by a line feed character (\n). The last line must end with a line feed character. Empty lines are ignored.

Link is here: Prometheus format

In the current output on the

<hostname>:8080/api/monitor/metrics

The MONITOR process (also called the Caché Monitor) scans the messages in your cconsole.log file and sends you emails based on the severity of those messages.  The MONITOR is configured using the ^MONMGR utility in terminal.

The MONITOR should not be confused with the similarly named System Monitor, which checks a variety of system health and performance metrics and can log messages regarding them to the cconsole.log, where they can then be scanned by the MONITOR.

Hi everyone,

Im trying configure the Caché Monitor Manager (^MONMGR) utility for send alert e-mails.
Following the steps I have doubs to configure the options in "Set Server" to send e-mails for hotmail or outlook (smtp-mail.outlook.com).
I dont know how can I configure Mail server SSLConfiguration for hotmail or outlook.
Could you give me help?
Thank you!

Mail server? mail.outlook.com (Enter '-' to reset) =>
Mail server port? 587 =>
Mail server SSLConfiguration?
Mail server UseSTARTTLS? 0 =>

We are running HealthShare on Linux Redhat via Azure.

A couple of days ago, the Azure server rebooted. Which we were unaware of. 

Resulting in the Instance being in a downed status.

In the short term I put together a quick script to check the status, if it is down to restart it.

However, before I go down that road, I thought it would be best to inquire if there is a much better and more streamlined solution?

In a nutshell I just want to check and see if the Instance is up or in a state such as  down or hung then start it.

Is there any recommended KPI's we should be using to monitor our IRIS configurations in Azure?

Hi, everyone!

I want to share a personal project that started with a simple request at work: 

Is it's possible to know how many Caché licenses we are using? 

Reading other articles here in the community, I found this excellent article by  David Loveluck 

APM - Using the Caché History Monitor
https://community.intersystems.com/post/apm-using-cach%C3%A9-history-monitor

So, using David's article, I started using Caché History Monitor and to show all that information. 

When facing the question: Which cool tech should I use? 

I installed a community version of Intersystems IRIS in a Large AWS EC2 instance to do some testing.  I installed SAM and when I try to "Add a new cluster" I receive the following:  "ERROR #5005: Cannot open file '/config/prometheus/isc_tmp_yml_file.yml'"
Screen shot included here: https://share.getcloudapp.com/RBu4K5yv

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.

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

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 articleI'm running net-snmp on Red Hat Enterprise Linux Server release 7.3 (with CentOS repositories), and Caché version 2017.1It looks like snmpd is running as AgentX master, and Caché subagent is running too/opt/cache/mgr/SNMP.log with debug shows no errors and it looks like cache

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" . 

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. The tool consists of the following components:

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