Skyline on ElasticXL

[Bob_Zimmerman]

I have a relatively simple Skyline config for my personal ElasticXL lab (R82 jumbo 122 in a 2x2 cluster):

[Expert@DallasticXL-s01-01:0]# cat /home/admin/payload.json
{
	"enabled": true,
	"export-targets": {
		"rebase": [
			{
				"enabled": true,
				"name": "internal",
				"type": "prometheus-remote-write",
				"url": "http://10.0.3.23:30104/api/v1/write"
			}
		]
	}
}

[Expert@DallasticXL-s01-01:0]# jq -c . /home/admin/payload.json
{"enabled":true,"export-targets":{"rebase":[{"enabled":true,"name":"internal","type":"prometheus-remote-write","url":"http://10.0.3.23:30104/api/v1/write"}]}}

I go to the Skyline Administration Guide's directions for "Step 4 - Configure the OpenTelemetry Collector on the Check Point Server to work with the Prometheus Server" > "Procedure to work with an on-premises Prometheus Server" > "Run the configuration command to apply the payload", and it says to run this for a Scalable Platform Security Group:

g_all sklnctl export --set "$(cat /home/admin/payload.json)"

But when I run it, it definitely doesn't work:

[Expert@DallasticXL-s01-01:0]# g_all sklnctl export --set "$(cat /home/admin/payload.json)"
sklnctl export --set {{
	"enabled": true,
	"export-targets": {
		"rebase": [
			{
				"enabled": true,
				"name": "internal",
				"type": "prometheus-remote-write",
				"url": "http://10.0.3.23:30104/api/v1/write"
			}
		]
	}
}}: command not found

[Expert@DallasticXL-s01-01:0]# g_all sklnctl export --set "$(jq -c . /home/admin/payload.json)"
sklnctl export --set {{"enabled":true,"export-targets":{"rebase":[{"enabled":true,"name":"internal","type":"prometheus-remote-write","url":"http://10.0.3.23:30104/api/v1/write"}]}}}: command not found

It's obviously running the command substitution before running the g_all, so I also tried this to get it to pass the command verbatim to the other members:

[Expert@DallasticXL-s01-01:0]# g_all sklnctl export --set "\$(jq -c . /home/admin/payload.json)"
1_01:
Error: invalid character '{' looking for beginning of object key string
1_02:
Error: invalid character '{' looking for beginning of object key string
2_01:
Error: invalid character '{' looking for beginning of object key string
2_02:
Error: invalid character '{' looking for beginning of object key string

[Expert@DallasticXL-s01-01:0]# g_all sklnctl export --set '$(jq -c . /home/admin/payload.json)'
1_01:
Error: invalid character '{' looking for beginning of object key string
1_02:
Error: invalid character '{' looking for beginning of object key string
2_01:
Error: invalid character '{' looking for beginning of object key string
2_02:
Error: invalid character '{' looking for beginning of object key string

For now, I can just move to each member and run the 'sklnctl export --set "$(cat /home/admin/payload.json)"' command by hand. It's just annoying.

Since the command in the documentation doesn't work, how should this be done using g_all?

[Bob_Zimmerman]

Tried a few things with 'hostname' to learn more about how g_all works.

[Expert@DallasticXL-s01-01:0]# g_all echo "$(hostname)"
1_01:
DallasticXL-s01-01
1_02:
DallasticXL-s01-01
...

[Expert@DallasticXL-s01-01:0]# g_all echo '$(hostname)'
1_01:
{DallasticXL-s01-01
1_02:
{DallasticXL-s01-02
...

[Expert@DallasticXL-s01-01:0]# g_all echo "\$(hostname)"
1_01:
{DallasticXL-s01-01
1_02:
{DallasticXL-s01-02
...

Not sure what's going on with the brace at the beginning of the returned data, but that seems likely to be part of the problem.

[Alex-]

There's definitely something with Skyline on scalable platforms.

Some syntax is not going through as you experienced and rebasing doesn't work as well.

With Maestro and VSX, the workaround of doing it per machine and SG causes data export issues and incomplete views.

We have an SR open.

[Elad_Chomsky]

Hi, 

Please contact me on [email protected] , so I can try to assist and promote it and further to the relevant R&D owners.