APM self instrumentation

Elastic Observability APM
1

If you are asking about a problem you are experiencing, please use the following template, as it will help us help you. If you have a different problem, please delete all of this text :slight_smile:

Kibana version: 7.2

Elasticsearch version: 7.2

APM Server version: 7.2

APM Agent language and version: N/A

Original install method (e.g. download page, yum, deb, from source, etc.) and version: Kubernetes - official docker images

Fresh install or upgraded from other version? Fresh

Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):
I've tried to enable the self instrumentation of APM Server, due to a bottleneck I'm experiencing when ingesting at a high rate.
I've set

instrumentation:
      enabled: true

in the config, but it doesn't seem to be taking effect, as per logs:

2019-09-25T11:21:16.678Z    INFO    [beater]    beater/beater.go:253    self instrumentation is disabled

Is there any additional configuration necessary?
I've tried setting things like:

    instrumentation:
      enabled: true
      environment: "pre-prod"
      hosts:
        - "elastic-apm-elasticsearch:9200"

but still no success

2

Hi, I can't see anything wrong with it. Can you share the whole config?

Otherwise, you maybe can try executing apm-server like apm-server -e -E apm-server.instrumentation.enabled=true

Can you give some details about the bottleneck you are experiencing?

3

Hi,

Full config:

  apm-server.yml: |
    apm-server.host: 0.0.0.0:8200
    output.elasticsearch:
      hosts: "elastic-apm-elasticsearch:9200"
    setup.template.settings:
      index.number_of_shards: 1
      index.number_of_replicas: 2
    instrumentation:
      enabled: true
      environment: "pre-prod"
      hosts:
        - "elastic-apm-elasticsearch:9200"
    monitoring.enabled: true
    monitoring.elasticsearch:
    logging.level: "warning"

If i manually specify the command as you asked, it seems to work.

I'm not too sure about the bottleneck, and thus the need for self instrumentation. When we reach around 10,000 requests a minute to apm server, we start seeing errors/timeouts from agents. Scaling out additional apm server instances doesn't help. The elastic search stack doesn't seem to be under too much pressure. Just feeling around in the dark at the moment

4

I see: instrumentation should be nested inside apm-server, so apm-server.instrumentation:...

5

That did the trick ... thanks. I feel pretty stupid now.

6

This topic was automatically closed 20 days after the last reply. New replies are no longer allowed.