Logging (not great)

RLJB

I have to say I find logging not very useful, 3 simple improvements would assist:

Ability to have logging for a specific Business Space.

We have (as I am sure many users do) about 30+ business spaces on our dev server. Having all logging in 1 file/screen is hopeless.

Ability to not show background process in the logging.

If you have a process running every 15 seconds and this is multiplied by the number of business spaces your whole log is filled up with background processes. Good luck finding your rule misfire.

Ability to write it to a proper .txt file so you can open it and search it.

The best you can do now is:

open the console
run your process
drop your cursor in the console window and quickly hit Ctrl+A to select all and then copy and paste it into a text editor to read. Hopefully you do this before the next background process runs and all your selection is lost.
you then get 11,000 lines to scroll through (love those background processes)

RocketRod

Agree!!

have the same issues with background processes mucking up trying to view and analyze logs.

Cheers Rod

aware_support

Regarding 1 and 3. You can redirect logging to a file in the logger settings. This is a proper text file that can be searched. If you look at this file you will see that each record has the name of the business space next to it.

You can also control the format of the info written into the log in the file AwareIM/bin/logger.props. By default the info written into the log viewer does not include the name of the business space, but the info written to a file does. You can easily change this to see the name of the business space in the logger.

There is also Log Management menu command that allows you to view log of a particular user only.

There is also a bug that puts timer events into the standard log, whereas it should be in the special timer log. This bug will be fixed in the next build.

aware_support

In build 1714 timer messages are no longer written into the main log

RLJB

Thanks support, that sounds great. Where do we get instructions re the logging and how to control it? Is it in the user guide?

aware_support

We use a popular Apache log4j package. You can go to their web site and read the documentation. This is what you need to do in the logger.props file

Rennur

Support,

Can you please also remove the background processes from the log viewer

VP > General > Run Background Process

Cannot analyse the log as this overwrites everything.

Cheers

hpl123

A better idea I think is to give us options. One idea is to create a 4th option called "Custom" we could customize down to each log event and then change "Full" so it has all events (if I remember correctly it doesn´t cover absolutely everything today?).

Thanks

RLJB

Aware Control Panel > Settings > Logging tab > "Log to file..."

How does this work? Has anyone set this up properly?

I was hoping to be able to "turn on" logging and have it dumped to a .txt file that I could then read over time. So I don't need to sit there and watch it happen in the log viewer. But I can't find an output file anywhere. Is that possible? And how?

For example, we have issues late at night, I would like to turn it on at 11pm and off again at 6am and then be able to review it in a big text file in the morning. Sometimes we have a crash in the middle of the night and I would like to know what was happening just before this happened.

hpl123

I would also be interested in knowing how to do this.

crisg0112

RLJB wrote
Aware Control Panel > Settings > Logging tab > "Log to file..."

How does this work? Has anyone set this up properly?

I was hoping to be able to "turn on" logging and have it dumped to a .txt file that I could then read over time. So I don't need to sit there and watch it happen in the log viewer. But I can't find an output file anywhere. Is that possible? And how?

For example, we have issues late at night, I would like to turn it on at 11pm and off again at 6am and then be able to review it in a big text file in the morning. Sometimes we have a crash in the middle of the night and I would like to know what was happening just before this happened.

Hi RJLB,

The file gets written into the C:\AwareIM\bin folder. It's called "test.log" for the first time. if you turn it off and run it again, it gets a filename of "test.log.1". Is this what you're after?

That's what I've noticed on ours .. and then I just use Notepad++ to query the file as it has an ability to find keywords on ALL OPENED DOCUMENTS.

Hope this helps!

crisg0112

my mistake.

The reason it is creating the test.log.1 file is because the test.log file has reached its maximum file size limit.

If you open up your logger.props, you will see all the options you want in there 🙂

RLJB

Thanks Chris - that did help, I couldn't figure out what is happening... still can't really, but I'm closer!

There seems to be 3 main files:

test.log
system.log
main.log

For prod environ, it seems like rule stuff goes into main.log, other system notes go into system.log (?)

I have main.log working well. I HAD system.log working for a bit (stuff getting written to there) but now it has stopped, nothing is getting written to it, can't seem to turn it on?

logger.props > looks fun, anyone have any tips on how to use it?

crisg0112

RLJB wrote
Thanks Chris - that did help, I couldn't figure out what is happening... still can't really, but I'm closer!

There seems to be 3 main files:

test.log
system.log
main.log

For prod environ, it seems like rule stuff goes into main.log, other system notes go into system.log (?)

I have main.log working well. I HAD system.log working for a bit (stuff getting written to there) but now it has stopped, nothing is getting written to it, can't seem to turn it on?

logger.props > looks fun, anyone have any tips on how to use it?

i've only played around with it a bit as i had to do the same with medicare before;
#log4j.appender.A2.layout.ConversionPattern=%d{ISO8601} %-5p Cat[%c] NDC[%x] - %m%n