A fluent plugin that collects metrics and exposes for Prometheus.

A td-agent plugin that collects metrics and exposes for Prometheus.

Fluentd plugins for Google Cloud Logging. An unaffiliated fork of the official library.

This is a collection of useful tools to help you in more easily instrumenting Ruby applications for the Prometheus monitoring system.

This gem is a Logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/logstash-plugin install gemname. This gem is not a stand-alone program. This plugin supports oauth2 token.

This gem is a Logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/logstash-plugin install gemname. This gem is not a stand-alone program. This plugin supports oauth2 token.

This gem is a Logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/logstash-plugin install gemname. This gem is not a stand-alone program. This plugin supports oauth2 token.

Output logstash data to a prometheus exporter

This gem is a Logstash plugin required to be installed on top of the Logstash core pipeline using $LS_HOME/bin/logstash-plugin install gemname. This gem is not a stand-alone program. This plugin supports oauth2 token.

Takes events from anything you like, and reliably sends them to a logstash server (or cluster thereof), using modern service discovery techniques like DNS.

Tool for monitoring application's processess state

APM For Ruby Applications based on Open Source Tools such as Prometheus, Grafana

Peatio gem contains microservices and command line tools

A fluent plugin that collects metrics and exposes for Prometheus.

Gathers metrics from Phobos, making it possible for Prometheus server to consume this

Export Prometheus statistics for a Postfix server

The missed parts of prometheus/client_ruby

Using prometheus-client with non-standard routes (i.e. using non-hexadecimal ids) yields problematic results. This gem solves the problem offering a configurable Collector middleware.

Tracer for accurate duration tracking with Prometheus metrics

Application to gather prometheus style metrics # Usage Install the gem into your gemfile ```gem prometheus-collector``` Install your gemset ```bundle install``` Consume the program. ``` require 'prometheus/collector' class Guage < Prometheus::Collector::Extensions::Base install def run # Do some things that would be collected in Prometheus::Client Objects end end ``` Mount the Prometheus::Collector::Application application, or start it from your app.rb ``` Prometheus::Collector::Application.start ``` # How it works The collector app makes use of the Prometheus client collector and exporter middleware to allow you to write custom applications that export prometheus style metrics. It is designed as a bare-bones scaffold to get you off the ground with a ruby applet to get some statistics. It utilizes rack and its middleware. The interface is fairly straightforward: Your Metric Executing code needs to extend Prometheus::Collector::Extensions::Base for 'repeatedly-runbable' operations and Prometheus::Collector::Extensions::Once for something that should only be executed Once. Your class should implement an instance level `run` function, and may optionally implement a class level `schedule` function: This must return a `cron` style string to tell the application when to invoke your `run` code. By default, `schedule` is set to `* * * * *` which would allow the code to be executed every minute. ### Scheduling Scheduling is implemented via em-cron. Thus the re-scheduling of a task should occur within the parameters of the `schedule` string but is evaluated upon completion. Thus in normal operation, the code should not execute more than one `run` of a given worker definition at a time.