Logging Extensions
Перейти к файлу
Spring Operator 779bd6f2f6 URL Cleanup (#9)
This commit updates URLs to prefer the https protocol. Redirects are not followed to avoid accidentally expanding intentionally shortened URLs (i.e. if using a URL shortener).

# Fixed URLs

## Fixed Success
These URLs were switched to an https URL with a 2xx status. While the status was successful, your review is still recommended.

* [ ] http://www.apache.org/licenses/ with 2 occurrences migrated to:
  https://www.apache.org/licenses/ ([https](https://www.apache.org/licenses/) result 200).
* [ ] http://www.apache.org/licenses/LICENSE-2.0 with 55 occurrences migrated to:
  https://www.apache.org/licenses/LICENSE-2.0 ([https](https://www.apache.org/licenses/LICENSE-2.0) result 200).
2019-03-26 17:12:38 -05:00
config update versions 2018-03-07 14:18:19 -06:00
scripts update versions 2018-03-07 14:18:19 -06:00
src/Steeltoe.Extensions.Logging.DynamicLogger URL Cleanup (#9) 2019-03-26 17:12:38 -05:00
test/Steeltoe.Extensions.Logging.DynamicLogger.Test URL Cleanup (#9) 2019-03-26 17:12:38 -05:00
.gitattributes Initial checkin 2017-08-07 06:20:12 -06:00
.gitignore Initial checkin 2017-08-07 06:20:12 -06:00
.travis.yml Add Stylecop 2017-12-15 09:01:34 -07:00
CONTRIBUTING.md Create CONTRIBUTING.md 2017-09-15 14:38:51 -04:00
LICENSE URL Cleanup (#9) 2019-03-26 17:12:38 -05:00
Logging.sln add ILoggingBuilder.SetMinimumLevel(LogLevel.Trace) so that we can get Debug and Trace level logs at runtime without setting the minimum in every app. Name change to DynamicLogger as this is not Cloud Foundry specific 2017-11-02 18:12:00 -05:00
README.md URL Cleanup (#14) 2019-03-26 17:10:59 -05:00
appveyor.yml update versions 2018-03-07 14:18:19 -06:00
nuget.config Initial checkin 2017-08-07 06:20:12 -06:00
open_source_licenses.txt URL Cleanup (#9) 2019-03-26 17:12:38 -05:00
stylecop.json Add and enforce Stylecop, use RTM version of XUnit 2017-10-23 14:39:58 -05:00
versions.props Initial checkin 2017-08-07 06:20:12 -06:00

README.md

.NET Logging Extensions

This repo contains a Logging extension that when used with the Steeltoe Management Logger Endpoint enables changing the Logging levels for a running application dynamically using the Pivotal Apps manager console.

This logger is simply a wrapper around the Microsoft Console logger, but enables querying and dynamically changing the logging levels of all the currently active loggers.

Windows Master (Stable): AppVeyor Master

Windows Dev (Less Stable): AppVeyor Dev

Linux/OS X Master (Stable): Travis Master

Linux/OS X Dev (Less Stable): Travis Dev

.NET Runtime & Framework Support

Like the ASP.NET Core Logging providers, these providers are intended to support both .NET 4.6+ and .NET Core (CoreCLR/CoreFX) run-times. The providers are built and unit tested on Windows, Linux and OSX.

While the primary usage of the providers is intended to be with ASP.NET Core applications, they should also work fine with UWP, Console and ASP.NET 4.x apps.

Currently all of the code and samples have been tested on .NET Core 1.1, .NET 4.6.x, and on ASP.NET Core 1.1.0.

Usage

See the Steeltoe documentation for information on how to use these components in your applications.

Nuget Feeds

All new configuration provider development is done on the dev branch. More stable versions of the providers can be found on the master branch. The latest prebuilt packages from each branch can be found on one of two MyGet feeds. Released version can be found on nuget.org.

Development feed (Less Stable) - https://www.myget.org/gallery/steeltoedev

Master feed (Stable) - https://www.myget.org/gallery/steeltoemaster

Release or Release Candidate feed - https://www.nuget.org/.

Building Pre-requisites

To build and run the unit tests:

  1. .NET Core SDK

Building Packages & Running Tests - Windows

To build the packages on windows:

  1. git clone ...
  2. cd clone directory
  3. Install .NET Core SDK
  4. dotnet restore src
  5. cd src<project> (e.g. cd src\Steeltoe.Extensions.Logging.CloudFoundry)
  6. dotnet pack --configuration Release or Debug

The resulting artifacts can be found in the bin folder under the corresponding project. (e.g. src\Steeltoe.Extensions.Logging.CloudFoundry\bin

To run the unit tests:

  1. git clone ...
  2. cd clone directory
  3. Install .NET Core SDK
  4. dotnet restore test
  5. cd test<test project> (e.g. cd test\Steeltoe.Extensions.Logging.CloudFoundry.Test)
  6. dotnet xunit -verbose

Building Packages & Running Tests - Linux/OSX

To build the packages on Linux/OSX:

  1. git clone ...
  2. cd clone directory
  3. Install .NET Core SDK
  4. dotnet restore src
  5. cd src/ (e.g.. cd src/Steeltoe.Extensions.Logging.CloudFoundry)
  6. dotnet pack --configuration Release or Debug

The resulting artifacts can be found in the bin folder under the corresponding project. (e.g. src/Steeltoe.Extensions.Logging.CloudFoundry/bin

To run the unit tests:

  1. git clone ...
  2. cd clone directory
  3. Install .NET Core SDK
  4. dotnet restore test
  5. cd test<test project> (e.g. cd test/Steeltoe.Extensions.Logging.CloudFoundry.Test)
  6. dotnet xunit -verbose -framework netcoreapp2.0

Sample Applications

See the Samples repo for examples of how to use these packages.