cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Limit of custom topology type entities

rastislav_danis
DynaMight Pro
DynaMight Pro

Oracle DB extension collects data for Backup jobs and creates lot of entities of type Oracle DB Backup Job. Which is nice until you hit this error and backup jobs stops showing in oracle instance screens (and anywhere else).

I'm not able to find any documentation related to this issue (link "learn more" is not working anymore;) ). So i cannot find what is the limit and how to limit/delete created entities.

Has anybody fell into this issue?

rastislav_danis_0-1734435481150.png

 

Alanata a.s.
8 REPLIES 8

jegron
DynaMight Champion
DynaMight Champion

Hi @rastislav_danis !

Never seen this limit. Do you use SaaS ? You could count the number of entities to better understand the limit.

fetch `dt.entity.sql:com_dynatrace_extension_sql-oracle_backup_job`
| fieldsSummary id

Maybe @Mike_L  could help us 🙂

Observability Engineer at Phenisys - Dynatrace Professional

This is Managed and i have fresh info from support:

there is limit for entities (100k in this env) which was hit with data from 30 Oracle instances (backup job featureset enabled) after 2 and half month. Another hidden info is about clean up job, that takes care about such short term entities but in this env it's set to 180 days. So either limit need to be extended or job interval should be shortened.

Any of that will be easier, if Oracle Database extension mentioned this limitations in documentation.

Alanata a.s.

Mike_L
Dynatrace Guru
Dynatrace Guru

If I remember correctly the limit is 100.000 entities of a single type. Either you have quite a few backup jobs, or there is something (semi) unique in them which makes the number of entities explode. I'd go with a support ticket so we can look into it further if I were you.

Mike

Hi @Mike_L , support ticket is open (https://one.dynatrace.com/hc/en-us/requests/418025), i already mentioned info from support here.

Alanata a.s.

This is also strange to me, when i look into topology definition, just Backup job type and DB instance should compose backup job entity id.

Alanata a.s.

What is important is the ID though, and the ID is built up using the following dimensions:

idPattern: sql_sql-oracle_{device}_{device}_{session_recid}_{session_stamp}
I've asked the owner of the extension to have a look at it, and will point support to this thread.

Mike

Thanks, i perform fast but not accurate moves today 😉 that was only name i mentioned, id is different.

Alanata a.s.

You did, I did beat you with 1 minute though 😎

Mike

Featured Posts