Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Enable custom database and table support for pt-heartbeat

Description

When collecting pt-heartbeat metrics via mysqld_exporter, it seems that the database and table names are hard-coded to heartbeat.heartbeat
We should be able to specify custom parameters for this, as it was possible in PMM1.
This seems to also be causing problem in

How to test

None

How to document

None

Smart Checklist

Activity

Show:

Lalit Choudhary October 9, 2020 at 11:59 AM

Hi Ivan,

Thank you for the report.

Michael Coburn September 18, 2020 at 3:18 PM

Michael Coburn September 18, 2020 at 3:16 PM

My $0.02

  1. use a more standard default such as schema: percona and continue with table name heartbeat

  2. hard code the default in mysqld_exporter to be percona.heartbeat

  3. hard code the default in pt-heartbeat to be percona.heartbeat

Details

Assignee

Reporter

Priority

Components

Needs QA

Yes

Needs Doc

Yes

Affects versions

Smart Checklist

Created September 18, 2020 at 3:12 PM
Updated March 6, 2024 at 3:53 AM
Configure