024fbd1c2d
* prevent eslintrc conflicts * Pricing + chat for website (#124) * Update manage users styles. Implement table (list) view. (#104) The goal of this PR is to change the layout of the manage users to a table (list view). Move the user actions into the table view. Move EditUserForm into a Modal Update styles for InviteUserForm Edit copy for the configuring SMTP warning. * Update query page (edit, new, manage) and packs page (edit, new, manage) styles. (#106) The goal of this PR is to update the style across the query and packs pages so they are consistent with the latest global styles (colors, buttons, and fonts). * Update app settings page and osquery options page styles. (#107) The goal of this PR is to implement the new global styling (colors, buttons, and fonts) to the "App settings" and "Osquery options" pages. These pages are only visible to users granted an admin role. * Fix and clarify API auth documentation (#109) - Fix header name. - Add note about SSO auth. * New styles for 404, 500, Login, User settings, and Confirm invite pages. (#108) - Kolide404 and Kolide500 components renamed to Fleet404 and Fleet500 - Styling for Login and Confirm invite pages are consistent with the recent changes to the Setup page. - Add "*" character to the 404 <Route />'s path property. Now the 404 page renders when there is no exact path match. * Fix JSON in rest-endpoints.md (#110) * Add host enrollment cooldown period (#112) This addresses an issue some users experienced in which performance problems were encountered when hosts were "competing" for enrollment using the same osquery host identifier. The issue is addressed by adding a cooldown period for host enrollment, preventing the same (as judged by osquery host identifier) host from enrolling more than once per minute. When users end up in the problematic scenario, they will see quite a bit of error logs due to this issue. For now that's probably a good thing as users need to be aware of the lack of visibility. We can explore rate limiting the logging if that becomes an issue for someone. Fixes #102 * Improve MySQL transaction error logging (#113) Clarify what exactly happened when logging these errors. * Migrate remaining URLs to fleetdm.com (#116) * Clean up unused test/demo SQL data (#117) * Add style fixes caught during QA. Add favicon. (#119) Changes include style fixes that were caught during a QA pass. * Make password reset styles consistent with new global styles. (#120) The changes include adding sentence casing and updating the styles of the and components. * CHANGELOG for 3.5.0 (#121) * Update fleetctl version number. Fix spelling error in changelog. (#122) * Fix alt tag * Set up pricing cards * Match footer to bottom of gradient * Set up FAQ and stub out chat button click * Add chat, plus some other tweaks. * fiddling with Papercups to hopefully get it to recognize who's responding from the Fleet side * This isn't really a solution but it's the best we've got til Papercups is hacked to allow programmatic opening (or til we switch to something else, or just bring in the traditional contact form) * trivial * Temporary workaround using an undocumented API in papercups Co-authored-by: Rachael Shaw <rachaelshaw@users.noreply.github.com> Co-authored-by: Mike McNeil <mikermcneil@users.noreply.github.com> Co-authored-by: Rachael McNeil <r@rachael.wtf> Co-authored-by: Rachael Shaw <rachaelshaw@users.noreply.github.com>
Website News Report a bug
Fleet is the most widely used open source osquery manager. Deploying osquery with Fleet enables programmable live queries, streaming logs, and effective management of osquery across 50,000+ servers, containers, and laptops. It's especially useful for talking to multiple devices at the same time.
Try Fleet
With Node.js installed:
# Get the Fleet command-line tool
npm install -g fleetctl
With Docker installed:
# Run a local demo of the Fleet server
fleetctl preview
A local copy of the Fleet server is now running at https://localhost:8412.
Adding hosts
Now that you've finished setting up Fleet, you will want to enroll a server, container, or laptop so you have something to run queries against.
Fleet comes with simulated hosts you can use for demo purposes.
First, finish setting up Fleet in the browser and retrieve your "Enroll Secret" by clicking the "Add New Host" button in the Fleet dashboard.
Then after cloning this repository,
cdinto theosquery/directory:cd osquery/This directory contains configuration that can start up Docker containers running osquery agents. To start them up:
ENROLL_SECRET=<paste your enroll secret here> docker-compose upNow navigate back to https://localhost:8412 or refresh to see your new hosts in Fleet!
Your first query
Ready to run your first query? Target some of your sample hosts and try it out:
Team
Fleet is independently backed and actively maintained with the help of many amazing contributors.
🎉 Announcing the transition of Fleet to a new independent entity 🎉
Please check out the blog post to understand what is happening with Fleet and our commitment to improving the product. To upgrade from Fleet ≤3.2.0, just grab the latest release from this repository (it'll work out of the box).
Documentation
Documentation for Fleet can be found here on GitHub.
Community
Chat
Please join us in the #fleet channel on osquery Slack.
Community projects
Below are some projects created by Fleet community members. Please submit a pull request if you'd like your project featured.
- Kolide Cloud ("K2") is a cloud-hosted, user-driven security SaaS application. To be clear: Kolide ≠ Fleet.
- davidrecordon/terraform-aws-kolide-fleet - Deploy Fleet into AWS using Terraform.
- deeso/fleet-deployment - Install Fleet on a Ubuntu box.
- gjyoung1974/kolide-fleet-chart - Kubernetes Helm chart for deploying Fleet.
