Where to find the Log

[Stuart Hemming]

I've enabled logging by adding the following elements to my model's app.config file ...

<backendconfiguration id="mssqlConfiguration" backend="mssql">
  <mappingname>mssqlMapping</mappingname>
  <logging.logEvents>all</logging.logEvents>
  <logging.logEventsToSysOut>true</logging.logEventsToSysOut>
</backendconfiguration>

After running my app, and getting the error I was trying to track down, I started trying to find the log.

I've looked in the EventViewer and I've looked in the Telerik directory.

Where do I find the log?

-- 
Stuart

[Stuart Hemming]

Move along....

There's nothing to see here ...

[PetarP]

Hi Stuart Hemming,

 You can specify the drop location for the log using the following configuration entries:

<backendconfiguration id="mssqlConfiguration" backend="mssql">
       <mappingname>mssqlMapping</mappingname>
       <logging.logEvents>all</logging.logEvents>
       <logging.logEventsToSysOut>True</logging.logEventsToSysOut>
       <logDownloader.filename>C:\output.txt</logDownloader.filename>
       <logDownloader.eventText>True</logDownloader.eventText>
     </backendconfiguration>

I hope this is what you are looking for.

Regards,
Petar
the Telerik team

[Stuart Hemming]

Thanks Petar,

but why doesn't it say that in the docs? What's the value of only documenting only half of the info you need?

Clicking on the only index entry for event logging in the docs takes you to a pages that simply reads "OpenAccess ORM has strong event logging, performance monitoring and tuning features. Events can be generated for nearly all operations executed by the server depending on the configured event logging level. The server maintains more than 50 different performance metrics (counters) monitoring everything from the 2nd level cache hit rate to the number of connections in the connection pool. Events and regular snapshots of all the metrics are stored in ring buffers."

Why anyone thought that that was helpful is beyond me.

-- 
Stuart

[Pencho]

Hello Stuart Hemming,

Yes, you are right, the aforementioned information is not mentioned in the help. Thanks a lot for your remark, it will be evaluated on our side and the corresponding information will be added in the help documentation.
However, in the current version of the documentation there is a information regarding the tracing and logging mechanisms in OpenAccess. For example, the following topic (Programming Guide>OpenAccess ORM Visual Designer>Programming Guide>OpenAccess Tasks>Managing the OpenAccessContext>How to: Trace SQL Statements Generated by OpenAccessContext ) could be usefull for you. It demonstrates how to create a custom trace listener, based on the Telerik.OpenAccess.Diagnostic.TraceAdapter class. Please note, nevertheless the fact that this topic is from the Visual Designer section, it could be used and for the classic version of OpenAccess (reverse/forward mapping).
Just a last note, if you are using the Visual Designer, you could enable the trace & log feature of OpenAccess in a few clicks. In the Model Settings dialog > Backend Settings tab page > Tracing & Loging tab page, just enable the Write Events to Text File option and specify a path in the File Name.
Once again, thanks for the feedback. Making a good documentation is a continued effort - the more feedback we get, the more we improve the documentation.

All the best,
Pencho
the Telerik team

[Stuart Hemming]

> Thanks a lot for your remark, it will be evaluated on our side and the corresponding
> information will be added in the help documentation.
Glad to hear it.

> For example, the following topic (Programming Guide>OpenAccess ORM Visual Designer
> Programming Guide>OpenAccess Tasks>Managing the OpenAccessContext
> How to: Trace SQL Statements Generated by OpenAccessContext )
And well it might. However, that topic isn't offered up when searching the index for "logging" or "event logging" and I think that that is an issue that you have to address.

-- 
Stuart

[Pencho]

Hi Stuart Hemming,

In the next release of Telerik OpenAccess ORM, you can find information regarding the Tracing and Logging features of OpenAccess in the  OpenAccess ORM Visual Designer > Programming Guide > OpenAccess Tasks > Tracing and Logging section. The same will be available in the OpenAccess ORM Classic node too, under the following path: OpenAccess ORM Classic > OpenAccess Tasks > Tracing and Logging.
In regard to the indexing problem, we haven't paid enough attention to that issue until now, but obviously we have to investigate and see how to optimize the search.
Thanks again.

Regards,
Pencho
the Telerik team

[Stuart Hemming]

Pencho, 

thanks for the response.

> In regard to the indexing problem, we haven't paid enough attention to that issue until now,
> but obviously we have to investigate and see how to optimize the search.
I absolutely agree. The index search is prolly the first place the vast majority of user will go when trying to find help on a subject they know little about.

With respect to the next release of ORM, I look forward to seeing it. Are we talking about the Q3 release or the SP for Q2?
-- 
Stuart

[Pencho]

Hello Stuart,

I meant the next service pack for Q2.

Greetings,
Pencho
the Telerik team

[Stuart Hemming]

Hi Pencho,

That's great. Thanks for letting me know.

-- 
Stuart