Dynatrace v2 API returns UNKNOWN for Software Components – Best practices?

NicolasDUMOUL1 — Mon, 09 Feb 2026 07:26:58 GMT

I’m encountering an issue when retrieving Software Components for a Process Group Instance via the Dynatrace v2 API. My goal is to identify the dependencies and libraries used by an application’s processes.

Here’s what I’ve observed:

When querying the v2 API /entities/{PGI_ID}, I correctly get the list of Software Components linked to a PGI.
For some Software Components, the displayName field is returned as UNKNOWN SOFTWARE_COMPONENT-ID.
Even after enabling all OneAgent features, enabling Deep Monitoring, and restarting the server, some PGIs still have 100% of their SCs marked as UNKNOWN.

Some technical observations:

UNKNOWN SCs do not contain any information in properties or tags.
The icon field shows primaryIconType: unknown.
The toRelationships.isSoftwareComponentOfPGI link is present, so the relationship with the PGI is correct.

Example:

For a Spring Boot process, I enabled all OneAgent features, and Dynatrace returns 90 unknowns out of 90 Software Components found.

For another process, even without enabling the features, I get no unknowns.

What I’d like to ask the community:

Is it expected that some Software Components remain UNKNOWN even with OneAgent features and Deep Monitoring?
Are there recommended ways to automatically populate the displayName or the technology/version of these UNKNOWN SCs?
Do you have any experience or best practices for getting a complete inventory of dependencies/libraries via Dynatrace, especially for vulnerability analysis?

Thank you in advance for your feedback and advice!

topic Dynatrace v2 API returns UNKNOWN for Software Components – Best practices? in Dynatrace API

Dynatrace v2 API returns UNKNOWN for Software Components – Best practices?