Change meaning of agent.type and service.type
So far service.name was used for things like elasticsearch. APM is putting this information under service.type and service.name is not used yet. .name and .type is also used in other places in ECS. Most of the .name entries are user defined and type is predefined values.
The general suggestion is to make .type the value that will not change over time but .name can. A few examples:
Filebeat Agent reading MySQL logs on production
agent.name: filebeat-prod
agent.type: filebeat
service.name: mysql-prod
service.type: mysql
service.environment: prod
APM Node.js agent is running inside the service foo on testing (self built)
agent.name:
agent.type: apm-agent-nodejs
service.name: foo-test
service.type: foo
The same APM agent is running in the same service but in production:
agent.name:
agent.type: apm-agent-nodejs
service.name: foo-prod
service.type: foo
Currently in APM
service.name: "opbeans-python"
This is given by the user. type would be copied?
agent.name and service.name are empty if not set.