Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use Serilog for sending telemetry #29

Closed
6 tasks done
tomkerkhove opened this issue Mar 22, 2018 · 1 comment · Fixed by #718
Closed
6 tasks done

Use Serilog for sending telemetry #29

tomkerkhove opened this issue Mar 22, 2018 · 1 comment · Fixed by #718
Assignees
@tomkerkhove
Labels
help-wanted All issues where people can contribute to the project operations All issues related to operations specs-defined All issues where the specifications are defined and ready to be implemented
Milestone
v1.1.0

Comments

@tomkerkhove
Copy link
Owner

tomkerkhove commented Mar 22, 2018 •
edited
Loading

All telemetry should be written via Serilog so we can use a variety of sinks.

Part of #11.

Specifications

  • Send exception information
  • Send general tracing information
  • Provide individual feature flags to control what is being sent
  • Document how to configure this

Supported Sinks

  • Console (on by default)
  • Application Insights (opt-in)
@tomkerkhove tomkerkhove added the operations All issues related to operations label Mar 22, 2018
@tomkerkhove tomkerkhove added this to the v1.1 milestone Mar 22, 2018
@tomkerkhove tomkerkhove mentioned this issue Mar 22, 2018
Closed
1 task
@tomkerkhove tomkerkhove added the help-wanted All issues where people can contribute to the project label Apr 2, 2018
@tomkerkhove tomkerkhove modified the milestones: v1.1, v1 May 26, 2018
@tomkerkhove tomkerkhove modified the milestones: v1, v1.1 Jun 18, 2018
@tomkerkhove tomkerkhove mentioned this issue Jun 18, 2018
Closed
4 tasks
@tomkerkhove tomkerkhove removed this from the vNext milestone Aug 18, 2018
@tomkerkhove tomkerkhove mentioned this issue Oct 22, 2018
Closed
@tomkerkhove tomkerkhove added this to the v1.1.0 milestone Feb 3, 2019
@tomkerkhove tomkerkhove added the specs-required All issues where the specifications are still being defined and implementation should be halted label Mar 11, 2019
@tomkerkhove
Copy link
Owner Author

We need to check how much we'll rely on Serilog over default .NET Configuration approach

@tomkerkhove tomkerkhove modified the milestones: v1.1.0, v1.2.0 Apr 9, 2019
@tomkerkhove tomkerkhove modified the milestones: v1.2.0, v1.1.0 Nov 30, 2019
@tomkerkhove tomkerkhove added specs-defined All issues where the specifications are defined and ready to be implemented and removed specs-required All issues where the specifications are still being defined and implementation should be halted labels Nov 30, 2019
@tomkerkhove tomkerkhove self-assigned this Nov 30, 2019
@tomkerkhove tomkerkhove mentioned this issue Dec 2, 2019
Merged
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@tomkerkhove tomkerkhove

Labels
help-wanted All issues where people can contribute to the project operations All issues related to operations specs-defined All issues where the specifications are defined and ready to be implemented
Projects
None yet
Milestone
v1.1.0
Development

Successfully merging a pull request may close this issue.

Migrate to .NET Core 3.1 tomkerkhove/promitor
1 participant
@tomkerkhove