Added message templating and corrected for Seq v2 #1
Conversation
|
Thanks for your contrib, and sorry for late reply! The way I usually test these is by creating a nuget package using "nuget pack Seq.App.HipChat.nuspec" in the project folder. Then I move the nupkg file to some folder and configure a repository in my local Seq instance. A NuGet feed doesn't need any fancy server software. Just go into Settings->Feeds in Seq and add a new feed pointing to a directory on your disk. Then it's just a matter of installing the app as if it where on nuget.org. |
| var placeholders = data.Properties.ToDictionary(k => k.Key.ToLower(), v => v.Value); | ||
|
|
||
| AddValueIfKeyDoesntExist(placeholders, "EventType", eventType); | ||
| AddValueIfKeyDoesntExist(placeholders, "RenderedMessage", data.RenderedMessage); |
There was a problem hiding this comment.
I see you set some custom properties here, but you never set "Level". Or am I missing something obvious?
There was a problem hiding this comment.
Good spot, I've added it.
Will give it a while in the way you've suggested cheers
|
Have you tested this? Unfortunately not running HipChat anymore so I can't test personally. |
I've fixed the url for the latest build of Seq and have also added the ability to use custom placeholders in the message i.e. so you can include information from the error itself rather than just the message.
I've not worked out how I can test this on Seq itself so this will need testing/validation.