deac
/
dnsbl_exporter
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
dnsbl_exporter/config.ru

33 lines
983 B
Plaintext
Raw Normal View History

Splitting Registry for action and process-statistics and clean up repositry. config.yml was only an example, so name it as config.yml.example and ignore any config.yml, that checkout could be used as local project-directory without conflicts. DnsblCollector will have singleton-behaviour like process configs and an own Registry. Config was loaded every request, yet. There was one Registry, which was reused for every request. Now every request will use his own Registry. Requests will get the content of both Registries.
2021-05-09 14:39:21 +02:00
# vim: set noet sw=2 ts=2 sts=2:
first working implementation
2018-12-14 14:58:11 +01:00
require 'rack'
Splitting Registry for action and process-statistics and clean up repositry. config.yml was only an example, so name it as config.yml.example and ignore any config.yml, that checkout could be used as local project-directory without conflicts. DnsblCollector will have singleton-behaviour like process configs and an own Registry. Config was loaded every request, yet. There was one Registry, which was reused for every request. Now every request will use his own Registry. Requests will get the content of both Registries.
2021-05-09 14:39:21 +02:00
require_relative 'dnsbl_exporter'
require 'yaml'
first working implementation
2018-12-14 14:58:11 +01:00
Splitting Registry for action and process-statistics and clean up repositry. config.yml was only an example, so name it as config.yml.example and ignore any config.yml, that checkout could be used as local project-directory without conflicts. DnsblCollector will have singleton-behaviour like process configs and an own Registry. Config was loaded every request, yet. There was one Registry, which was reused for every request. Now every request will use his own Registry. Requests will get the content of both Registries.
2021-05-09 14:39:21 +02:00
DnsblCollector.load_config './config.yml'
first working implementation
2018-12-14 14:58:11 +01:00
run lambda {|env|
begin
req = Rack::Request.new env
case req.path
when '/metrics'
collector = DnsblCollector.new
target =
begin
target = IPAddr.new req.params['target']
rescue IPAddr::AddressFamilyError
return [400, {"Content-Type" => "text/plain"}, ["Valid target-IP-Address expected.\n"]]
end
collector.collect target
[200, {"Content-Type" => "text/plain"}, [
Splitting Registry for action and process-statistics and clean up repositry. config.yml was only an example, so name it as config.yml.example and ignore any config.yml, that checkout could be used as local project-directory without conflicts. DnsblCollector will have singleton-behaviour like process configs and an own Registry. Config was loaded every request, yet. There was one Registry, which was reused for every request. Now every request will use his own Registry. Requests will get the content of both Registries.
2021-05-09 14:39:21 +02:00
Prometheus::Client::Formats::Text.marshal( collector.registry),
Prometheus::Client::Formats::Text.marshal( DnsblCollector.registry),
first working implementation
2018-12-14 14:58:11 +01:00
]]
else
[404, {"Content-Type" => "text/plain"}, ["Not found.\nYou want to try /metrics?\n"]]
end
rescue
STDERR.puts "#$! (#{$!.class})", $!.backtrace
[500, {"Content-Type" => "text/plain"}, ["Server-error.\n"]]
end
}