I am certain I am doing something obviously wrong, and hoping a fresh set of eyes will see it right away (since mine are getting bleary looking at this for so long!)

I am trying to configure healthMonitoring to log events to a custom data store via a custom WebEventProvider.  The custom TRIDataWebEventProvider is a subclass of BufferedWebEventProvider, and it seems to be working fine.  Problem is I can only capture a few events.

I can capture: 

1001 application starting
1002 application shutting down
1003 app compilation starting
1004 app compilation is complete
4003 "URL autorization succeeded...

I cannot capture any events related good/bad logins using forms auth with memberhship and login control, page accesses, or anything else. 

I have tried to log *everything* for testing using this configuration: 

     <healthMonitoring enabled="true">   
      <providers>
        <add name="TRIDataWebEventProvider"
            type="TRIApplication.Management.TRIDataWebEventProvider"
            connectionStringName="LocalTRIDatabase"
            applicationID="1"
            buffer="false"
            bufferMode=""  />
      </providers>
      <rules>
        <clear/>
        <add name="Log them all!"
             eventName="All Events"
             provider="TRIDataWebEventProvider"
             profile="Critical"
             minInstances="1"
             maxLimit="Infinite"
             minInterval="00:00:00"              
             custom="" />
      </rules>
    </healthMonitoring>

I am hoping I am making some silly mistake, I misunderstand how this is supposed to work, etc.  As usual, it seems like the answer is somewhere I am not even looking.

Any ideas would be appreciated

   -t
 

 

 

 

Aaargh.

I am using a custom MembershipProvider, and apparently I am responsible for creating and firing healthMonitoring events in the ValidateUser method.  Not sure if this is the intended solution, but at least it works after I added the code to do it this way.

No examples or documentation I can find make any mention of this requirement. 

Of course that explains why no events had been firing for login success and failure.  My, what a PITA
 

BTW... it would be cool if someone could confirm or deny that this solution (creating and firing WebAuthenticationFailureAuditEvent or WebAuthenticationSuccessAuditEvent healthMonitoring events in the ValidateUser() method of a custom MembershipProvider) is the expected or technique?  I don't see any [Attributes] I have missed and it is not possible to call the base method for ValidateUser so I don't see any other way to provide these healthMonitoring events.

In light of the fact that nothing like this is mentioned in the documentation, it seems like a pretty flakey way to do this sort of thing.  And this issue will come up with each and every developer who uses a custom MembershipProvider with HealthMonitoring providers.

thanks,
    -t