eyalkoren
eyalkoren
Fixing a bug discovered while testing this end-to-end: when Elastic Agent is ran through `./elastic-agent install`, it creates a file tree that is not readable for all users on Linux...
The Java attacher discovery relies on go-sysinfo, which requires cgo for macOS, which is not built into APM Server. Optional alternatives: - enhance go-sysinfo to use `sysctl` for listing processes,...
A followup on #8590 , which doesn't include Windows support. Two topics that require some investigation in this regard: 1. ~~We don't yet have a proper `ps`-equivalent for full command...
## Description of the issue As reported in https://github.com/elastic/apm-agent-java/issues/693 - we fail to parse the container ID from the `/proc/self/cgroup` file in Cloud Foundry Garden containers. The algorithm used by...
# Aligning span names This is the initial step towards aligning span names across agents. Naturally, it only deals with frameworks that are not language-specific. We have specs for those,...
**Is your feature request related to a problem? Please describe.** CPU metrics reported from containerised services are inaccurate. **Describe the solution you'd like** So far we only support [memory](https://github.com/elastic/apm/issues/291) cgroup-based...
Following up on https://github.com/elastic/apm-server/pull/8590: 1. If the attacher CLI is invoked with only `--include-pid` discovery rules, there's no need for discovery and for applying discovery rules, only try to attach...
We currently restrict ecs-reformatting only to file appenders (hardcoded in the implementations of [`createAndStartEcsAppender()`](https://github.com/elastic/apm-agent-java/blob/main/apm-agent-plugins/apm-logging-plugin/apm-logging-plugin-common/src/main/java/co/elastic/apm/agent/loginstr/reformatting/AbstractEcsReformattingHelper.java#L423) implementations). We should apply `SHADE` and `OVERRIDE` [options](https://www.elastic.co/guide/en/apm/agent/java/current/config-logging.html#config-log-ecs-reformatting) to standard output logging as well, especially since...
## Is your feature request related to a problem? We currently only create error events for logging APIs that accept a `Throwable`. Any error (and fatal) logging event should result...