-
Notifications
You must be signed in to change notification settings - Fork 121
Add support for Asp.net triggers #884
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.
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
Conversation
kelltrick
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
| return _eventPipeTriggerFactory.Create(endpointInfo, aspnetTriggerSourceConfiguration, _traceEventTriggerFactory, settings, callback); | ||
| } | ||
|
|
||
| private static StatusCodeRange ParseRange(string range) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is a good start but I imagine we may want to expand this syntax to support something like: 200,202-204
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Each item in the StatusCodes property above represents either a single code or a code range. An individual item should not have a combination of them. So this is permissable:
[ "200", "202-204" ]but not:
[ "200,202-204" ]There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will leave it as is for now, but if there's strong favor for having the payload be one string I can change it.
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
6916c7f to
e29a058
Compare
Depends on dotnet/diagnostics#2592