Update report-http.md

[cadirol]

Hy!
Great work with BGPalerter!
i like to update the report documentation with a RocketChat Http Request
Cheers

[massimocandela]

Thanks for this contribution. I changed the PR to be merged in dev.

I have some remarks (1 is the most important):

1. Are you sure the "payload=" part should be there? If I look at the documentation it looks like a JSON post body should be enough. Could you please verify that the example you provided works exactly as is (except for user-specific params). Be aware, the initial ' wrapping the payload is not closed. Please, if a string and a JSON post body are available, prefer the JSON one.
2. Can you describe the role of the "channel" key?
3. Are you ok with me adding "Thanks to @cadirol" at the bottom of the example?

Thanks

[cadirol]

Hi To your points: 1. To be honest, it is working on both ways: This way it seems to be fine as well! ----------------- %< -----------------     params:       templates:         default: '{"username": "BGPalerter ${channel}", "channel": "#BGPalerter", "text": "Channel: *${channel}* Type: *${type}* on Prefix *${prefix}* via Peer *${peers}* | Message Summary: ${summary}"}'       headers:       isTemplateJSON: true ----------------- %< ----------------- The trailing ' was lost in my pull request. but of course, it needed! 2. Channel is describe the RocketChat Channel. Users can create Channels as they like. Something like a "Room" 3. Yes of course, would make me proud! :-) Cheers Adrian On Fri. 3. December 2021 16:11 CET, Massimo Candela ***@***.***> wrote:     Thanks for this contribution. I changed the PR to be merged in dev. I have some remarks (1 is the most important): * Are you sure the "payload=" part should be there? If I look at the documentation it looks like a JSON post body should be enough. Could you please verify that the example you provided works exactly as is (except for user-specific params). Be aware, the initial ' wrapping the payload is not closed. Please, if a string and a JSON post body are available, prefer the JSON one. * Can you describe the role of the "channel" key? * Are you ok with me adding "Thanks to @cadirol" at the bottom of the example? Thanks — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

…

-- Adrian Kägi Network Engineer Direct +41 31 517 77 19 | Phone +41 31 517 77 77 NTS Workspace AG colocate lightspeed Wölflistrasse 1d | CH-3006 Bern | www.nts.ch

[massimocandela]

I applied my review. Let me know if you are ok with it and if everything looks fine. Then, I will merge it.

[cadirol]

Seems good! your additional hint for #channel and @user completes the howto