1516caad46
in #10134 we added a silent mechanism to try to read configuration values from macOS configuration profiles if --fleet-url and --enroll-secret weren't present. while using this logic to test #9459 I have found that there's a race condition where sometimes `fleetd` is installed before the configuration profile with the values delivered by Fleet, causing orbit to get stuck forever. I added logic to loop every 30 seconds and try to fetch the values again if none are found, but I didn't felt comfortable adding this logic without also adding an extra flag to explicitly enable this behavior. |
||
|---|---|---|
| .github | ||
| .storybook | ||
| .vscode | ||
| articles | ||
| assets | ||
| changes | ||
| charts/fleet | ||
| cmd | ||
| cypress | ||
| docs | ||
| ee | ||
| frontend | ||
| handbook | ||
| infrastructure | ||
| mdm_profiles | ||
| orbit | ||
| pkg | ||
| proposals | ||
| schema | ||
| scripts | ||
| server | ||
| terraform | ||
| test/upgrade | ||
| tools | ||
| website | ||
| .dockerignore | ||
| .eslintrc.js | ||
| .gitattributes | ||
| .gitignore | ||
| .gitpod.yml | ||
| .golangci.yml | ||
| .goreleaser-snapshot.yml | ||
| .goreleaser.yml | ||
| .npmignore | ||
| .prettierignore | ||
| .prettierrc.json | ||
| .trivyignore | ||
| CHANGELOG.md | ||
| CODE_OF_CONDUCT.md | ||
| CODEOWNERS | ||
| docker-compose.yml | ||
| Dockerfile | ||
| Dockerfile-desktop-linux | ||
| Dockerfile.osquery-perf | ||
| go.mod | ||
| go.sum | ||
| LICENSE | ||
| Makefile | ||
| manifest.yml.cloudgov.example | ||
| package.json | ||
| postcss.config.js | ||
| README.md | ||
| SECURITY.md | ||
| tools.go | ||
| tsconfig.json | ||
| webpack.config.js | ||
| yarn.lock | ||
Website News Report a bug
Fleet is the lightweight, open source telemetry platform for servers and workstations. Deploy osquery with Fleet to get comprehensive, customizable data from all your devices and operating systems – without the downtime risk.
Try Fleet
Head to fleetdm.com/try-fleet to fire up a one-off cloud instance for quickly trying out Fleet.
Now what?
Check out the Learn how to use Fleet doc to learn how to add your device to Fleet and how to ask questions about your devices by running queries.
Team
Fleet is independently backed and actively maintained with the help of many amazing contributors.
📖 In keeping with our value of openness, Fleet Device Management's company handbook is public and open source. You can read about the history of Fleet and osquery and our commitment to improving the product. To upgrade from Fleet ≤3.2.0, just follow the upgrading steps for the earliest subsequent major release from this repository (it'll work out of the box until the release of Fleet 5.0).
Documentation
Documentation for Fleet can be found here.
Community
Chat
Please join us in the #fleet channel on osquery Slack.
Contributing
Contributions are welcome, whether you answer questions on Slack/GitHub/StackOverflow/Twitter, improve the documentation or website, write a tutorial, give a talk, start a local osquery meetup, troubleshoot reported issues, or submit a patch. The Fleet code of conduct is on GitHub.
