puma-plugin-telemetry_too 0.0.1.alpha1

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: 6c682b1fe20857520c6a607906dd69ddd84b42578b47eb774942aed89245b0eb
+  data.tar.gz: 74e52f5636942939be701e6095dbb81da1b124bc87fee0a8569a0a90f986d1c9
+SHA512:
+  metadata.gz: b60248fbb6767b8b46cc1b0566cb717a77e406febd159df2c85142ebd67f09f8c379ae7cff758a92cafb24a9b3d3b978c58aba4720eee636e02a6802573e5b29
+  data.tar.gz: c3154f1ec4e3c4a6171b02ba8d85bd2b731fcad86ba25bf2dc5967942f83c092abe7ebb94cac86a55362de528ae44f081e3065bcbad923396eb3cc60efee7e88

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,13 @@
+require:
+  - rubocop-performance
+
+AllCops:
+  TargetRubyVersion: 3.2
+  NewCops: enable
+
+Metrics/BlockLength:
+  Exclude:
+    - spec/**/*
+Metrics/ClassLength:
+  Exclude:
+    - spec/**/*

data/.tool-versions

@@ -0,0 +1 @@
+ruby 2.6.10

data/CHANGELOG.md

@@ -0,0 +1,115 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased] TBD
+
+### Changed TBD
+- Forked and renamed Gem to `puma-plugin-telemetry_too`
+
+### Added
+- Introduce new `formatter:` options: `:json` and `:passthrough`
+- Introduce new `transform:` options: `:cloud_watch` and `:passthrough`
+- Introduce new `LogTarget` for logging metrics to any `::Logger` compatible logger
+- Support for Puma 7
+
+## [1.1.4] 2025-05-29
+
+### Changed
+- Updated gems in the Gemfile.lock
+
+### Added
+- Support for 'ubuntu-24.04'
+- Support for Ruby 3.4
+
+### Dropped
+- Support for 'ubuntu-20.04'
+- Support for Ruby 2.6 and 2.7
+
+## [1.1.3] 2024-05-13
+
+### Changed
+- Updated gems in the Gemfile.lock
+
+### Added
+- Support for Ruby 3.2 and 3.3
+
+### Dropped
+- Check for support for 'ubuntu-18.04'
+
+## [1.1.2] 2022-12-28
+
+- Add Puma 6 compatibility
+
+## [1.1.1] 2022-06-22
+
+Public release.
+
+## [1.1.0] 2022-06-22
+
+Out of beta testing, reading for usage. Following is a recap from Alpha & Beta releases.
+
+### Added
+- new metric: `sockets.backlog` (disabled by default), pulls information from Puma
+  sockets about the state of their backlogs. This together with `queue.backlog`
+  allows for full insights into total number of requests waiting to be processed
+- `config.sockets_telemetry!` option to enable sockets telemetry
+- `config.socket_parser` option to allow custom parser implementation as needed
+- Datadog widgets examples under `docs/examples.md`
+
+## [1.1.0 Beta] ???
+### Added
+
+Different ways to parse `Socket::Option`. Mainly due to the fact that `#inspect` can't
+generate proper data on AWS Fargate, which runs Amazon Linux 2 with 4.14 kernel. So now
+besides `#inspect` there's also `#unpack` that parses binary data and picks proper field.
+
+It depends on the kernel, but new fields are usually added at the end of the `tcp_info`
+struct, so it should more or less stay stable.
+
+You can configure it by passing in `config.socket_parser = :inspect` or
+`config.socket_parser = ->(opt) { your implementation }`.
+
+## [1.1.0 Alpha] ???
+### Added
+
+Socket telemetry, and to be more precise new metric: `sockets.backlog`. If enabled it will
+pull information from Puma sockets about the state of their backlogs (requests waiting to
+be acknowledged by Puma). It will be exposed under `sockets-backlog` metric.
+
+You can enable and test it via `config.sockets_telemetry!` option.
+
+## [1.0.0] 2021-09-08
+### Added
+- Release to GitHub Packages
+- Explicitly flush Datadog metrics after publishing them
+- Middleware for measuring and tracking request queue time
+
+### Changed
+- Replace `statsd.batch` with direct calls, as it aggregates metrics internally by default now.
+  Also `#batch` method is deprecated and will be removed in version 6 of Datadog Statsd client.
+
+## [0.3.1] 2021-03-26
+### Changed
+- IO target replaces dots in telemetry keys with dashes for better integration with AWS CloudWatch
+
+## [0.3.0] 2020-12-21
+### Added
+- Datadog Target integration tests
+
+### Fixed
+- Datadog Target
+
+## [0.2.0] 2020-12-21
+### Fixed
+- Removed debugging information
+
+## [0.1.0] 2020-12-18
+### Added
+- Core Plugin
+- Telemetry generation
+- IO Target with JSON formatter
+- Datadog Statsd Target

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at tnt@babbel.com. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
+available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2022 Babbel GmbH
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,190 @@
+# Puma::Plugin::TelemetryToo
+
+NOTE: This is a fork of `puma-plugin-telemetry`, modified to:
+
+- Support Puma 7
+- Add `LogTarget`, with custom `formatter:` and `transform:` options
+- Warn about socket telemetry on unsupported platforms
+
+Puma plugin which should be able to handle all your metric needs regarding your webserver:
+
+- ability to publish basic puma statistics (like queue backlog) to both logs and Datadog
+- ability to add custom target whenever you need it
+- ability to monitor puma socket listen queue (!)
+- ability to report requests queue time via custom rack middleware - the time request spent between being accepted by Load Balancer and start of its processing by Puma worker
+
+## Install
+
+Add this line to your application's Gemfile:
+
+```ruby
+gem "puma-plugin-telemetry_too"
+```
+
+And then execute:
+
+```console
+$ bundle install
+```
+
+Or install it yourself as:
+
+```console
+$ gem install puma-plugin-telemetry_too
+```
+
+## Usage
+
+In your puma configuration file (i.e. `config/puma.rb` or `config/puma/<env>.rb`):
+
+```ruby
+plugin "telemetry"
+
+Puma::Plugin::TelemetryToo.configure do |config|
+  config.enabled = true
+
+  # << here rest of the configuration, examples below
+end
+```
+
+### Basic IO Target
+
+A basic I/O target will emit telemetry data to `STDOUT`, formatted in JSON.
+
+```ruby
+config.add_target(:io)
+```
+
+#### Options
+
+This target has configurable `formatter:` and `transform:` options.
+The `formatter:` options are
+
+* `:json` _(default)_ - Print the logs in JSON.
+* `:logfmt` - Print the logs in key/value pairs, as per `logfmt`.
+* `:passthrough` - A pass-through formatter which returns the telemetry `Hash` unaltered, passing it directly to the `io:` instance.
+
+The `transform:` options are
+
+* `:cloud_watch` _(default)_ - Transforms telemetry keys, replacing dots with dashes to support AWS CloudWatch Log Metrics filters.
+* `:logfmt` - Transforms telemetry keys, prepending `sample#` for [L2Met][l2met] consumption.
+* `:passthrough` -  A pass-through transform which returns the telemetry `Hash` unaltered.
+
+### Log target
+
+While emitting to `STDOUT` via the basic `IOTarget` can work for getting telemetry into logs, we also provide an explicit `LogTarget`.
+This target will defaults to emitting telemetry at the `INFO` log level via a [standard library `::Logger`][logger] instance.
+That default logger will print to `STDOUT` in [the `logfmt` format][logfmt].
+
+```ruby
+config.add_target(:log)
+```
+
+You can pass an explicit `logger:` option if you wanted to, for example, use the same logger as Rails.
+
+```ruby
+config.add_target(:log, logger: Rails.logger)
+```
+
+This target also has configurable `formatter:` and `transform:` options.
+The [possible options are the same as for the `IOTarget`](#options), but the defaults are different.
+The `LogTarget` defaults to `formatter: :logfmt`, and `transform: :passthrough`.
+
+[l2met]:  https://github.com/ryandotsmith/l2met "l2met - Logs to metrics"
+[logfmt]: https://brandur.org/logfmt "logfmt - Structured log format"
+[logger]: https://rubyapi.org/o/logger "Ruby's Logger, from the stdlib"
+
+### Datadog StatsD target
+
+A target for the Datadog StatsD client, that uses batch operation to publish metrics.
+
+**NOTE** Be sure to have the `dogstatsd` gem installed.
+
+```ruby
+config.add_target(:dogstatsd, client: Datadog::Statsd.new)
+```
+
+You can provide all the tags, namespaces, and other configuration options as always to `Datadog::Statsd.new` method.
+
+### All available options
+
+For detailed documentation checkout [`Puma::Plugin::TelemetryToo::Config`](./lib/puma/plugin/telemetry_too/config.rb) class.
+
+```ruby
+Puma::Plugin::TelemetryToo.configure do |config|
+  config.enabled = true
+  config.initial_delay = 10
+  config.frequency = 30
+  config.puma_telemetry = %w[workers.requests_count queue.backlog queue.capacity]
+  config.socket_telemetry!
+  config.socket_parser = :inspect
+  config.add_target :io, io: StringIO.new, formatter: :json, transform: :passthrough
+  config.add_target :dogstatsd, client: Datadog::Statsd.new(tags: { env: ENV["RAILS_ENV"] })
+end
+```
+
+### Custom Targets
+
+Target is a simple object that implements `call` methods that accepts `telemetry` hash object. This means it can be super simple `proc` or some sophisticated class calling some external API.
+
+Just be mindful that if the API takes long to call, it will slow down frequency with which telemetry will get reported.
+
+```ruby
+  # Example key/value log to `STDOUT` target
+  config.add_target ->(telemetry) { puts telemetry.map { |k, v| "#{k}=#{v.inspect}" }.join(" ") }
+```
+
+## Extra middleware
+
+This gems comes together with middleware for measuring request queue time, which will be reported in `request.env` and published to given StatsD client.
+
+Example configuration:
+
+```ruby
+# in Gemfile add `require` part
+gem "puma-plugin-telemetry_too", require: ["rack/request_queue_time_middleware"]
+
+# in initializer, i.e. `request_queue_time.rb`
+Rails.application.config.middleware.insert_after(
+  0,
+  RequestQueueTimeMiddleware,
+  statsd: Datadog::Statsd.new(namespace: "ruby.puma", tags: { "app" => "accounts" })
+)
+
+Rails.application.config.log_tags ||= {}
+Rails.application.config.log_tags[:queue_time] = ->(req) { req.env[::RequestQueueTimeMiddleware::ENV_KEY] }
+```
+
+This will provide proper metric in Datadog and in logs as well. Logs can be transformed into log metrics and used for auto scaling purposes.
+
+## Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `bundle exec rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`.
+
+## Release
+
+All gem releases are manual, in order to create a new release follow:
+
+1. Create new PR (this could be included in feature PR, if it's meant to be released)
+   - update `VERSION`, we use [Semantic Versioning](https://semver.org/spec/v2.0.0.html)
+   - update `CHANGELOG`
+   - merge
+2. Draft new release via Github Releases
+   - use `v#{VERSION}` as a tag, i.e. `v0.1.0`
+   - add release notes based on the Changelog
+   - create
+3. Gem will get automatically published to given rubygems server
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/stevenharman/puma-plugin-telemetry_too.
+
+## License
+
+The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).
+
+## Code of Conduct
+
+Everyone interacting in the puma-plugin-telemetry_too project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/stevenharman/puma-plugin-telemetry_too/blob/master/CODE_OF_CONDUCT.md).

data/Rakefile

@@ -0,0 +1,10 @@
+# frozen_string_literal: true
+
+require 'bundler/gem_tasks'
+require 'rspec/core/rake_task'
+require 'rubocop/rake_task'
+
+RSpec::Core::RakeTask.new(:spec)
+RuboCop::RakeTask.new
+
+task default: %i[rubocop spec]

data/docs/examples.md

@@ -0,0 +1,163 @@
+## Keeping track of waiting requests
+
+There are requests waiting in 2 places:
+- socket
+- queue
+
+Their sum is a total number of accepted requests waiting.
+
+Puma configuration
+
+```ruby
+plugin :telemetry
+
+Puma::Plugin::TelemetryToo.configure do |config|
+  config.enabled = true
+  config.initial_delay = 10
+
+  config.puma_telemetry = %w[queue.backlog]
+
+  config.socket_telemetry!
+
+  config.add_target :dogstatsd, client: Datadog::Statsd.new(tags: %w[your tags], namespace: "ruby.puma")
+end
+```
+
+Example Datadog widget and it's configuration. Depending on what you prefer to see, you might replace `rollup(max)` with `rollup(sum)` whenever you want to see maximum value or sum across the aggregated time frame.
+
+| :point_up:    | Remember to update tags after initial setup! |
+|---------------|:---------------------------------------------|
+
+![Datadog Widget, barchart showcasing sockets & queue backlog sizes stacked up](example-datadog_backlog_size.png "Datadog Widget")
+
+```json
+{
+    "viz": "timeseries",
+    "requests": [
+        {
+            "style": {
+                "palette": "dog_classic",
+                "type": "solid",
+                "width": "normal"
+            },
+            "type": "bars",
+            "formulas": [
+                {
+                    "alias": "queue",
+                    "formula": "query1"
+                },
+                {
+                    "alias": "socket",
+                    "formula": "query2"
+                }
+            ],
+            "response_format": "timeseries",
+            "on_right_yaxis": false,
+            "queries": [
+                {
+                    "query": "max:ruby.puma.queue.backlog{}.rollup(max)",
+                    "data_source": "metrics",
+                    "name": "query1"
+                },
+                {
+                    "query": "max:ruby.puma.sockets.backlog{}.rollup(max)",
+                    "data_source": "metrics",
+                    "name": "query2"
+                }
+            ]
+        }
+    ],
+    "yaxis": {
+        "include_zero": true,
+        "max": "auto",
+        "scale": "linear",
+        "min": "auto",
+        "label": ""
+    },
+    "markers": []
+}
+```
+
+## Keeping track of request queue time
+
+The time request spent waiting to be processed, between it's accepted by Load Balancer till it starts going through Rack Middleware in your application. Holy grail of autoscaling.
+
+Example configuration of middleware, i.e. in case of Rails it could be placed under `config/initializers/request_queue_time.rb`
+
+```ruby
+Rails.application.config.middleware.insert_after(
+  0,
+  RequestQueueTimeMiddleware,
+  statsd: Datadog::Statsd.new(namespace: "ruby.puma", tags: %w[your tags])
+)
+```
+
+If you are utilizing tags in your logs, you might also want to add this measurement as follows:
+
+```ruby
+Rails.application.config.log_tags ||= {}
+Rails.application.config.log_tags[:queue_time] = ->(req) { req.env[::RequestQueueTimeMiddleware::ENV_KEY] }
+```
+
+Example Datadog widget with configuration.
+
+| :point_up:    | Remember to update tags after initial setup! |
+|---------------|:---------------------------------------------|
+
+![Datadog Widget, barchart showcasing sockets & queue backlog sizes stacked up](example-datadog_queue_time.png "Datadog Widget")
+
+```json
+{
+    "viz": "timeseries",
+    "requests": [
+        {
+            "style": {
+                "palette": "dog_classic",
+                "type": "solid",
+                "width": "normal"
+            },
+            "type": "line",
+            "response_format": "timeseries",
+            "queries": [
+                {
+                    "query": "max:ruby.puma.queue.time.max{}",
+                    "data_source": "metrics",
+                    "name": "query1"
+                },
+                {
+                    "query": "max:ruby.puma.queue.time.95percentile{}",
+                    "data_source": "metrics",
+                    "name": "query2"
+                },
+                {
+                    "query": "max:ruby.puma.queue.time.median{}",
+                    "data_source": "metrics",
+                    "name": "query3"
+                }
+            ],
+            "formulas": [
+                {
+                    "alias": "max",
+                    "formula": "query1"
+                },
+                {
+                    "alias": "p95",
+                    "formula": "query2"
+                },
+                {
+                    "alias": "median",
+                    "formula": "query3"
+                }
+            ]
+        }
+    ],
+    "yaxis": {
+        "include_zero": true,
+        "max": "auto",
+        "scale": "linear",
+        "min": "auto",
+        "label": ""
+    },
+    "markers": []
+}
+```