Instead of disabling the monitoring, we could take in account the autoextend option in the usage calculation, if not the case (other issues are opened about this at this time)

Hello,

are there any plans to calculate available tablespace space taking into account autoextend feature ? It seems to be a common source of false alarms problem

Indeed, currently the "Oracle by Zabbix agent 2" monitoring template makes no sense for tablespace "Tablespace usage, percent" item value when "AUTOEXTENSIBLE" value is set to "YES" and the tablespace file automatically grows to "Tablespace MAX size, bytes" item value. Thus for the "Tablespace usage, percent" item instead of current 

Used bytes/Allocated bytes*100 

for "AUTOEXTENSIBLE" set to "YES" tablespaces there should be

Used bytes/MAX bytest*100  

It would be nice if some if/else logic would be added to respect the "AUTOEXTENSIBLE" value for the tablespace.
There is ZBXNEXT-8705, which brought "Tablespace allocated, percent" (Allocated bytes/Max bytes*100) - it is nice, but is a half measure, as you need to manually disable/create disabled the discovery rules' items and trigger prototypes propagated from the template to match your "autoextensible" case. 
Here is the community template that adjusts to "autoextensible" setting: https://github.com/zabbix/community-templates/blob/main/Databases/Oracle/template_oracle_db/6.0/README.md :

when autoextensible = 'YES' then maxbytes  

knaglis  it would be nice if the official Zabbix template had the same logic built in 

asebiskveradze - could you, please, consider adding the corresponding logic to the  "Oracle by Zabbix agent 2" monitoring template so it would take into consideration "autoextend" feature and would not produce false positives on tablespace running out of free space while the actual usage is still far from the "Tablespace MAX size, bytes" ( as Mugugnu also mentioned) ?  Here is the community template, which already has this logic implemented.