ab365cd322
* Expose core error logger to plugins and report custom criteria errors Fixes #77 This adds an error logging method on the IObservatoryCore interface that writes the exception details to ObservatoryCore's central error log (found in `${Documents}/ObservatoryErrorLog.txt`). In addition, added a timestamp to each error log. Also updates the Explorer to report Custom Criteria file load errors and execution errors to the log. Also updates HeraldNotifier to report CacheIndex.json parse failures to the error log as well. * Expand debugging/error logging in Herald; cleanup empty mp3 files Herald crashes if attempting to play 0-byte mp3s so if detected, delete, re-request (empty files can occur in some azure failure cases (ie. out of quota). Trap and log errors in other places in HeraldQueue to avoid hard crashes due to weird and wonderful unexpected stuff.
Elite Observatory Core
Tool for reading/monitoring Elite Dangerous journals for interesting objects. Successor to the original Elite Observatory, rewritten from scratch using .NET 5.0 and AvaloniaUI.
IMPORTANT
Observatory Core and it's associated plugins are currently in an alpha state and are neither feature-complete nor using a finalised UI. Over the coming weeks I will outline in detail what functionality is missing but still planned, and begin work on getting it to feature parity with the original Elite Observatory.
Omissions to current functionality include:
- Integration with Frontier's Companion API
- Data submission to IGAU
- More that I'm just not thinking of right now
How To Use
Observatory Core differs from the original Elite Observatory in that it is a fully generic reader for the Elite Dangerous journal files, passing those events along to plugins to do the actual work.
Observatory will attempt to locate your Elite Dangerous journal location in its default location, though other locations can be specified from the settings in the "Core" application tab. Due to the variety of possible system configurations this automatic detection does not function under Linux, so all Linux users will need to browse for the correct location.
The "Read All" button will read all journal files in the specified folder, handing their contents over to all loaded worker plugins. "Start Monitor" will begin watching files in the journal folder for changes, and pass new journal lines as they are created, as well as all changes to the status.json file, over to the worker plugins.
In addition to updating the content of their respective UI tabs, some workers can also send notifications, which will be distributed to all notifier plugins, as well as be passed to Observatory Core's native notification popup.
For specifics on what each plugin does, please refer to their respective wiki pages:
If you're interested in Custom Criteria for Explorer in particular you can find the documentation for writing them in the project wiki.
If you want to chat or collaborate with other users of Observatory you can find us either in the Elite Dangerous forum thread for Observatory, or on the Elite Observatory Discord.
For information on how to create a plugin, refer to this article about ObservatoryFramework.
Prerequisites for use
.NET 5, and by extension one of its supported OSes.
Prerequisites for building
C# 9.0, .NET 5.0, AvaloniaUI 0.10.3, and of course ObservatoryFramework.