Skip to content
This repository has been archived by the owner on Sep 14, 2019. It is now read-only.

Configure heartbeat requests to go straight to API #473

Merged
merged 82 commits into from Nov 26, 2018
Merged

Conversation

pwnbus
Copy link
Contributor

@pwnbus pwnbus commented Nov 9, 2018

This bypasses rabbitmq entirely for heartbeats. The agents will now post heartbeats to the API directly, which writes to postgres.

Zack Mullaly and others added 30 commits October 3, 2018 18:24
…ns of authorizing agents to upload heartbeats
…are authorized to upload heartbeats before saving them
database/actions.go Outdated Show resolved Hide resolved
database/schema.sql Outdated Show resolved Hide resolved
mig-api/api.go Show resolved Hide resolved
Copy link
Contributor

@arcrose arcrose left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like how this looks at this point. A couple notes for reviewers who follow:

  • Heartbeat type is redefined for both the agent and API to decouple them from one another.
  • Opted not to re-implement authentication for heartbeats due to the low efficacy of the current approach.

@arcrose arcrose merged commit e068d93 into master Nov 26, 2018
@arcrose arcrose deleted the abstract-rabbit branch November 26, 2018 20:52
arcrose added a commit that referenced this pull request Jul 9, 2019
Configure heartbeat requests to go straight to API
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants