Improvement
- Build process-agent with go 1.17
Bugfix
- Fix cgroup metrics collection for containers (STAC-18119)
Features
- Add metrics to "process" check of process-agent (STAC-16983)
Bugfix
- Fix default enabled checks (STAC-16953)
- Limited size of a message for self-health state check (STAC-17340)
Bugfix
- Remove some Kubernetes processes from blacklist
Bugfix
- Fix warning message to not have an "error" string
Features
- Reporting CPU throttling metrics for containers
- Reporting checks topology along with health states of those (to see faulted checks in StackState UI)
Improvements
- Support running process agent as a separate container in StackState Agent helm chart
Bugfix
- Fix hostname when process agent is running in a separate container
Improvements
- Use updated main agent which is now using go.mod
Bugfix
- Fix infinitely growing memory usage
Bugfix
- Process agent will send HTTP response times when they are zero's
Features
- Support for Containerd and CRI-O container runtimes
Improvements
- Moved from Gopkg.toml to go.mod
Improvement
- Set process agent check intervals to be default 30 seconds, added ENV variable overrides for process agent check intervals
Bugfix
- Process agent now acknowledges STS_SKIP_SSL_VALIDATION environment variable
Bugfix
- Fixed endianness in payload data
Bugfix
- Fixed bytes sent/received metrics for network connections going enormously high sometimes.
Bugfix
- Namespaces are not always reported for containers/processes running in k8s
- Increase network connection tracking limits and make them configurable
- Pods merge with the same ip address while using argo
Features
- Added collection interval to payload
Bugfix
- Fixed bytes sent/received metrics for network connections going enormously high sometimes
Bugfix
- Fix rebranding script to include
DOCKER_DD_AGENTandDD_APM_ANALYZED_SPANS - When setting
STS_PROCESS_AGENT_ENABLEDdo not disable container checks
Bugfix
- fix versioning script
Features
- Pass the cluster name along with the process metric information so that StackState can determine that the metrics came from Kuberentes/OpenShift.