HeartbeatPlugin ignores heartbeat intervals with a seconds component under 30 (uses TimeSpan.Seconds instead of TotalSeconds) #387

In Exceptionless 6.2.0 (core Exceptionless package), HeartbeatPlugin validates the configured interval with interval.Value.Seconds >= 30. TimeSpan.Seconds is only the 0-59 seconds component, so most whole-minute intervals are rejected and silently replaced with the 1 minute default.

Where

• Exceptionless.Net/src/Exceptionless/Plugins/Default/100_HeartbeatPlugin.cs

  Lines 16 to 18 in 5792f00

  	public HeartbeatPlugin(TimeSpan? interval = null) {
  	_interval = interval.HasValue && interval.Value.Seconds >= 30 ? interval.Value : TimeSpan.FromMinutes(1);
  	}

• Exceptionless.Net/src/Exceptionless/Extensions/ExceptionlessConfigurationExtensions.cs

  Lines 111 to 121 in 5792f00

  	public static void UseSessions(this ExceptionlessConfiguration config, bool sendHeartbeats = true, TimeSpan? heartbeatInterval = null, bool useSessionIdManagement = false) {
  	config.SessionsEnabled = true;
  	if (useSessionIdManagement)
  	config.AddPlugin<SessionIdManagementPlugin>();
  	if (sendHeartbeats)
  	config.AddPlugin(new HeartbeatPlugin(heartbeatInterval));
  	else
  	config.RemovePlugin<HeartbeatPlugin>();
  	}

  (UseSessions(heartbeatInterval: ...) passes the value through)

What happens

Any interval that is a whole number of minutes falls back to 1 minute, so config.UseSessions(heartbeatInterval: TimeSpan.FromMinutes(5)) sends heartbeats every minute instead of every 5 minutes.

Expected

Intervals of 30 seconds or more are honored; only intervals under 30 seconds fall back to the default.

With the 6.2.0 package, new HeartbeatPlugin(TimeSpan.FromMinutes(5)) stores an interval of 00:01:00, while new HeartbeatPlugin(TimeSpan.FromSeconds(90)) stores 00:01:30.

Steps to reproduce

1. config.UseSessions(heartbeatInterval: TimeSpan.FromMinutes(5));
2. Set a user identity and submit an event to start a session.
3. Session heartbeat events are sent every minute, not every 5 minutes.

Suggested fix

Use interval.Value.TotalSeconds >= 30 (or interval.Value >= TimeSpan.FromSeconds(30)).