Prism's ILoggerFacade provides logging of all internal Prism errors, and a quick and easy way for your WPF, UWP, or Xamarin Forms app to introduce logging throughout your ViewModels and Services. The implementation of ILoggerFacade is really left to the developer to determine how you want to handle your logging. While this "Works", it is also a more than a decade old definition that doesn't match modern application logging demands. For this reason the Prism Logging Plugins introduce some new logging interfaces:
- IAnalyticsService
- adds
void TrackEvent(string name, IDictionary<string, string> properties)
- adds
- ICrashesService
- adds
void Report(Exception ex, IDictionary<string, string> properties)
- adds
- ILogger (inherits from IAnalyticsService, ICrashesService, ILoggerFacade)
- adds
void Log(string message, IDictionary<string, string> properties) - has extensions for Debug, Info, Warn
- adds
| Package | NuGet | Sponsor Connect |
|---|---|---|
| Prism.Plugin.Logging.Abstractions |  |
 |
| Prism.Plugin.Logging.Common |  |
 |
| Prism.Plugin.Logging.AppCenter |  |
 |
| Prism.Plugin.Logging.AppInsights |  |
 |
| Prism.Plugin.Logging.Graylog |  |
 |
| Prism.Plugin.Logging.Loggly |  |
 |
| Prism.Plugin.Logging.Syslog |  |
 |
If this project helped you reduce time to develop and made your app better, please be sure to Star the project help support Dan.
Logging is an important facet of app development. It can help you identify how users are navigating through your application, alert you when unexcepted exceptions are thrown, and help shorten the Dev-Loop. Note that the sample below show registering the logger with Prism IContainerRegistry as a Transient Service. It is typically advisable to access the underlying container and register a single instance of your logger against any interfaces that may be called by your app.
// For DryIoc it might look something like this:
var container = containerRegistry.GetContainer();
container.RegisterMany<SyslogLogger>(Reuse.Singleton,
ifAlreadyRegistered: IfAlreadyRegistered.Replace,
serviceTypeCondition: t => typeof(SyslogLogger).ImplementsServiceType(t));
// For Unity it might look something like this:
var logger = Container.Resolve<SyslogLogger>();
containerRegistry.RegisterInstance<ILoggerFacade>(logger);
containerRegistry.RegisterInstance<ILogger>(logger);
containerRegistry.RegisterInstance<IAnalyticsService>(logger);
containerRegistry.RegisterInstance<ICrashesService>(logger);
containerRegistry.RegisterInstance<ISyslogLogger>(logger);If you're using the Prism.Container.Extensions you might simply register your logger like:
containerRegistry.RegisterManySingleton<SyslogLogger>();There are times where you may actually want to have multiple logging providers. For instance you may wish to send logs to App Center and the device console at the same time. The Aggregate Logger by default will log to the console, but gives you the ability to explicitly define any loggers that you may wish to use. Note that when you add the first logger it will clear the default Console Logger and you will need to pass in a Console Logger if you wish to continue using the Console Logger as one of the Aggregate Loggers.
protected override void RegisterTypes(IContainerRegistry containerRegistry)
{
containerRegistry.Register<ISyslogOptions, MySyslogOptions>();
containerRegistry.RegisterManySingleton<AggregateLogger>();
}
protected override void OnInitialized()
{
var aggLogger = Container.Resolve<IAggregateLogger>();
aggLogger.AddLoggers(
Container.Resolve<ConsoleLoggingService>(),
Container.Resolve<SyslogLogger>()
);
}The App Center and Application Insights packages both make some assumptions that while running a Debug build that the logging output should be sent to the Application Output (the console in the IDE). Simply running a Release build will trigger the logger to attempt to send telemetry using the App Center or Application Insights SDK's
Starting with version 1.2, two new interfaces were added for mocking Analytics and Crashes. While the Report API was previously available in the ILogger, this has been moved to the ICrashesService, with a new IAnalyticsService that exposes a TrackEvent API. Both of these interfaces are implemented through the ILogger. These services map directly App Center Analytics and Crashes API's. This allows you to null logging events you may use during development, while leaving intact specific tracking of events and crashes.
Application Insights requires that you have an Instrumentation Key to create the client. In addition you may pass any root telemetry you wish about your users. This could include the Device type, OS version, etc. You are able to pass both the Instrumentation Key and User Traits to the Application Insights Logger using the IApplicationInsightsOptions. Note that Prism.Forms developers may want implement this on a Platform Specific basis and register this with the IPlatformInitializer.
Both the App Center and Application Insights loggers attempt to make a determination if the build is a Debug build. This is done based on the entry assembly. All Debug builds will automatically write to the Device Console. The Console will also be used if the underlying service is not available. This could occur becuase you failed to start App Center Crashes or Analyics, or provided the wrong client id for either App Center or Application Insights.
The SocketLogger is configurable to send messages using any Socket Type you choose. Typically you would choose Udp or Tcp. This works great for simple solutions where you simply want to receive logging messages over the network.
public class SocketOptions : ISocketLoggerOptions
{
// e.g. 192.168.0.100
// e.g. logging.contoso.com
public string HostOrIp => Secrets.LoggingHost;
public int Port => 12345;
public ProtocolType ProtocolType => ProtocolType.Udp;
}
public class App : PrismApplication
{
protected override void RegisterTypes(IContainerRegistry containerRegistry)
{
containerRegistry.Register<ISocketLoggerOptions, SocketOptions>();
// Resolve the logger as a Transient Service
containerRegistry.Register<ILoggerFacade, SocketLogger>();
containerRegistry.Register<ILogger, SocketLogger>();
}
}The Syslog package will enable you to send your logging messages to the Syslog Server of your choice, and works great with Visual Syslog Server.
public class AwesomeAppOptions : ISyslogOptions
{
// e.g. 192.168.0.100
// e.g. logging.contoso.com
public string HostNameOrIp => Secrets.LoggingHost;
// If this is null, the SyslogLogger will use port 514
public int? Port => int.Parse(Secrets.LoggingPort);
public string AppNameOrTag => "AwesomeApp"
}
public class App : PrismApplication
{
protected override void RegisterTypes(IContainerRegistry containerRegistry)
{
containerRegistry.Register<ISyslogOptions, AwesomeAppOptions>();
// Registers the Syslog Logger as a Transient Service
containerRegistry.Register<ILoggerFacade, SyslogLogger>();
containerRegistry.Register<ILogger, SyslogLogger>();
}
}Loggly offers both free and paid Logging as a Service plans. The Loggly package will allow you to choose from either their Syslog implementation or Rest service.
NOTE By default we will send all requests to logs-01.loggly.com. To override this you will need to inherit from the Logging class.
- For
LogglyHttpLoggeryou will need to overrideLogglyBaseUri's default value ofhttps://logs-01.loggly.com - For
LogglySyslogLoggeryou will need to implement a Logger class that derives fromLogglySyslogLoggerand update theHostNameOrIpproperty.
public class LogglyOptions : ILogglyOptions
{
public string Token => Secrets.LogglyToken;
public string AppName => "AwesomeApp";
public IEnumerable<string> Tags => new string[]
{
"sample"
};
}
public class App : PrismApplication
{
protected override void RegisterTypes(IContainerRegistry containerRegistry)
{
// Used by both the LogglyHttpLogger and LogglySyslogLogger
containerRegistry.Register<ILogglyOptions, LogglyOptions>();
containerRegistry.Register<ILoggerFacade, LogglyHttpLogger>();
// Or
containerRegistry.Register<ILoggerFacade, LogglySyslogLogger>();
}
}Graylog is a very popular Logging platform which will accept Syslog messages. In addition to the Syslog Messages, you can also choose to use the Graylog package to take advantage of the Graylog REST Api and GELF Log Messages.
public class GelfOptions : IGelfOptions
{
// e.g. http://graylog.example.org:12202
public Uri Host => new Uri(Secrets.GraylogHost);
}
public class App : PrismApplication
{
protected override void RegisterTypes(IContainerRegistry containerRegistry)
{
containerRegistry.Register<IGelfOptions, GelfOptions>();
containerRegistry.Register<ILoggerFacade, GelfLogger>();
}
}
![dependabot-preview[bot] avatar](https://avatars.githubusercontent.com/in/2141?v=4 "dependabot-preview[bot]")
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "github-actions[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent