The thing is that each transaction could connect with multiple external services. The ideal situation here would be a join between each transaction to an external service transaction table on a transaction ID, but you can’t join.
I’d imagine the join limitation is holding back this feature and others. But that’s for another more well-known feature request thread. And if someone suggests selecting from multiple sources please don’t, there’s no method to set an identifier on each source to filter them independently and you can’t join to the same table in any useful way either. You also can’t join on any particular attribute.
Ok, I’m sorry if the above seems very negative, I do appreciate you trying to help. I’ll try and reciprocate by giving an example, say you have a single service that is sporadically performing very badly and is logging transaction into the transaction table, how can you define a search on transactions that are above a certain APDEX score for that single service, not every single service, and get an average external service transaction time for each of the external services associated with that external transaction type. Alternatively, perhaps for each bucket of 0.05 on the Apdex scale you could chart it on a line graph from 0 to 1 on the X axis, and average time on the Y axis, with each line representing the average duration for a transaction that was taking a long time.
Even with the method above, you couldn’t do anything like this. I don’t know whether any of your competitors can do it either, but you give a developer, or a DevOps engineer, or a DBA access to a SQL like interface and there are certain things they expect to have, access to all data, common SQL functions like join, mod, left, right, etc then they should be able to use having, to be able to work with timestamps and durations with ease, and I could go on.
Thank you for pointing me to that alert condition, it does address part of the concern I had, however, it’s not the whole picture.