mirror of https://github.com/fnproject/fn.git synced 2022-10-28 21:29:17 +03:00

Files

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

835 B

Raw Blame History

Logging

There are a few things to note about what IronFunctions logs.

Logspout

We recommend using logspout to forward your logs to a log aggregator of your choice.

Format

All logs are emitted in logfmt format for easy parsing.

Call ID

Every function call/request is assigned a call_id. If you search your logs, you can track all the activity for each function call and find errors on a call by call basis. For example, these are the log lines for an aynschronous function call:

Note the easily searchable call_id=x format.

call_id=477949e2-922c-5da9-8633-0b2887b79f6e

Metrics

Metrics are emitted via the logs.

See Metrics doc for more information.

835 B Raw Blame History