Skip to content

v3.5.0
Compare
Choose a tag to compare
@niemyjski niemyjski released this 10 May 20:08
v3.5.0
94897b0

Version 3.5.0 focused on improvements to sessions, real time configuration and logging.

  • Added the ability to exclude events by type and source in real time as well as minimum log levels! We've made improvements to real time project configuration to ensure that if you accidentally disable logging completely, your settings can be updated in the background and functionality restored! We will expand on UI support for this in the near future, in the mean time please check out the example project configuration below:
    • Key: @@EVENT_TYPE:SOURCE Value: false You can use any event type or source. We support using wildcards * as part of the source. If you want to ignore complete event types then set the source to *.
    • Key: @@error:*MyCustomException Value: false The following disables the submission of any error event where the stack trace contains an exception with a type name that ends with MyCustomException. You can also specify the full type name with namespace and remove the wildcard.
    • Key: @@log:* Value: Off Log types are special cased but still accept true or false for values. This example will turn off log messages completely. Known values are: Trace, Debug, Info, Warn, Error, Fatal, Off.
    • Key: @@log:MyNamespace.EventPostsJob Value: Info This sets a minimum log level for the EventPostsJob.
  • Added support for automatically checking for updated configuration settings when the client is idle. By default the client will now check every 2 minutes after the last event submission for updated configuration settings. You can also turn off the automatic updating of configuration settings when idle by calling client.Configuration.UpdateSettingsWhenIdleInterval = TimeSpan.Zero;.
    • Checking for updated settings doesn't count towards plan limits.
    • Only the current configuration version is sent when checking for updated settings (no user information will ever be sent).
    • If the settings haven't changed, then no settings will be retrieved.
  • Session Heartbeats and Session End events are now sent through an optimized api end point. This means that they no longer count towards your plan limits!
  • Added an easy way to exclude events from being submitted via by defining a simple Func<Event, bool> callback. The following example ignores any event that has has a value property of 2 client.Configuration.AddEventExclusion(e => e.Value.GetValueOrDefault() != 2);
  • Fixed a bug where SettingsCollection.GetBoolean(name) didn't support parsing 0 or 1 as boolean values (#88). We also now support yes and no as valid boolean values.

Please take a look at the change log for a full list of the changes.

Feedback

We're listening and we'd love to hear your feedback! Please send us your feedback by clicking on one of the links below!

Assets 40
Loading