I'm trying to make a copy of all alarms into an external database (SQL Express for now, eventually MySQL). I have reviewed all the documentation that I can find, but still can't figure out the proper names of all the variables that I can move to my new database.
I have most of the columns, but some still come up as "NULL". Where can I find a list of variable names that would work in an adogtw subscribe profile?
My datafile looks like this (the columns in red come out as NULL):
What do you mean they "come out as NULL"? Do you mean the data contains NULL values in those columns? That is normal for many columns.
If you are using SQL (Express or otherwise) anyway, you should be able to just use the same column properties as the NIS database (assuming you have the NIS bridge enabled, which I believe is default when you install the UMP).
Thanks for your comment. I appreciate the help, but I'm still missing something.
I've built a second table and modeled it on the NAS_ALARMS table in the NimsoftSLM database. I am subscribing to all "alarm" messages and am getting data. Some of the columns have correct data compared to the NAS_ALARMS table for the row with the same nimid) but many columns contain "NULL" - time_origin, time_arrival, hostname, nas, etc.
I think I'm getting close, since there are some columns with correct data, but I'd like to get everything that I can. I believe that the $variables in the adogtw profile are based on column names, and I suspect that some of them don't match up.
I'm really looking for a list of the $variables available in adogtw profiles so I can do some more testing and comparison.
I think I have a better understanding of your issue now. Some of the values in the database are determined by the NAS and do not come from the alarm messages on the bus. The only way to get them will be to request them from the NAS or query from the NAS_ALARMS table in the database.
If you build your table from alarm messages on the bus, there are lots of things that will be different from the entries in the NAS_ALARMS table. Some that come to mind include:
Depending on what you are trying to do, some of these differences may be very big deals. Maybe we need to take a step back. What are you trying to accomplish? What is the purpose of having this information in another table or database?
Let me get a better definition of what we're trying to accomplish (in this case I'm just the messenger).
Thanks for your explanation. Is there anywhere that I can find out what's available on the bus?
The best way to see what is in the messages is to go directly to the bus and check yourself. The DrNimBUS (or DrNimsoft) utility lets you capture specific messages from the bus and display them in a GUI. Different alarms may contain slightly different fields, but most will have a lot of the same information.
I've tried that, and will review it again. I will also investigate using the NiS-provided files instead of making an external copy. I believe that most of what we need is there.