rack-insight will be merging back home into Rack Bug.
@brynary and I have discussed it, and I will do the work to re-namespace Rack Insight. Rack Insight, née Rack Bug, will be the basis of the next major release of Rack Bug.
I will be the new maintainer of the project.
Rack::Insight adds a diagnostics toolbar to Rack apps. When enabled, it injects a floating div allowing exploration of logging, database queries, template rendering times, etc. Rack::Insight stores debugging info over many requests, incuding AJAX requests.
| Project | Rack Insight |
|---|---|
| gem name | rack-insight |
| license | MIT |
| moldiness |  |
| version |  |
| dependencies |  |
| code quality |  |
| inline documenation |  |
| continuous integration |  |
| test coverage |  |
| homepage | https://github.com/pboling/rack-insight |
| documentation | http://rdoc.info/github/pboling/rack-insight/frames |
| author | Peter Boling |
| Spread |  |
| Working Example | On Rails 3.2.20 |
Add this to your Gemfile:
gem "rack-insight"
In config/environments/development.rb, add:
config.middleware.use 'Rack::Insight::App',
:secret_key => 'someverylongandveryhardtoguesspreferablyrandomstring'
Any environment with Rack::Insight loaded will have a link to "Rack::Insight" added to as
the last child of <body> to normal responses. Clicking that link will load the
toolbar. It's set with an id of "rack-insight-enabler", so it can be styled
to go somewhere more noticeable. E.g. "position: absolute; top: 0; left: 0"
Just use Rack::Insight::App as any other middleware. See the SampleApp in the
spec/fixtures folder for an example Sinatra app.
This is a minimal setup:
class SinatraExample < Sinatra::Base
get '/' do
<<-HTML
<html>
<head>
</head>
<body>
<p>Stink o' Man</p>
</body>
</html>
HTML
end
use Rack::Insight::App
end
Pattern:
Rack::Insight::Config.configure do |config|
config[:option] = value
end
Options:
:logger - Can be set to any Ruby-esque Logger, examples include the Rails Logger, or the Ruby Logger (default).
If you do not set logger Rack::Insight defaults to the Ruby Logger.
You can configure it with additional options:
:log_file - The logdev parameter for the Ruby Logger (a file path, an IO, like STDOUT, or STDERR, etc)
:log_level - The maximum severity at which things should be logged.
:rails_log_copy - If you are setting :logger to the Rails Logger, you should set this to false (default is true).
:verbosity - true is default.
true is equivalent to relying soley on the logger's log level to determine if a message is logged.
Other potential values are:
anything falsey => no logging at all
Rack::Insight::Config::VERBOSITY[*level*] where *level* is one of:
:debug, :high, :med, :low, :silent
:panel_load_paths => [File::join('rack', 'insight', 'panels')] (default)
See *Configuring custom panels* section for example usage
:panel_configs => This is a nested config, se below:
Panel level configuration options for all panels, including extension gems.
Currently this is implemented in the log_panel, and configured as:
Rack::Insight::Config.configure do |config|
# The following two lines have the same result
config[:panel_configs][:log] = {:probes => {'Logger' => [:instance, :add]}}
config[:panel_configs][:log] = {:probes => ['Logger', :instance, :add]}
end
Example: If you want all of your log statements in Rails to be traced twice by Rack::Insight,
this will do that because ActiveSupport::BufferedLogger utilizes Logger under the hood:
config[:panel_configs][:log_panel] = {:probes => {
"ActiveSupport::BufferedLogger" => [:instance, :add],
"Logger" => [:instance, :add]
}}
:database => a hash. Keys :raise_encoding_errors, and :raise_decoding_errors are self explanatory
:raise_encoding_errors
When set to true, if there is an encoding error (unlikely)
it will cause a 500 error on your site. !!!WARNING!!!
:raise_decoding_errors
The bundled panels should work fine with :raise_decoding_errors set to true or false
but custom panel implementations may prefer one over the other
The bundled panels will capture these errors and perform admirably.
Site won't go down unless a custom panel is not handling the errors well.
Specify the set of panels you want, in the order you want them to appear:
require "rack-insight"
ActionController::Dispatcher.middleware.use "Rack::Insight::App",
:secret_key => "someverylongandveryhardtoguesspreferablyrandomstring",
:panel_files => %w(
timer_panel
active_record_panel
request_variables_panel
redis_panel
templates_panel
cache_panel
log_panel
memory_panel
sphinx_panel
)
By default panel files are looked up by prepending "rack/insight/panels/" and requiring them. Subclasses of Rack::Insight::Panel are loaded and added to the toolbar. This makes it easier to work with the configuration and extend Rack::Insight with plugin gems.
If you need to customize the load paths where Rack::Insight will look for panels you can configure the load paths in an initializer, or in your gem prior to requiring your panels. Example config/initializers/rack_insight.rb:
Rack::Insight::Config.configure do |config|
# Note: The parent directory of the 'special' directory must already be in Ruby's load path.
config[:panel_load_paths] = File.join('special','path')
# Example 1: Do not load any of the regular Rack::Insight panels:
config[:panel_load_paths] = File.join('my','custom','panel','directory')
# Example 2: Add your custom path to the existing load paths, to have your panels join the party!
config[:panel_load_paths] << 'custom/panels'
end
When you create custom panels use the render_template method and pass it the path to the view to be rendered relative to the panel load path you added above:
# with Example #2 from above, will try to render 'custom/panels/thunder_panel/views/thor.html.erb'
render_template 'thunder_panel/views/thor'
We have have found that Rack::Insight is fast enough to run in production for specific troubleshooting efforts.
Add the middleware configuration to an initializer or the appropriate environment files, taking the rest of this section into consideration.
Restrict access to particular IP addresses:
require "ipaddr"
ActionController::Dispatcher.middleware.use "Rack::Insight::App"
:secret_key => "someverylongandveryhardtoguesspreferablyrandomstring",
:ip_masks => [IPAddr.new("2.2.2.2/0")]
Restrict access using a password:
ActionController::Dispatcher.middleware.use "Rack::Insight::App",
:secret_key => "someverylongandveryhardtoguesspreferablyrandomstring",
:ip_masks => false, # Default is 127.0.0.1
:password => "yourpassword"
Rack::Insight uses SQLite to store data across requests, and outputs a database file in the root directory. If you need the file to be created at another location (i.e. Heroku), you can pass a custom file path.
Please report back if you have success with this on Heroku!
ActionController::Dispatcher.middleware.use "Rack::Insight::App"
:secret_key => "someverylongandveryhardtoguesspreferablyrandomstring",
:database_path => "tmp/my_insight_db.sqlite"
You can now create a fully functional new panel with a simple class definition:
module Rack::Insight
class FooBarPanel < Panel
self.is_magic = true
end
end
Setup the probes for the magic panel in a before_initialize block in your application.rb as follows:
# Assuming there is a FooBar class with instance methods: foo, bar, cheese, and ducks
Rack::Insight::Config.configure do |config|
# Not :foo_bar_panel or 'FooBarPanel'... :foo_bar
config[:panel_configs][:foo_bar] = {:probes => {'FooBar' => [:instance, :foo, :bar, :cheese, :ducks]}}
end
See Magic Panels above, remove the is_magic declaration, and add your own methods. Look at the panels bundled with this gem for pointers. Here are some important methods to watch for:
Rack::Insight began life as an fork of Logical::Insight by LRDesign.
It should be even easier to extend than LogicalInsight was, because extension gems can access the Config class and truly bolt-on cleanly.
Having made really significant architectural changes, I'll be keeping Rack::Insight a separate project for the foreseeable future.
git checkout -b my-new-feature)git commit -am 'Added some feature')git push origin my-new-feature)This library aims to adhere to Semantic Versioning 2.0.0. Violations of this scheme should be reported as bugs. Specifically, if a minor or patch version is released that breaks backward compatibility, a new version should be immediately released that restores compatibility. Breaking changes to the public API will only be introduced with new major versions.
As a result of this policy, you can (and should) specify a dependency on this gem using the Pessimistic Version Constraint with two digits of precision.
For example:
spec.add_dependency 'rack-insight', '~> 0.5'
Rack::Insight owes a lot to both LogicalInsight and Rack::Bug, as the basis projects. There's a lot of smart in there. Many thanks to Judson, and Bryan for building them.
Inspiration for Rack::Bug is primarily from the Django debug toolbar. Additional ideas from Rails footnotes, Rack's ShowException middleware, Oink, and Rack::Cache
MIT. See LICENSE in this directory.
Legacy files: would like to re-include them, but they need work
lib/rack/insight/views/panels/mongo.html.erb
lib/rack/insight/panels/mongo_panel/mongo_extension.rb
lib/rack/insight/panels/mongo_panel/stats.rb
lib/rack/insight/panels/mongo_panel.rb
This one is mostly just a curiosity lib/rack/insight/panels/speedtracer_panel/profiling.rb
FAQs
Unknown package
We found that rack-insight demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.
Research
Security News
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.
Security News
NVD’s backlog surpasses 20,000 CVEs as analysis slows and NIST announces new system updates to address ongoing delays.