* update docs * plugins: use plugin specific logging Hooking up pkg/log also changed NewWithPlugin to just take a string instead of a plugin.Handler as that is more flexible and for instance the Root "plugin" doesn't implement it fully. Same logging from the reload plugin: .:1043 2018/04/22 08:56:37 [INFO] CoreDNS-1.1.1 2018/04/22 08:56:37 [INFO] linux/amd64, go1.10.1, CoreDNS-1.1.1 linux/amd64, go1.10.1, 2018/04/22 08:56:37 [INFO] plugin/reload: Running configuration MD5 = ec4c9c55cd19759ea1c46b8c45742b06 2018/04/22 08:56:54 [INFO] Reloading 2018/04/22 08:56:54 [INFO] plugin/reload: Running configuration MD5 = 9e2bfdd85bdc9cceb740ba9c80f34c1a 2018/04/22 08:56:54 [INFO] Reloading complete * update docs * better doc |
||
---|---|---|
.. | ||
OWNERS | ||
pprof.go | ||
README.md | ||
setup.go | ||
setup_test.go |
pprof
Name
pprof - publishes runtime profiling data at endpoints under /debug/pprof
.
Description
You can visit /debug/pprof
on your site for an index of the available endpoints. By default it
will listen on localhost:6053.
This is a debugging tool. Certain requests (such as collecting execution traces) can be slow. If you use pprof on a live server, consider restricting access or enabling it only temporarily.
For more information, please see Go's pprof documentation and read Profiling Go Programs.
This plugin can only be used once per Server Block.
Syntax
pprof [ADDRESS]
If not specified, ADDRESS defaults to localhost:6053.
Examples
Enable pprof endpoints:
. {
pprof
}
Listen on an alternate address:
. {
pprof 10.9.8.7:6060
}
Listen on an all addresses on port 6060:
. {
pprof :6060
}