Big question. TSM has a lot of data available, and what do you want to do with it exactly? "What problem are you trying to solve, exactly?" is always a good question.
One good simple starting point is the dsmaccnt.log
file. It's a basic CSV of performance and accounting data around every TSM server connection. Lots of good data there, and it's simple to ingest and parse.
Beyond that, there's several good data points inside the TSM database itself, such as the activity log, the summary data, the nodes table, and several other things. In "modern" TSM (V6.1 and above) all of this is stored in DB2, so you might be able to get at it using the DB Connect app pretty easily.
If you aren't deeply familiar with both TSM and Splunk this might be the right kind of job to turn over to Professional Services to help you figure out how to ingest this data.
It is possible to run a scheduled script to collect information from TSM using dsmadmc and SQL and store it in a comma separated file. use a universal forwarder to put this data into splunk and then extract those metrics into a dashboard.
some examples:
DB space
Tape drives in use
Scratch Tapes remaining
Drives offline
Tivoli Storage Manager AIX machines are integrated and OS level logs are ingested in the splunk already , now we are planning get the Application (TSM) to the splunk , for example to get a dashboard report weekly occupancy report .. backup success rate , nodes data ..
Big question. TSM has a lot of data available, and what do you want to do with it exactly? "What problem are you trying to solve, exactly?" is always a good question.
One good simple starting point is the dsmaccnt.log
file. It's a basic CSV of performance and accounting data around every TSM server connection. Lots of good data there, and it's simple to ingest and parse.
Beyond that, there's several good data points inside the TSM database itself, such as the activity log, the summary data, the nodes table, and several other things. In "modern" TSM (V6.1 and above) all of this is stored in DB2, so you might be able to get at it using the DB Connect app pretty easily.
If you aren't deeply familiar with both TSM and Splunk this might be the right kind of job to turn over to Professional Services to help you figure out how to ingest this data.
What is TSM?
You say you are "trying to integrate TSM servers with Splunk" and then "TSM servers are already integrated in the Splunk". Which is it? What EXACTLY are you trying to do and what EXACTLY is already done/working?