Commit Graph

8 Commits (835a87aed2478ee441f2dbfab15124315ddd880a)

Author SHA1 Message Date
Wojciech Tyczynski e6d188fca8 Remove BoundPod structure 2015-03-17 10:27:41 +01:00
Satnam Singh 105803ce04 Update cluster level docs for proxy access 2015-03-02 16:14:03 -08:00
Brian Browning 3831aa7042 Add a clarification that the console output showing the kibana url is not present in versions below 0.11 2015-02-22 22:32:42 -08:00
Satnam Singh 295bd3768d Launch Elasticsearch and Kibana automatically 2015-01-09 13:41:46 -08:00
Alex Robinson 55709e3463 Mention Fluentd in the logging doc, as originally requested by Kiyoto in
PR 2727.
2014-12-11 14:29:52 -08:00
Eric Tune c47693c0d5 Separated user, dev, and design docs.
Renamed: logging.md -> devel/logging.m
Renamed: access.md -> design/access.md
Renamed: identifiers.md -> design/identifiers.md
Renamed:    labels.md -> design/labels.md
Renamed:    namespaces.md -> design/namespaces.md
Renamed:    security.md -> design/security.md
Renamed:    networking.md -> design/networking.md

Added abbreviated user user-focused document in place of most moved docs.

Added docs/README.md explains how docs are organized.
Added short, user-oriented documentation on labels
Added a glossary.
Fixed up some links.
2014-10-31 08:35:53 -07:00
Sam Ghods 868c6fe4b8 Increase logging levels in hack/local-up-cluster.sh 2014-10-07 00:07:05 -07:00
Clayton Coleman 4e56dafecc Introduce some default log verbosity control
Move a lot of common error logging into better buckets:

glog.Errorf() - Always an error
glog.Warningf() - Something unexpected, but probably not an error
glog.V(0) - Generally useful for this to ALWAYS be visible
            to an operator
            * Programmer errors
            * Logging extra info about a panic
            * CLI argument handling
glog.V(1) - A reasonable default log level if you don't want
            verbosity
            * Information about config (listening on X, watching Y)
            * Errors that repeat frequently that relate to conditions
              that can be corrected (pod detected as unhealthy)
glog.V(2) - Useful steady state information about the service
            * Logging HTTP requests and their exit code
            * System state changing (killing pod)
            * Controller state change events (starting pods)
            * Scheduler log messages
glog.V(3) - Extended information about changes
            * More info about system state changes
glog.V(4) - Debug level verbosity (for now)
            * Logging in particularly thorny parts of code where
              you may want to come back later and check it
2014-09-25 16:30:14 -04:00