Cannot Parse Model Vertex Errors in Em.log

Seeing several DB related errors in em.log.. Below is an example of one of the errors from the MOM: 7/02/18 07:52:22.958 AM CDT [WARN] [main] [Manager.ATC.DAO] cannot parse model vertex com.fasterxml.jackson.databind.JsonMappingException: Invalid external id: SERVLET:TransferRequestHandler|ProcessRequest:QQQQQQQI002:mat_1.27.33:.NET Process (through reference chain: com.wily.introscope.appmap.em.ontology.ModelMergedVertex["externalId"]) at com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:379) at com.fasterxml.jackson.databind.JsonMappingException.wrapWithPath(JsonMappingException.java:339) at com.fasterxml.jackson.databind.deser.BeanDeserializerBase.wrapAndThrow(BeanDeserializerBase.java:1514) at com.fasterxml.jackson.databind.deser.BeanDeserializer.vanillaDeserialize(BeanDeserializer.java:262) at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:125) at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:3807) at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:2797) at com.wily.introscope.appmap.em.model.dao.impl.OntologyOperationsDaoImpl$2.mapRow(OntologyOperationsDaoImpl.java:162) at com.wily.introscope.appmap.em.model.dao.impl.OntologyOperationsDaoImpl$2.mapRow(OntologyOperationsDaoImpl.java:1) at org.springframework.jdbc.core.RowMapperResultSetExtractor.extractData(RowMapperResultSetExtractor.java:93) at org.springframework.jdbc.core.RowMapperResultSetExtractor.extractData(RowMapperResultSetExtractor.java:60) at org.springframework.jdbc.core.JdbcTemplate$1.doInPreparedStatement(JdbcTemplate.java:708) at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:644) at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:695) at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:722) at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.j

Should I be concerned?

Environment:

APM 10.x

Answer:

These warnings/exceptions in the EM logs about "Invalid external id" are due to missing layer/application name on parsing the external id string. To narrow down the root cause,review the agent side to see what transaction tracers were used and whether they were reporting the layer/application name accordingly.

Next Step:Gather the agent DEBUG logs and autoprobe logs from the .NET Agent that reported these transactions, e.g. for instance, TransferRequestHandler|ProcessRequest:QQQQQQI002:mat_1.27.33:.NET Process