Instant deployment with Fleet Managed Cloud. Join the beta
Welcome to the documentation for Fleet, the lightweight telemetry platform for servers and workstations.
Install osquery and Fleet
Get startedCan't find what you need?
SupportThis document includes configuration files and settings that are helpful when developing or contributing to Fleet.
Unlike the configuration files documentation, the files and settings in this document are not recommended for production use. Each setting includes the best practice for being successful in production.
Integration settings in Fleet can be configured using the integrations
section of the config
YAML file. To see all settings in this file, check out the configuration files documentation.
Warning: Be careful not to store your integration credentials in source control. The best practice is to configure integrations via the Fleet UI.
Jira integrations are configured under the integrations.jira
field, which is an array of dictionaries.
This is the URL of the Jira server to use, including the scheme (e.g. "https://").
integrations:
jira:
- url: "https://example.atlassian.net"
username: "user1"
api_token: "secret"
project_key: "PJ1"
Use this username to authenticate API requests with the Jira server.
integrations:
jira:
- url: "https://example.atlassian.net"
username: "user1"
api_token: "secret"
project_key: "PJ1"
Use this API token to authenticate API requests with the Jira server.
integrations:
jira:
- url: "https://example.atlassian.net"
username: "user1"
api_token: "secret"
project_key: "PJ1"
Use this Jira project key to create tickets.
integrations:
jira:
- url: "https://example.atlassian.net"
username: "user1"
api_token: "secret"
project_key: "PJ1"
Whether the integration is configured to create Jira tickets for failing policies.
false
integrations:
jira:
- url: "https://example.atlassian.net"
username: "user1"
api_token: "secret"
project_key: "PJ1"
enable_failing_policies: true
Whether the integration is configured to create Jira tickets for recent software vulnerabilities.
false
integrations:
jira:
- url: "https://example.atlassian.net"
username: "user1"
api_token: "secret"
project_key: "PJ1"
enable_software_vulnerabilities: true
Zendesk integrations are configured under the integrations.zendesk
field, which is an array of dictionaries.
This is the URL of the Zendesk server to use, including the scheme (e.g. "https://").
integrations:
zendesk:
- url: "https://example.zendesk.com"
email: "[email protected]"
api_token: "secret"
group_id: 1234
Use this email address to authenticate API requests with the Zendesk server.
integrations:
zendesk:
- url: "https://example.zendesk.com"
email: "[email protected]"
api_token: "secret"
group_id: 1234
Use this API token to authenticate API requests with the Zendesk server.
integrations:
zendesk:
- url: "https://example.zendesk.com"
email: "[email protected]"
api_token: "secret"
group_id: 1234
Use this group ID to create tickets.
integrations:
zendesk:
- url: "https://example.zendesk.com"
email: "[email protected]"
api_token: "secret"
group_id: 1234
Whether the integration is configured to create Zendesk tickets for failing policies.
false
integrations:
zendesk:
- url: "https://example.zendesk.com"
email: "[email protected]"
api_token: "secret"
group_id: 1234
enable_failing_policies: true
Whether the integration is configured to create Zendesk tickets for recent software vulnerabilities.
false
integrations:
zendesk:
- url: "https://example.zendesk.com"
email: "[email protected]"
api_token: "secret"
group_id: 1234
enable_software_vulnerabilities: true
SMTP settings in Fleet can be configured using the smtp_settings
section of the config
YAML file. To see all settings in this file, check out the configuration files documentation.
Warning: Be careful not to store your SMTP credentials in source control. The best practice is to configure SMTP via the Fleet UI.
Use this authentication method when the authentication type is authtype_username_password
.
authmethod_plain
authmethod_cram_md5
authmethod_login
authmethod_plain
smtp_settings:
authentication_method: authmethod_cram_md5
This is the type of authentication for the configured SMTP server.
authtype_username_password
authtype_none
- use this if your SMTP server is openauthtype_username_password
- use this if your SMTP server requires authentication with a username and passwordsmtp_settings:
authentication_type: authtype_none
Whether SMTP support is enabled or not to send emails from Fleet.
false
smtp_settings:
enable_smtp: true
Whether to enable SSL/TLS for the SMTP connection.
true
smtp_settings:
enable_ssl_tls: false
Whether to detect if TLS is used by the SMTP server and start using it if so.
true
smtp_settings:
enable_start_tls: false
Use this password for SMTP authentication when the authentication_type
is set to authtype_username_password
.
smtp_settings:
password: supersekretsmtppass
Use this port to connect to the SMTP server.
587
(the standard SMTP port)smtp_settings:
port: 5870
Use this email address as the sender for emails sent by Fleet.
smtp_settings:
sender_address: [email protected]
This is the server hostname for SMTP.
smtp_settings:
server: mail.example.org
Use this username for SMTP authentication when the authentication_type
is set to authtype_username_password
.
smtp_settings:
user_name: test_user
Whether the SMTP server's SSL certificates should be verified. This can be turned off if self-signed certificates are used by the SMTP server.
true
smtp_settings:
verify_ssl_certs: false
If you notice something we've missed or could be improved on, please follow this link and submit a pull request to the Fleet repo.