"David Keogh [MSFT]" <dkeogh@online.microsoft.com> wrote in message
news:a4J%23h%23YmDHA.1548@cpmsftngxa06.phx.gbl...
> Yes, that's exactly what you can do.
>
> For instance, two bind event sources to two different trace sessions, you
> would have something like this in your event sinks section:
>
> <eventSink name="traceSink" description="Outputs to trace session 1."
> type="Microsoft.EnterpriseInstrumentation.EventSinks.TraceEventSink">
> <parameter name="sessionName" value="TraceSession1" />
> </eventSink>
> <eventSink name="traceSink" description="Outputs to trace session 2."
> type="Microsoft.EnterpriseInstrumentation.EventSinks.TraceEventSink">
> <parameter name="sessionName" value="TraceSession2" />
> </eventSink>
>
> Hope this helps,
> David [MSFT]
>
> --------------------
> | From: "Steve Miller" <stevemi@avanade.com>
> | Subject: EIF event sink configuration.
> | Date: Mon, 20 Oct 2003 22:32:38 -0400
> | Lines: 9
> | X-Priority: 3
> | X-MSMail-Priority: Normal
> | X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
> | Message-ID: <ODGJcu3lDHA.424@TK2MSFTNGP10.phx.gbl>
> | Newsgroups: microsoft.public.vsnet.enterprise.tools
> | NNTP-Posting-Host: reverse.24.x.114.209.idealapps.com 209.114.239.24
> | Path:
>
cpmsftngxa06.phx.gbl!cpmsftngxa09.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP10.
> phx.gbl
> | Xref: cpmsftngxa06.phx.gbl microsoft.public.vsnet.enterprise.tools:1214
> | X-Tomcat-NG: microsoft.public.vsnet.enterprise.tools
> |
> | When you define an event sink in the <EventSinks></EventSinks> section
of
> | the EIF configuration file you have to specifiy the type to be used for
> the
> | event sink. Is it possilbe to use the same type with different event
sink
> | definitions? For instance, I would like to use the same type with
> different
> | parameters and in different event filtering configurations.
> |
> | Steve Miller
> |
> |
> |
>

>From: "Steve Miller" <stevemi@avanade.com>
>References: <ODGJcu3lDHA.424@TK2MSFTNGP10.phx.gbl>
<a4J#h#YmDHA.1548@cpmsftngxa06.phx.gbl>
>Subject: Re: EIF event sink configuration.
>Date: Tue, 18 Nov 2003 09:34:36 -0500
>Lines: 63
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
>Message-ID: <O9cbzEerDHA.2588@tk2msftngp13.phx.gbl>
>Newsgroups: microsoft.public.vsnet.enterprise.tools
>NNTP-Posting-Host: 216.183.179.1
>Path:

>Xref: cpmsftngxa06.phx.gbl microsoft.public.vsnet.enterprise.tools:1418
>X-Tomcat-NG: microsoft.public.vsnet.enterprise.tools
>
>David:
>
>In the example below, should the "name" attribute be different in
><eventSink> element definition? Else how would the EIF know which one to
>use?
>
>sm
>
>"David Keogh [MSFT]" <dkeogh@online.microsoft.com> wrote in message
>news:a4J%23h%23YmDHA.1548@cpmsftngxa06.phx.gbl...
>> Yes, that's exactly what you can do.
>>
>> For instance, two bind event sources to two different trace sessions, you
>> would have something like this in your event sinks section:
>>
>> <eventSink name="traceSink" description="Outputs to trace session 1."
>> type="Microsoft.EnterpriseInstrumentation.EventSinks.TraceEventSink">
>> <parameter name="sessionName" value="TraceSession1" />
>> </eventSink>
>> <eventSink name="traceSink" description="Outputs to trace session 2."
>> type="Microsoft.EnterpriseInstrumentation.EventSinks.TraceEventSink">
>> <parameter name="sessionName" value="TraceSession2" />
>> </eventSink>
>>
>> Hope this helps,
>> David [MSFT]
>>
>> --------------------
>> | From: "Steve Miller" <stevemi@avanade.com>
>> | Subject: EIF event sink configuration.
>> | Date: Mon, 20 Oct 2003 22:32:38 -0400
>> | Lines: 9
>> | X-Priority: 3
>> | X-MSMail-Priority: Normal
>> | X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
>> | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
>> | Message-ID: <ODGJcu3lDHA.424@TK2MSFTNGP10.phx.gbl>
>> | Newsgroups: microsoft.public.vsnet.enterprise.tools
>> | NNTP-Posting-Host: reverse.24.x.114.209.idealapps.com 209.114.239.24
>> | Path:
>>