---
title: 'Beats: Metricbeat'
description: Send Metricbeat metric data to Coralogix through your own Logstash instance, from a host machine or a Docker container.
url: https://coralogix.com/docs/integrations/metrics/metricbeat/
product: ingress
feature: Metrics Ingress
feature_id: metrics.ingress
feature_identifier: ingress/metrics.ingress
last_updated: '2026-10-29'
---

# Beats: Metricbeat

Coralogix integrates with `Metricbeat` so you can send your metric data from anywhere and create metric dashboards.

## What you need

* Have `Metricbeat` installed. For more information on how to install it, see [the Elastic documentation](https://www.elastic.co/guide/en/beats/metricbeat/current/metricbeat-installation.html).

* A [Logstash](https://coralogix.com/docs/integrations/files/logstash.md) instance that you run in your own infrastructure, configured to receive Beats input and forward it to Coralogix. Coralogix no longer hosts a Logstash server for Beats shippers. See [Run your own Logstash instance](https://coralogix.com/docs/user-guides/latest-updates/deprecations/logstash.md#run-your-own-logstash-instance) for the Logstash input, filter, and output configuration.

## General

**Private Key**: Your [Send-Your-Data API key](https://coralogix.com/docs/user-guides/account-management/api-keys/send-your-data-api-key.md) is a unique ID that represents your company.

**Application Name**: The name of your main application, for example, a company named "SuperData" would probably insert the "SuperData" string parameter or if they want to debug their test environment they might insert the "SuperData - Test".

**SubSystem Name**: Your application probably has multiple subsystems, for example: Backend servers, Middleware, Frontend servers etc. in order to help you examine the data you need, inserting the subsystem parameter is vital.

## Configuration

### On the host machine

Open your `Metricbeat` configuration file and configure it to use `Logstash`. For more information about configuring `Metricbeat` to use `Logstash`, see [the Elastic documentation](https://www.elastic.co/guide/en/beats/metricbeat/current/logstash-output.html).

Point your `Metricbeat` to output to your own Logstash instance:

```
<logstash-ip-address>:5044
```

Note

The Coralogix-hosted Logstash endpoints (`logstashserver.coralogix.com`, `logstash.coralogix.in`, `logstashserver.coralogix.us`) are retired and no longer accept data. See [Deprecation of Coralogix-hosted Logstash](https://coralogix.com/docs/user-guides/latest-updates/deprecations/logstash.md).

Set the [General](#general) values (Send-Your-Data API key, application name, and subsystem name) in your Logstash configuration, not in `metricbeat.yml`.

Here is a basic example of a `metricbeat.yml` file for collecting metrics from a `Redis` server:

```
metricbeat.modules:

- module: redis

  enabled: true

  hosts: ["redis:6379"]

  metricsets: ["info", "keyspace"]

  period: 10s



output.logstash:

  enabled: true

  hosts: ["<logstash-ip-address>:5044"]
```

### With Docker

Build Docker image with your `metricbeat.yml`:

```
FROM docker.elastic.co/beats/metricbeat:6.6.2



LABEL description="Metricbeat metrics data collector"



# Adding configuration file for Metricbeat

COPY metricbeat.yml /usr/share/metricbeat/metricbeat.yml



# Changing permission of configuration file

USER root

RUN chown root:metricbeat /usr/share/metricbeat/metricbeat.yml



# Return to deploy user

USER metricbeat
```

## Usage

You can also deploy with Docker-compose:

```
version: '3.6'

services:

  redis:

    image: redis:latest

    container_name: redis



  metricbeat:

    image: docker.elastic.co/beats/metricbeat:6.6.2

    container_name: metricbeat

    volumes:

      - ./metricbeat.yml:/usr/share/metricbeat/metricbeat.yml:ro
```

Make sure you change the owner of the `metricbeat.yml` file to `root` (uid=1000).