New post

#System Alerting and Monitoring (SAM)

3

InterSystems System Alerting and Monitoring (SAM) is a cluster monitoring solution for InterSystems IRIS data platform version 2020.1 and later. Whether your application runs on a local mirrored pair or in the cloud with multiple application and data servers, you can use SAM to monitor your application.

Additional resources:
•‎ Documentation
•‎ GitHub repo
•‎ Easy start: Viewing & Customizing Metrics with SAM

Question
· Dec 4, 2023
Custom Application Metric

I made a custom application metric, imported it to the USER namespace and used:

set status = ##class(SYS.Monitor.SAM.Config).Add.ApplicationClass("historymonitor.errorSensor", "USER")

to add it. When I do 'w status' it returns 1 so it is added but I still can't see the custom metric in the api/monitor/metrics endpoint. Even though I added %DB_USER in the application roles for api/monitor.

Does anyone know where the problem might be that the metrics endpoint still doesn't show my metric?

0 1
0 139

Hello, I am quite new with InterSystems, SAM and Grafana. I am looking a way to get Log Files and Application Errors from InterSystems to SAM like in this post: https://community.intersystems.com/post/grafana-support-intersystems-iris. Is this plugin still under development or is there any other way to get those errors? By using SAM, I do not get those errors.

0 2
0 302

My employer set up a web-based HL7 interface monitor dashboard that will display all Ensemble components (Service/Process/Operation) in a Production, their status, and the support information embedded in each interfaces listing on the Monitor. Please see 3 screenshots.

This is part of the URL that we go to when accessing this Web based Monitor: ......57772/csp/healthshare/monitor/Rush.Monitor.Web.Home.cls

0 3
0 190
Question
· May 25, 2023
SAM not starting

i tried to install SAM 2.0.1. on a redhat 8 server.

i use docker for managing the containers.

I have followed the documentation for the installation and deployment of SAM step by step

when trying to start the SAM with the script i have an container that can't be created and the prompt not responding

must kill the process to stop .

Does anyone have an idea?

0 2
0 182
Question
· Aug 25, 2022
SAM - Adding node_exporter

Note sure if anyone would know this.... But I presented my team with a Proof of Concept of running SAM to monitor our IRIS Development and Test Clusters. In talking with them we would like additional OS metrics that aren't provided by what is built into SAM. Looking at more OS detail I found node_exporter from Promethus. I added node_exporter to our server that we want to monitor, but then tried to config isc_prometheus.yml to use node_exporter. That did not go well and when I restarted SAM, it would not download the built in metrics to SAM.

0 3
0 162
Question
· Aug 19, 2022
SAM - Custom Application Metrics

Now that I have SAM up and running, out of the box I would like to add some Application Metrics. Does anyone have templates, or have suggested classes that someone could use to add custom metrics to SAM? Maybe we should start a repository somewhere? Or would someone be willing to share custom metrics on the Open Exchange?

What I am looking to do is capture the overall HL7 message and header count per day.

0 3
0 304

I am trying to investigate whether the SAM component will give us metrics that we are looking for when it comes to # of messages, etc... I have IRIS 2022.1 running on Red Hat 8, but noticed that SAM was bundled as a docker-compose image. REL 8 doesn't install docker off the bat, but has podman which reading podman 3 versions and later, I should be able to call docker-compose.yml images. After installing Apache and making some modifications to docker-compose.yml, I tried executing the start.sh script after verifying podman was running and podman-compose was installed.

0 5
0 432

Monitoring IRIS through SAM (sam:1.0.0.115)

While I've used to make it work in the past, I'm not able any more to fix the already faced issue : "State: Unreachable"

Despite all the ip-addresses attempts (or hostname = host.docker.internal) and while "/api/monitor/metrics" is running well...

Could someone provide good practices to make it work cleanly ?

1 13
0 425