In NAM 2019 it is possible to control what kind of applications are created on Dynatrace side. This requires config file tweaking on NAM server. See https://www.dynatrace.com/support/doc/nam/shortlink/id-unifying-dc-rum-data-with-dynatrace-saas-and-....
Unfortunately in NAM 2018 it's always one software service - one app on D side, though the list of exported software services is controlled, in the Console.
Hope this helps.
As stated in the original question the ingested DCRUM software services were seen as separate applications.
We have Managed connected with NAM 2019 instance. With the interface set to 'Dynatrace SaaS-Managed export bu applications'.
Now for every software service - application combination, an application entry is registered in the format of "<application name> (<software service>)". Which is almost the same.
The applications count in Managed is now larger than the amount of applications (in NAM).
I would expect to be able to see/use just the <application name>. Where under relations to services are made. And the application be used when OA dat will be added.
I guess this is by design, but is this something that we can control/change?
@Krzysztof Z. what is your take on this?
Your guess is right, that's how the integration is designed and implemented, software service name becomes part of application name thus number of applications is often increased. I would like to underline, that main benefit of 'export bu applications' setting is not a possibility of aggregating data into single entities as applications. It's rather possibility of exporting to Dynatrace not whole software service visible on NAM side, but only it's part which matches rules defined in BU configuration on NAM side (I mean metrics calculated for this part of traffic)
Is there a way to change it? Well, short answer is No, however, perhaps there is a way to improve things on NAM side configuration. Perhaps you may consider replacing multiple services which you have under your applications with single software service with multiple rules ? Of course I realize, that it is possible only in case of software services working with the same analyzer, so you can not work with frontend and backend this way, but still, perhaps it could be step into right direction