Manages user profile metrics
Sample package to illustrate best practices for controllers
NestJS module for Prometheus
A simple abort controller library
OpenTelemetry Collector Metrics Exporter allows user to send collected metrics to the OpenTelemetry Collector
OpenTelemetry metrics SDK
An implementation of WHATWG AbortController interface.
OpenTelemetry Collector Metrics Exporter allows user to send collected metrics to the OpenTelemetry Collector
Client for prometheus
Native metrics collector for libuv and v8
OpenTelemetry Collector Metrics Exporter allows user to send collected metrics to the OpenTelemetry Collector using protobuf over HTTP
Microsoft Azure SDK for JavaScript - Aborter
AbortController for Node based on EventEmitter
Buffered metrics reporting via the Datadog HTTP API
Easily measure performance metrics in JavaScript
Unpack capsize font metrics from fonts
OpenTelemetry Exporter Prometheus provides a metrics endpoint for Prometheus
A module for generating metrics from V8.
PM2.io NodeJS APM
Abortable async function helpers
Utility functions to calculate mutation testing metrics.
Keyboard manager which works in identical way on both iOS and Android
Transform OpenTelemetry SDK data into OTLP
OpenTelemetry Host Metrics for Node.js
A ruby gem inspired by HireFire to autoscale kubernetes controllers and docker services. Metrics can be standard average response time, New Relic web metrics, queue size for workers, ...
metrics allows one to track the performance of particular controllers, database calls, and other methods
Gem that will let you control your code quality by reporting custom metrics to [CodeStats](https://github.com/Wolox/codestats)
RequestMetrics provides a base class for attaching per-request counters and timing metrics to Rails controller log lines. Subclass RequestMetrics::Base, declare metrics with metric_accessor, implement #log and .summary_log, and the gem wires everything into ActionController via a Railtie automatically.
Using the provided API, record metrics (such as number of hits to a particular controller, bytes in/out, compression ratio) within your system. Visualization is NOT provided within this gem.
SolidStackWeb is a mountable Rails engine that provides a production-ready operations dashboard for the full Solid Stack. It covers Solid Queue (job browser, failed job retry with inline argument editing, queue pause/resume, recurring tasks, performance stats, CSV export, and alert webhooks), Solid Cache (entry browser, size distribution, 24-hour write timeline, and optional value preview), and Solid Cable (channel browser, per-channel message list, and purge controls). Ships with dark mode, Turbo Stream responses, a JSON metrics endpoint, and no asset pipeline dependency.
The DevCreek gem enables programmers to collect and transmit metrics from their Ruby Test::Unit and RSpec test suites to a DevCreek server. Please visit the DevCreek site (http://devcreek.com/index.html) for more info. == FEATURES/PROBLEMS: Supported frameworks include Test::Unit and RSpec (> 1.10). == SYNOPSIS: The DevCreek Ruby Gem is library that, when loaded, will automatically listen to and collect metrics from your Test::Unit/RSpec unit tests. All you have to do is load the DevCreek library in your code and give it your DevCreek account info so that it can transmit the metrics to the server. Here is the simplest example of how to load DevCreek: -------- #Load the devcreek gem require 'rubygems' require 'devcreek' #set your account info DevCreek::Core.instance().load_from_yaml("#{ENV['HOME']}/.yoursettingsfile.devcreek.yml") -------- There are two ways to provide DevCreek with your account settings. The first (as shown above) is to point DevCreek to a settings file. The 'enabled' attribute tells devcreek whether or not it should actually transmit the metrics that it collects. The yaml file would like this: -------- user: your_devcreek_username password: your_devcreek_password project: your_devcreek_project enabled: true -------- The other way to provide DevCreek with your settings is via a hash. So, instead of loading a yaml file, you could do this: -------- #Load the devcreek gem require 'rubygems' require 'devcreek' #set your account info DevCreek::Core.instance().load( :user => 'your_devcreek_username', :password => 'your_devcreek_password', :project => 'your_devcreek_project', :enabled => true ) -------- The first method is preferrable because it allows you to keep your account settings outside of your project (and therefore your source control tool). If you only have 1 test file, you can place the code to load devcreek in the test file and your done. However, most projects will have many test files. In this case, you need to make sure that the Ruby interpreter loads devcreek before running the test classes. This can be done via the Ruby '-r' option. For example, assuming your code to load devcreek is in a file called foo.rb, you would run your tests from the command line like this: ruby -r foo.rb test/test_* If you run your tests from a Rakefile, then you need to tell rake to include the -r option when it runs the tests (rake runs it's tests in a separate Ruby process). You can do this pretty easily in your Rakefile, like so; -------- require 'rake/testtask' Rake::TestTask.new('all_tests') do |t| t.ruby_opts = ['-r foo.rb'] t.test_files = ['test/test_*.rb'] end --------
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.