Export or email memory usage

[ravi]

Hi All,

We are currently monitoring the tm1 server memory usage for our tm1 model.
In this regard, I would like to have tm1 cube memory size and dimension size and data directory size etc.....
generated in CSV file or email alerts to know current memory usage in tm1 model in server.
Currently memory size of cubes and dim- I am manually checking it in tm1 perspective server explorer to know memory usage.

Is there way you can suggest to write IT proces.......?

Thanks and Regards,
Ravi

[declanr]

Hi All,

We are currently monitoring the tm1 server memory usage for our tm1 model.
In this regard, I would like to have tm1 cube memory size and dimension size and data directory size etc.....
generated in CSV file or email alerts to know current memory usage in tm1 model in server.
Currently memory size of cubes and dim- I am manually checking it in tm1 perspective server explorer to know memory usage.

Is there way you can suggest to write IT proces.......?

Thanks and Regards,
Ravi

As long as you already know which cubes the data you wish to view is held in why can't you just use asciioutput to create your CSV file within a TI and then something like sendemail.exe within another TI (described extensively on this forum) to pick up that CSV file and send it as an attachment?

If there is a specific part of the process you are struggling with, then I'm sure we will be able to point you in the right direction.

[Darkhorse]

Do you have an email system pearl script configured to use Ravi?

[PlanningDev]

If you don't want to create your own take a look at Blat.exe command line smtp emailer.

It takes care of attachments, HTML emails, etc. super easy to use. We built a standard process for sending emails. That intakes parameters and builds the command line call dynamically so anyone can send emails from TM1.

[macsir]

I think gathering server physical memory uasge info is more practical to prevent server crash. As long as your cubes can live with current server's memory, it is meanless to check them all the time. Unless you use up all your server memory, it is time to re-order or clean up tm1 objects.