Dear all,

I am currently developing a new application agent for Oracle databases and need some guidance on how to implement it properly.

My first goal is to get the current and historical usage of each tablespace – a DB consists of multiple tablespaces.

This would give a good overview of data growth inside a database.

My application agent running on my DB is polling the data via SQL and returning it to observium as comma spaced values.

The output looks as follows:

CIT;600;596.63

COMPASS;28488;1406.5

COMPASS_IDX;27996;1568.06

CONFIG;1000;959.69

CONTROLLING;600;596.69

CSR;40960;4966

Now I’m almost at my question.

All existing application agents I know are rather static, containing only certain fixed (and hard coded) entities.

Tablespaces are much like storage in my point of view so I think it would be a good idea to implement them as a new storage-type in the storage table of the observium database.

Is this a proper way to do it or do you suggest a different approach?

I’d like to be as compatible as possible to future updates and would also contribute my code if anyone needs it.

Please let me know your thoughts.

Thanks and kind regards,

Philipp