StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15710700
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-03-29T20:09:38.760
FavoriteCount
0
LastActivityDate
2013-03-29T20:09:38.760
LastEditDate
LastEditorUserId
0
OwnerUserId
125439
ParentId
15228108
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I think those concepts (Activity and LogicalOperation) are orthogonal. You could have an Activity that has many LogicalOperations inside. Or, you could have a LogicalOperation where the Activity could change. I would guess it would be more common that the Activity is at a higher level than the LogicalOperation. It is probably not very helpful of me to say so, but it is up to you do decide what makes most sense to you and your application as far as organizing your logging. I suspect that it would be common to have a single request result in a single Activity. You might find it helpful to have helper classes to make it easier to manage the Activity and LogicalOperation. Something like this: <pre><code>class ActivityScope : IDisposable { Guid oldActivity; ActivityScope() { oldActivity = System.Diagnostics.CorrelationManager.ActivityId; System.Diagnostics.CorrelationManager.ActivityId = Guid.NewGuid(); } public void Dispose() { System.Diagnostics.CorrelationManager.ActivityId = oldActivity; } } class LogicalOperationScope : IDisposable { public LogicalOperationScope(string logicalOperation) { System.Diagnostics.CorrelationManager.StartLogicalOperation(logicalOperation); } public void Dispose() { System.Diagnostics.CorrelationManager.StopLogicalOperation(); } } </code></pre> You can use them like this: <pre><code>void ServiceARequest() { using (new ActivityScope()) { //Do some stuff using (new LogicalOperationScope("SomeWork")) { DoSomeWork(); for (int i = 0; i < 10; i++) { using (new LogicalOperationScope(string.Format("nested {0}", i)) { DoNestedWork(i); } } } } } void DoSomeWork() { using (new LogicalOperationScope("DoSomeWork")) { } } void DoNestedWork(int level) { } </code></pre> Obviously my example is heavy on diagnostic code and light on real code, but you get the idea. If it makes sense to you to have an ActivityId or a LogicalOperation, try managing them with "scope" classes similar to this. Good luck!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POGranularity of Activity scope when tracing using system.diagnostics server side
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USwageoghe
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.