File: cmd.log-level.markdown

package info (click to toggle)
watchman 4.9.0-9
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid
  • size: 9,992 kB
  • sloc: cpp: 27,459; python: 6,538; java: 3,404; php: 3,257; ansic: 2,803; javascript: 1,116; makefile: 671; ruby: 364; sh: 124; xml: 102; lisp: 4
file content (44 lines) | stat: -rw-r--r-- 946 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
---
pageid: cmd.log-level
title: log-level
layout: docs
section: Commands
permalink: docs/cmd/log-level.html
---

Changes the log level of your connection to the watchman service.

From the command line:

```bash
$ watchman --server-encoding=json --persistent log-level debug
```

JSON:

```json
["log-level", "debug"]
```

This command changes the log level of your client session.  Whenever watchman
writes to its log, it walks the list of client sessions and also sends a log
packet to any that have their log level set to match the current log event.

Valid log levels are:

 * `debug` - receive all log events
 * `error` - receive only important log events
 * `off`   - receive no log events

Note that you cannot tap into the output of triggered processes using this
mechanism.

Log events are sent unilaterally by the server as they happen, and have
the following structure:

```json
{
  "version": "1.0",
  "log": "log this please"
}
```