Releases: OpsMx/oes-birger
v4.0.0
BREAKING CHANGES
This release is a pretty much entire rewrite of the gRPC transport to make it easier to handle data flows independently, and not cause one bad actor, be it client or server, to tie up the whole system.
Configuration Changes
Minor changes. Mostly these are related to adding prometheusListenPort
to the client (aka agent)
Network Changes
The old agent and controller protocol are completely rewritten. They are not compatible.
Image Names
The old names of forwarder-controller
and forwarder-agent
have been renames to agent-controller
and agent-client
.
Authentication Changes
The agent used to use a TLS certificate and key. It now uses a JWT. The command-and-control API has been changed to return this JWT for the /api/v1/generateAgentManifestComponents
endpoint.
Other changes
- Logging is much improved. Technical details: using the go
context.Context
package, a logger is added to a context with optional fields, and those fields are logged in all subsequent loggers generated from this context. This means the agent name and other details for a HTTP stream are properly logged in all cases and no longer requires explicit coding intent to add them. agent-client
creates a prometheus HTTP service on port 9102 by default.- The
agent-controller
andagent-client
images have a--profile
option, which will runpprof
services on the prometheus HTTP server port at/debug/pprof
. This is mostly used for testing and debugging, and should not generally be used. - Many bugs were fixed by this rewrite, including handling memory in a much better way.
Issues
- Streaming HTTP sessions are not yet fully profiled, but should be working.
- "reverse connections" (incoming HTTP clients on the agent) which are serviced by the controller are not yet implemented. This will be in v4.1.
v3.5.9
What's Changed
- fix(memleak): close http response body by @skandragon in #16
Full Changelog: v3.5.8...v3.5.9
v3.5.8
What's Changed
- chore: add 'argocd' service type to docs by @skandragon in #13
- feat: log non-2xx responses agent-side by @skandragon in #14
- feat: retry initial grpc dial by @skandragon in #15
Full Changelog: v3.5.7...v3.5.8
v3.5.7
What's Changed
- feat: set X-Opsmx-Agent-Name header by @skandragon in #12
Full Changelog: v3.5.6...v3.5.7
v3.5.6
Zapify.
Also log the remote IP address on the initial agent Hello message.
v3.5.5
log credential failures
v3.5.3
add version to manifest return
v3.5.2
handle missing agentInfo
v3.5.1
handle null annotations on agentInfo
v3.5.0
Add "annotations" which is a key: value
map to agentInfo and outgoing services.
These will be sent from the agent to the controller, and are shown in the getAgentStatistics
API call.