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 ?

Hey Developers,

Watch as the presenter uses IKO to deploy the WebGateway, SAM, and InterSystems API Manager with the latest version of the InterSystems Kubernetes Operator: 

⏯ IKO: The InterSystems Kubernetes Operator (Version 3.0)

SAM only makes Management Portal connections to http.

Has anyone figured out how to get to the SMP through SAM when the instance server is setup for https:

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

Using Prometheus to monitor Caché ，when config application /metrics done， Prometheus connection error: “server returned HTTP status 404 Not Found”

I could not find this file

cat /etc/docker/daemon.json  

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.

I want to try SAM in AWS. I followed these steps:

docker pull store/intersystems/sam:1.0.0.115

git clone intersystems-community/sam: System Alerting and Monitoring (SAM) (github.com)

git clone https://github.com/intersystems-community/sam

tar zpxvf sam-<version>.tar.gz

tar zpxvf sam-1.0.0.115-unix.tar.gz

$ cd sam-<version>

cd /home/ec2-user/git/sam/sam-1.0.0.115-unix/

$ ./start.sh

In your browser, visit:
http://<ip-address-of-host-where-SAM-runs>:8080/api/sam/app/index.csp
You'll be prompted to login.You can use standard InterSystems IRIS credentials like _SYSTEM/SYS.

cAdvisor (short for container Advisor) analyzes and exposes resource usage and performance data from running containers. cAdvisor exposes Prometheus metrics out of the box. 

https://prometheus.io/docs/guides/cadvisor/

Prometheus is integrated in SAM. This makes it possible to leverage the cAdvisor metrics and expose them via Prometheus and Grafana.

Since cAdvisor listens on port 8080, which conflicts with the Nginx port, you can choose to change the Nginx port to accommodate that.

Configuration Steps:

1. Change nginx port.

modify nghix.conf:

    server {
        listen 9991; 

This allows you to access

InterSystems SAM is a great tool to monitor your InterSystems IRIS and InterSystems IRIS For Health clusters on prem or in a cloud environment. This article describes how you can implement a customized alert handler. This is currently an undocumented and most likely an unknown feature of InterSystems SAM. With future releases it will be probably made easier to leverage this useful concept.

In the interest of shortness, I will only mention InterSystems IRIS in this article, but the following applies to InterSystems IRIS and InterSystems IRIS For Health. 

InterSystems SAM is a cluster of five

Hi Community,

Enjoy watching the new session recording from InterSystems Virtual Summit 2020:

⏯ Performance Testing with InterSystems Tools

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)

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

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

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: