Andrey Novikov
Andrey Novikov
@i5okie, currently you can specify port for exporter with `PROMETHEUS_EXPORTER_PORT` environment variable. Specify different ports for different processes: https://github.com/yabeda-rb/yabeda-prometheus/blob/4393803a273ff333c39587fe7225aee3af0c3831/lib/yabeda/prometheus/exporter.rb#L22-L26
@w32-blaster, if your processes are not isolated from each other (not being run in containers, so can share common memory or file system) then you can use either of two...
Yes, in case of yabeda-prometheus it wraps [original `prometheus-client`](https://github.com/prometheus/client_ruby/) which have [open issue about multi-process support](https://github.com/prometheus/client_ruby/issues/9). GitLab forked prometheus-client to [`prometheus-client-mmap`](https://gitlab.com/gitlab-org/prometheus-client-mmap/) which does support multi-process servers via memory mapped files....
@elct9620, try to use yabeda-prometheus 0.1.4 with GitLab's gem: ```ruby # Gemfile gem "prometheus-client-mmap" gem "yabeda-prometheus" ``` Please note that [you need to specify `prometheus_multiproc_dir` env variable for it](https://gitlab.com/gitlab-org/prometheus-client-mmap/blob/c1bddf6aec2e322295e2d5fd429ec42f4da76abe/lib/prometheus/client/configuration.rb#L12) to...
Closing this issue, as official Prometheus Ruby client got pretty good support for metrics aggregation via `DirectFileStore` (there are caveats however). See https://github.com/prometheus/client_ruby#data-stores
Show your `package.json`, probably you have something weird in it, as per error message: ``` Refusing to install package with name "delete-test-01" under a package also called "delete-test-01". Did you...
That seems to be pretty widespread issue in running _some_ AMD64 Docker images on ARM64 Macs. See: - https://gitlab.com/qemu-project/qemu/-/issues/1059 - https://gitlab.com/qemu-project/qemu/-/issues/340 - https://github.com/docker/for-mac/issues/6264 Not sure that I can do anything...
Try to raise `map_expiration_period` setting in your `config/crystalball.yml`: ```yaml --- map_expiration_period: 604800 # 1 week ```
Well, I believe that by default it shouldn't fail if binary wasn't found. It is better to miss something than completely break workflow for some people, IMO. I don't see...
Nothing windows-specific here. I'm also observing this behavior on Linux for 0.7.3 built from Homebrew and installed from Ruby gem. But version 0.6.4 from snap store works as expected. So...