* Add Headers and body
add PUT Method
* fix check length of headers
* bad commit
* style check
* better body description
* Descr and RFC enforcement on 'PUT' and body
Only PUT can accept a statically defined body. GET will ignore it (RFC) and POST body is generated with the parameters.
* Process the variables as well for headers
* Update Api.php
* update docs
* Catch exceptions generated by alert transports
The alert.php script would completely die if a single alert
transport generated an exception. For example the API transport
if CURL couldn't connect to the api endpoint. The script
should attempt to send alerts to all working transports and not
die because a single transport fails.
* Move alert transport creation into try block
Catch any potential exceptions during transport creation.
None of the transports currently implement __construct()
but the DB could throw and in the future there may be
a transport that does implement it.
* Remove auth use of $_SESSION
Will break plugins that depend on $_SESSION, Weathermap was already fixed.
Port them to use Auth::check()/Auth::user()/Auth:id()
* revert accidental replacement
* Changed snmptrap.php and handlers to allow for alerts.
* Moved RunRules() to Dispatcher.php
* Modified includes, passes pre-commit tests locally.
* Converted RunRules to OO, fixed formatting in files found by TravisCI
* rebase, covert alert subsy to oop
* Modified init.php to call new Alert subsystem
* fixed dependencies
* Resolved undefined functions
* Fixed PingCheck.php not triggering
* Changed runAlerts to __construct
* Fixes
Can't have Config inside empty()
incorrectly named function (my fault)
poller.php missing shebang
organize imports
* Add support for using Markdown.
Alert templates can be written using Webex Teams (i.e., Spark) Markdown,
which makes for some richer alerts. This option defaults to false to
maintain Principle of Least Astonishment.
* Update Cisco Spark docs.
* Mention that Cisco Spark is now called Webex Teams
* Add support for Markdown
* Refactor text.
Do not exceed 80 characters per line.
* Refactor code to meet style guidelines.
* Remove errant tabs and use spaces instead
* Correct type check
* Remove use of 'else'
* Allow new {{ $xxxx }} syntax
* Properly handle urlencode on variable values without braking the URL, and uses Blades
* Doc
Doc typo
* use Guzzle for HTTP requests
* Add Basic auth support
* Doc update
* clean
* Revert Blades, but keep the {{ $xxxx }} syntax
* Revert Blades, but keep the {{ $xxxx }} syntax
* Init Vars and comments
* Notifications
* api-options are not required
* Update notifications.rss
* Merge pull request #54 from librenms-plugins/revert-52-PluginNamespaceCorrection
Revert "Adding namespace LibreNMS\Plugins;"
SMS Eagle prevent user mis-configuration
Only allow URLs, but automatically append http:// to ones that are only hostname
* restore whitespace
Windows puts line returns as \r\n, when parsing LibreNMS previously left the \r, which could cause issues
Centralize the code so we just have one place to fix.
Try to fix SMSEagle, it had the options wrong (copied from another transport)
* Removed legacy transports and templates code
* Add notification
* abstract LnmsCommand
* Only issue alerts "legacy" alerts to mail for default contacts, etc.
* Prevent no contacts error when default contact is not specified, or there are no contacts for other reasons.
* remove eval \o/
* Update notifications.rss
* Change in the Canopsis transport to make it 3.9.0 compliant and link to
the new documentation
* Add missing php72 module on Centos
* Fixing documentation for AMQP based tranport outside of the main doc
* fixed#5659
Added support for Mattermost notifications.
George Pantazis <gpant@eservices-greece.com>
* Update Mattermost.php
* changes as requested by @murrant
* send entity ID as string
VO will not accept an int as an entity ID, this causes issues when issuing recovery alerts as the entity_id is the only way to link incidents. I have tested this with VO and incidents will alert AND recover.
* change from str() to strval() which is the correct function
* Add format field to Telegram Messages
Added Telegram field to send formatted messages as Mardown or HTML
* Update Telegram.php
* Correct Mistypo.
* Correct mistypo
* Correct Mistypo
* Correct mistypo
* Update Transports.md
* Add Format field on Telegram Examples
* Change Telegram Format field to type select
* Add "blank" option to Format field
* Update Telegram.php
* Update Telegram.php
* Update Telegram.php
DO NOT DELETE THIS TEXT
#### Please note
> Please read this information carefully. You can run `./scripts/pre-commit.php` to check your code before submitting.
- [x] Have you followed our [code guidelines?](http://docs.librenms.org/Developing/Code-Guidelines/)
#### Testers
If you would like to test this pull request then please run: `./scripts/github-apply <pr_id>`, i.e `./scripts/github-apply 5926`
After you are done testing, you can remove the changes with `./scripts/github-remove`. If there are schema changes, you can ask on discord how to revert.
SourceDoctor
cjwbath
mendoza-conicet
PipoCanaja
Tony Murray
Ngo Quang Hoa
hartred
seros1521
Shao Yu-Lung (Allen)
Lee Keitel
SniperVegeta
Heath Barnhart
Joe Clarke
Tyler Christiansen
Mihai Petracovici
Neil Lathwood
angryp
pobradovic08
Misha Komarovskiy
aylham
Richard Mayhew
George Pantazis
TheGreatDoc
GitStoph
George Pantazis
Alex Typaldos
gillmore-ac
Drew Hynes
Paulo Coimbra