Implement state reporting for Beats

[ruflin]

This is a meta issue to track the implementation of the state reporting to the API and X-Pack Monitoring

• Metricbeat modules Add Beats state reporting #7075
  • Elasticsearch template Add template config for Beat state to X-Pack Monitoring elasticsearch#31809
• Filebeat modules Add Filebeat module to state API #7532
• Filebeat inputs Add input counters and names to Filebeat state API #7530
• Output name Add output.name to state metrics #7522
• Queue name Add queue name to state reporting #7537
• Host info Add host reporting to state API endpoint #7508
• Update templates: Add new fields to monitoring template for Beats state elasticsearch#32085
• Update template version Update monitoring template version to 6040099 elasticsearch#32088

The reported event looks as following:

{
  "beat": {
    "name": "ruflin"
  },
  "host": {
    "architecture": "x86_64",
    "name": "ruflin",
    "os": {
      "build": "17E202",
      "family": "darwin",
      "platform": "darwin",
      "version": "10.13.4"
    }
  },
  "input": {
    "count": 1,
    "names": [
      "redis"
    ]
  },
  "module": {
    "count": 3,
    "names": [
      "system"
    ]
  },
  "output": {
    "name": "elasticsearch"
  },
  "queue": {
    "name": "mem"
  },
  "service": {
    "id": "0e1b1913-73db-4512-b17a-8209fa45eaa4",
    "name": "metricbeat",
    "version": "7.0.0-alpha1"
  }
}

For now processor were left out as they need some additions to the interface to be reported.

This ticket is kept open until the changes are also applied to the Elasticsearch template and all PR's are merged.

[hiiamok]

Hi,

we are experiencing a problem since the implementation of the state reporting.
We are using "Filebeat" and "Metricbeat" inside the same application.
During the initialisation a panic is thrown, because the name "module" is used in both beats.
Error Message: "panic: name module already used"

Can you suggest a workaround or possible fix?
Would it be possible to change the name to something unique, or instead of throwing a panic just returning an error?

Best regards

[elasticmachine]

Pinging @elastic/stack-monitoring

[cachedout]

@hiiamok IMHO, it might be better to file this as a brand-new issue along with steps to reproduce it so we can more easily troubleshoot what's going on here.

[botelastic]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[botelastic]

This issue doesn't have a Team:<team> label.