Files
fn-serverless/docs/operating/metrics.md
Benji Visser a32ca3d90a docs: moving documentation around to be more clear and easier to browse (#236)
* moving documentation around to be more clear and easier to browse

- moved assets into their own directory and updated links to them
- moved operating docs into their own directory
- consolidated kubernetes docs
- added docker-swarm folder for docs
- updated docs layout in docs/README.md to reflect the changes and make it easier to read

* docs: s/Operating Functions/Operating IronFunctions/

* docs: removing duplicate database link

* docs: moving databases into general docs

* docs: moving databases/mqs back

* docs: removing memory.md (duplicate of operating/routes.md)

* docs: converting to markdown bullets
2016-11-09 09:39:53 -08:00

26 lines
761 B
Markdown

# Metrics
Metrics are emitted via the logs for few couple of reasons:
1. Everything supports STDERR.
2. User can optionally use them, if not, they just end up in the logs.
3. No particular metrics system required, in other words, all metrics systems can be used via adapters (see below).
## Metrics
The metrics format follows logfmt format and looks like this:
```
metric=someevent value=1 type=count
metric=somegauge value=50 type=gauge
```
It's a very simple format that can be easily parsed by any logfmt parser and passed on to another stats service.
TODO: List all metrics we emit to logs.
## Statsd
The [Logspout Statsd Adapter](https://github.com/iron-io/logspout-statsd) adapter can parse the log metrics and forward
them to any statsd server.