Skip to content

[Obsolete] FabricObserver 3.1.8, ClusterObserver 2.1.6, FabricObserverWebApi 2.0.1 - Update ASAP
Compare
Choose a tag to compare
@GitTorre GitTorre released this 07 Apr 01:31
41168093
84e73a4
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

FabricObserver 3.1.8, ClusterObserver 2.1.6, FabricObserverWebApi 2.0.1- sfpkgs with Microsoft-signed binaries. Nupkgs (FO, CO) are located in the nuget.org package gallery.

Changes

FabricObserver 3.1.8 - Update ASAP.

  • Important Bug fix in Application Parameter Update logic.

  • Bug fix in WindowsCpuUtilizationProvider.

  • ApplicationManifest and Settings files have updated Parameters.

  • New TelemetryData member: ProcessId.

  • Updated health event clearing code when FO exits (gracefully) or parameters are updated.

  • CSV Data logging update: Support for multiple file output (time stamped files created per observer run.) Only AppObs, FSO and NodeObs support CSV logging. The default write behavior has not changed to not break existing usage. See Settings.xml for comments. This feature (writing CSV files) can be turned on/off via application parameter updates.

  • Log lifetime management: FO will prune old log files based on configured lifetime (see Settings.xml, ObserverManagerConfiguration section).

  • Fixed bugs in port monitoring logic. It is now much more accurate on Windows.

  • FO will only locally log Health Report data if EnableVerboseLogging is enabled or the FOWebApi app is deployed. It is best to only turn on verbose logging while debugging. You do not need to eat unnecessary disk in production. Just emit telemetry or read from the SF Health Event Store to get details about some warning that you want to handle. The HeatlthEvent.HealthInformation.Description property of any health event FO generates will always be a serialized (JSON) TelemetryData instance.

  • Updated default monitor durations (decreased values).

  • General code maintenance.

NOTE: There is a known issue with ETW where you will see EventSource errors in ETW data that look like this:

ERROR: Exception in Command Processing for EventSource FabricObserverETWProvider:
An instance of EventSource with Guid 0012c99c-680d-5235-03c3-7d3d6e193767 already exists.

This does not break ETW data transmission and will be fixed in 3.1.9. Again, this does not break ObserverLogger.LogEtw function nor is the exception bubbled up to FO process. This is an FYI.

ClusterObserver 2.1.6 - Requires FO 3.1.8 - If you use this service, update ASAP.

Important Bug fixes and added support for FO 3.1.8 (TelemetryData).

FabricObserverWebApi 2.0.1 - If you use this service, update ASAP.

  • Bug fixes.
  • Support for FO 3.1.8.
Assets 14
Loading