[RELEASE] Scylla Monitoring Stack 4.1.0

[Amnon Heiman]

The ScyllaDB team is pleased to announce the release of ScyllaDB Monitoring Stack 4.1.0

ScyllaDB Monitoring Stack is an open-source stack for monitoring ScyllaDB Enterprise and ScyllaDB Open Source, based on Prometheus and Grafana. ScyllaDB Monitoring Stack 4.1.0 supports:

• ScyllaDB Open Source versions 4.5, 4.6, 5.0 and 5.1

• ScyllaDB Enterprise versions 2020.x, 2021.x and 2022.x

• ScyllaDB Manager 2.3.x, 2.4.x, 2.5.x, 2.6.x, 3.0.x

This release brings new panels and graphs, bug fixes, stability improvements and performance enhancements.

Related Links

• Download ScyllaDB Monitoring Stack 4.1

• ScyllaDB Monitoring Stack Docs

• Upgrade from ScyllaDB Monitoring 3.x to 4.y

Versions updates for Scylla Monitoring Stack 4.1.00

• Set Prometheus version to 2.38.0

• Set Grafana version to 9.1.0

• Update Loki to 2.6.1

New Information in ScyllaDB Dashboards

• Add TTL metrics to Alternator dashboard #1783

Bug Fixes

• No progress on backup and repair gauges #1796

Operational Changes

• Don't configure Grafana loki data source if Loki is disable #1818

[Michael Wohlwend]

Am Sonntag, 4. Dezember 2022, 17:30:03 CET schrieb 'Amnon Heiman' via ScyllaDB
users:

> The ScyllaDB team is pleased to announce the release of ScyllaDB Monitoring
> Stack 4.1.0
>

I tried to start all this up, but it fails with an error (Scylla-version not
found), which it shouldn't.

After adding some logging into the start scripts it shows this:

$ start-all.sh -d /data-dir


Wait for Prometheus container to start.
before start grafana: VERSIONS=5.1
grafana: VERSIONS=
grafana args: -L 172.17.0.3:3100 -E -p 172.17.0.5:9090 -D -m docker run -d -i
-p 9093:9093 -v /home/mwohlwend/scylla-mon4/scylla-monitoring-scylla-
monitoring-4.1.0/prometheus/rule_config.yml:/etc/alertmanager/config.yml:z --
name aalert docker.io/prom/alertmanager:v0.24.0 --log.level=debug --
config.file=/etc/alertmanager/config.yml >& /dev/null 172.17.0.2:9093 -M 3.0 -v
5.1
grafana : option=L
grafana : option=E
grafana : option=p
grafana : option=D
grafana : option=m
grafana : VERSIONS=
>>>> VERSION = , VERSIONS =
Scylla-version was not not found, add the -v command-line with a specific
version (i.e. -v 2021.1)
-----------------------------------
So start-grafana.sh gets the "-v 5.1" argument, but there is a " >& /dev/null
" in here which prevents the script from getting the "-v" argument.

How should this work?

Thanks for helping,
Michael

[Amnon Heiman]

assuming you are using scylla version 2022.1

you can start it with
./start-all.sh -v 2022.1

In a real deployment you should add the prometheus directory with the -d flag:

./start-all.sh -v 2022.1 -d prom-data/

--
You received this message because you are subscribed to the Google Groups "ScyllaDB users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scylladb-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scylladb-users/1837484.tdWV9SEqCh%40pc21a.

[Michael Wohlwend]

Am Donnerstag, 22. Dezember 2022, 12:23:28 CET schrieb 'Amnon Heiman' via
ScyllaDB users:

> assuming you are using scylla version 2022.1
> you can start it with
> ./start-all.sh -v 2022.1

adding the "-v" option gives the same error.

> In a real deployment you should add the prometheus directory with the -d
> flag:
> ./start-all.sh -v 2022.1 -d prom-data/

I did: "start-all.sh -d /data-dir"

As you can see in my mail, the real error is, that there is a " >& /dev/null"
appearing in the argument list to start-grafana.sh which prevents the script
from getting the "-v 5.1" argument.

The shell variable AM_ADDRESS (which is given to start-grafana as argument) is
set to:

AM_ADDRESS= docker run -d -i -p 9093:9093 -v /home/mwohlwend/scylla-
mon4/scylla-monitoring-scylla-monitoring-4.1.0/prometheus/rule_config.yml:/etc/

alertmanager/config.yml:z --name aalert docker.io/prom/
alertmanager:v0.24.0 --log.level=debug --config.file=/etc/alertmanager/
config.yml >& /dev/null
172.17.0.2:9093

I cannot see where this redirect to /dev/null comes from, this is the error.

Any ideas?

[Amnon Heiman]

Can you start with a clean version (before any changes you made to the scripts)

run:

./start-all.sh -v 2022.1

And see if it works?

--
You received this message because you are subscribed to the Google Groups "ScyllaDB users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scylladb-user...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/scylladb-users/8157136.T7Z3S40VBb%40pc21a.

[Michael Wohlwend]

Am Donnerstag, 22. Dezember 2022, 13:19:25 CET schrieb 'Amnon Heiman' via
ScyllaDB users:

> Can you start with a clean version (before any changes you made to the
> scripts)
> run:
> ./start-all.sh -v 2022.1
>
> And see if it works?
>
> On Thu, Dec 22, 2022 at 1:33 PM Michael Wohlwend <mic...@fantasymail.de>

This was where it started, with a clean version. After getting the error I
added the -v, after still getting the error I added only "echo" commands to
the scripts, I didn't changed the code.

Does the startup needs internet?
Since I don't have external network I installed it on a different server and
used "docker save" and "docker load" to transfer the docker images.

But this shouldn't cause this strange ">& /dev/null" problem (I think..)

[Amnon Heiman]

maybe you have an env.sh file locally?

--
You received this message because you are subscribed to the Google Groups "ScyllaDB users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scylladb-user...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/scylladb-users/3709142.kQq0lBPeGt%40pc21a.

[Michael Wohlwend]

Am Donnerstag, 22. Dezember 2022, 14:03:11 CET schrieb 'Amnon Heiman' via
ScyllaDB users:

> maybe you have an env.sh file locally?

no, there is no env.sh