fleet/schema/tables/puppet_logs.yml
Lucas Manuel Rodriguez 4784217b57
Add documentation for missing fleetd tables and regenerate JSON (#9960)
Updating documentation of Fleetd tables as part of the oncall duty.

Updating the json used by Fleet using the following command:
```sh
cd website
 ./node_modules/sails/bin/sails.js run generate-merged-schema
```

Samples:
![Screenshot 2023-02-20 at 17 20
55](https://user-images.githubusercontent.com/2073526/220192112-69a116e4-badb-4328-92d3-9a2a6f8657fe.png)
![Screenshot 2023-02-20 at 17 21
09](https://user-images.githubusercontent.com/2073526/220192117-dfa06c69-2166-47d4-99c3-e108911e2084.png)


@mikermcneil @eashaw: `generate-merged-schema` generates a different
output every time it's executed. Guess: It seems it should sort the
output lexicograhically?
2023-02-22 16:05:36 -03:00

42 lines
1.2 KiB
YAML

name: puppet_logs
notes: This table is not a core osquery table. It is included as part of [Fleetd](https://fleetdm.com/docs/using-fleet/orbit), the osquery manager from Fleet. Fleetd can be built with [fleetctl](https://fleetdm.com/docs/using-fleet/adding-hosts#osquery-installer).
description: Outputs [Puppet](https://puppet.com/) logs from the last run.
platforms:
- darwin
- windows
- linux
evented: false
examples: >-
List Puppet logs that are of a level of anything but informational.
```
SELECT * FROM puppet_logs WHERE level!='info';
```
columns:
- name: level
description: The level of the log item (info, error, etc).
required: false
type: text
- name: message
description: The log message content.
required: false
type: text
- name: source
description: The source of the log item.
required: false
type: text
- name: time
description: The time at which this item was logged.
required: false
type: text
- name: file
description: The file from which osquery read this log.
required: false
type: text
- name: line
description: The line from which this log item was read.
required: false
type: text