Skip to content

Multiple Instances of osquery on a Host Causes Issues #108

Description

@obelisk

The way goserver and goquery work using UUIDs instead of Node Keys means that it's not deterministic when connecting to a UUID. You could have multiple instances of osquery and your request could go to any of them.

There should be something in goserver to detect this and goquery might want to be informed so a choice can be made (though that decision would be opaque behind the Node Key).

We should definitely at least guarantee that when you connect to a host, that all the queries are going to the same node key...some how.

Metadata

Metadata

Assignees

No one assigned

    Labels

    New APIFor issues or PRs that add functionality to goquery the requires new backend supportbugSomething isn't workingmock serverosqueryThis is related to the osquery process on the remote machinewishlist

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions