monitoring: enable tracing self instrumentation in APM Server

[1pkg]

Motivation/summary

This PR addresses the issue #14230 and enables self instrumentation in APM Server.

Checklist

• Update CHANGELOG.asciidoc
• Documentation has been updated

For functional changes, consider:

• Is it observable through the addition of either logging or metrics?
• Is its use being published in telemetry to enable product improvement?
• Have system tests been added to avoid regression?

How to test these changes

Test that self-instrumentation is enabled by default in the Cloud.
Additionally verify that instrumentation config outlined in #13514 (comment) are handled correctly when orchestrated by the standalone agent.

Related issues

#14230

[mergify]

This pull request does not have a backport label. Could you fix it @1pkg? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-7.17 is the label to automatically backport to the 7.17 branch.
• backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
• backport-8.x is the label to automatically backport to the 8.x branch.

[mergify]

backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label.

[marclop]

I think this change needs a changelog entry

[1pkg]

While testing the changes manually, I discovered a bug in EA tracing sampling changes where sampling_rate is formatted as a binary (hex) with exponent instead of decimal literal without exponent, this breaks subsequent call in apm-agent-go when tracer is initialized with a custom sampling rate.

[1pkg]

Raised an issue in the agent repo elastic/elastic-agent#5711

[axw]

Thanks @1pkg!

[1pkg]

Can't be merged yet due to the Cloud configuration missing sensible default for sampling_rate.

[mergify]

This pull request is now in conflicts. Could you fix it @1pkg? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b enable-self-instrumentation-tracing upstream/enable-self-instrumentation-tracing
git merge upstream/main
git push upstream enable-self-instrumentation-tracing

[lahsivjar]

Testing on ESS

Tested successfully with 8.16 BC2, can visualize traces (screenshots attached)

Testing on Standalone

Tested successfully with commit SHA ae423f0

Ran the elastic-agent locally with the following docker-compose and elastic-agent.yml:

version: '3.9'
services:
  elastic-agent:
    image: elastic-agent-systemtest:8.16.0-0e756d08-SNAPSHOT
    networks:
      - network1
    ports:
      - 8220:8220
      - 8200:8200
    user: root
    environment:
      FLEET_SERVER_ENABLE: 'true'
      FLEET_SERVER_ELASTICSEARCH_HOST: http://elasticsearch:9200
      FLEET_SERVER_SERVICE_TOKEN: AAEAAWVsYXN0aWMvZmxlZXQtc2VydmVyL3Rva2VuLTE3MzAyNDE5NTk0OTA6bFo5TnNWMlFST3VPQmp1Q1MxVC1kQQ
      FLEET_SERVER_POLICY_ID: fleet-server-policy
      FLEET_SERVER_PORT: 8220
networks:
  network1:
    name: apm-server_default
    external: true

fleet:
  enabled: true

agent.monitoring:
  # enabled turns on monitoring of running processes
  enabled: true
  traces: true
  apm:
    environment: "816bctesting"
    global_labels:
      foo: localbctesting
    hosts:
      - https://88e3f5<REDACTED>.elastic-cloud.com:443 # this is a personal ESS cluster where I am sending monitoring data
    secret_token: <REDACTED>
    sampling_rate: 1

outputs:
  default:
    type: elasticsearch
    hosts:
      - 'http://elasticsearch:9200'
    username: admin
    password: changeme

Observed traces on 88e3f5 (configured monitoring cluster):