# Only seeing CPU and Memory metrics in Kibana

**URL:** https://discuss.elastic.co/t/only-seeing-cpu-and-memory-metrics-in-kibana/236626
**Category:** APM
**Tags:** nodejs
**Created:** [June 11, 2020, 6:42am UTC](https://discuss.elastic.co/t/only-seeing-cpu-and-memory-metrics-in-kibana/236626 "2020-06-11T06:42:22Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![dobes\_gf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dobes_gf/32/70116_2.png) [@dobes\_gf](https://discuss.elastic.co/u/dobes_gf)
#### Post date: [June 11, 2020, 6:42am UTC](https://discuss.elastic.co/t/only-seeing-cpu-and-memory-metrics-in-kibana/236626/1 "2020-06-11T06:42:22Z")

</div>

**Kibana version** :

7.7.1

**Elasticsearch version** :

7.7.1

**APM Server version** :

7.7.1

**APM Agent language and version** :

elastic-apm-node 3.6.1

**Original install method (e.g. download page, yum, deb, from source, etc.) and version**:

docker / kubernetes

**Fresh install or upgraded from other version?**

Upgraded from earlier versions

**Is there anything special in your setup?**

```
apm-server:
  host: '0.0.0.0:8200'
  frontend:
    enabled: false
  rum:
    enabled: true
  kibana:
    enabled: true
    host: 'http://kibana:5601'
  ilm:
    setup:
      enabled: "true"
      overwrite: true
      mapping:
        - event_type: 'error'
          policy_name: 'apm-formative-policy'
        - event_type: 'span'
          policy_name: 'apm-formative-policy'
        - event_type: 'transaction'
          policy_name: 'apm-formative-policy'
        - event_type: 'metric'
          policy_name: 'apm-formative-policy'
        - event_type: 'profile'
          policy_name: 'apm-formative-policy'
      policies:
        - name: 'apm-formative-policy'
          policy:
            phases:
              hot:
                actions:
                  rollover:
                    max_size: '50gb'
                    max_age: '1d'
                  set_priority:
                    priority: 100
              warm:
                min_age: '7d'
                actions:
                  set_priority:
                    priority: 50
                  readonly: {}
              cold:
                min_age: '14d'
                actions:
                  set_priority:
                    priority: 0
                  freeze: {}
              delete:
                min_age: '30d'
                actions:
                  delete: {}
setup.template.settings:
  index:
    number_of_shards: 1
    codec: best_compression
output.elasticsearch:
  hosts: ['http://elasticsearch:9200']
  bulk_max_size: 2560
  workers: 2
queue:
  mem:
    events: 10240
logging:
  level: warning
  json: true

```

**Description of the problem including expected versus actual behavior. Please include screenshots (if relevant)**:

When I view metrics for a node.js process I only see CPU and memory metrics. However, the documentation indicates that many other metrics should / could be collected. I'm not quiet sure where to start debugging this, or to be honest if those metrics are currently even supposed to appear in kibana or if I'm supposed to query them myself.

**Steps to reproduce** :

1. Run a node.js process with elastic-apm-node
2. Observe what metrics you see for that service in Kibana

---

<div class="post-metadata">

### Author: ![simitt](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simitt/32/106406_2.png) [@simitt](https://discuss.elastic.co/u/simitt)
#### Post date: [June 12, 2020, 6:53am UTC](https://discuss.elastic.co/t/only-seeing-cpu-and-memory-metrics-in-kibana/236626/2 "2020-06-12T06:53:45Z")

</div>

Hi @dobes_gf,  
as you mentioned, the system cpu and memory information is shown in the `metrics` tab. There is also the _Time spent by span type_ in the `transaction` tab, that is based on collected metrics.

Additional `nodejs` specific metrics are currently not incorporated into the curated APM UI. They should however be collected, allowing you to query for them and build your own visualizations.

---

<div class="post-metadata">

### Author: ![dobes\_gf](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dobes_gf/32/70116_2.png) [@dobes\_gf](https://discuss.elastic.co/u/dobes_gf)
#### Post date: [June 12, 2020, 4:38pm UTC](https://discuss.elastic.co/t/only-seeing-cpu-and-memory-metrics-in-kibana/236626/3 "2020-06-12T16:38:52Z")

</div>

Ah OK, thanks for clarifying that.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 3, 2020, 12:38pm UTC](https://discuss.elastic.co/t/only-seeing-cpu-and-memory-metrics-in-kibana/236626/4 "2020-07-03T12:38:57Z")

</div>

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