Change percona to shatteredsilicon#1
Conversation
|
This looks concerning: Regarding the service and spec file, does node_exporter have a separate rpm and service script in pmm-server? I just checked in a deployed PMM 1.17.5 server and there is no node_exporter rpm, there is only pmm-client rpm. I can see that there is /usr/lib/systemd/system/node_exporter.service, but this is part of the pmm-server package. |
You are right, node_exporter doesn't have a separate rpm, it's part of ssm-client package, and the service script is part of ssm-server package. I just bindly retrieved them from ssm-server-packaging repo, didn't realize they are not being used in this repo. I just removed them. |
Other changes: - Update Gopkg files - Specify promu package to v0.1.0
|
What do we need this for? It looks Windows specific? Gopkg.lock: |
|
What is this needed for? [[projects]] |
|
Similarly these don't seem to be in the original: [[projects]] [[projects]] [[projects]] [[projects]] [[projects]] [[projects]] [[projects]] [[projects]] [[projects]] Were they auto-pulled by dependencies? |
Yep, all of these are auto-pulled by dependencies. I might did a dependency update, and it causes a lot of changes in denpendency tree. |
* Make FS space alerts thresholds configurable (#1) This makes it possible to tweak the thresholds for the NodeFilesystemSpaceFillingUp alerts. Which might be necessary in systems like Kubernetes, where the image garbage collector runs at 85%, so it's not a problem that the disk reaches that usage %. Signed-off-by: iuri aranda <iuri@skyscrapers.eu>
* Make FS space alerts thresholds configurable (#1) This makes it possible to tweak the thresholds for the NodeFilesystemSpaceFillingUp alerts. Which might be necessary in systems like Kubernetes, where the image garbage collector runs at 85%, so it's not a problem that the disk reaches that usage %. Signed-off-by: iuri aranda <iuri@skyscrapers.eu>
No description provided.