Synthetics - add ability to set device/group properties to reference in the .side file
With synthetic transactions, currently the only way to pass a value into the .side file is within the Authentication step during the initial creation of the synthetic check. The values can be referenced withthe credential.username/password/token variables in the .side file. This is pretty limiting, especially since it can only be defined during the initial check creation. If the password changes for my websites test user, I need to delete/recreate the check to redefine the authentication. This causes a loss of historical data. It would be a huge improvement if we could set a property on the synthetic check in LogicMonitor and then reference that property within the .side file. That way if I want to change the username or password for a check which involves a login, I don’t need to delete/recreate the check.20Views10likes0CommentsSynthetics - add ability to update existing checks and download .side file via configsource
With synthetic transactions, currently you need to delete/recreate a check if we want to update it or change the username/password used for authentication. This causes loss of historical data and is difficult to manage. There are 2 things I would like to request that would make it easier for us to manage synthetic transactions. add ability to update an existing check. This includes updating the .side file or updating the authentication Add ability to download the .side file for an existing check via a companion Configsource. This would make it easier to resolve issues with a check and tweak it without impacting historical data.11Views10likes0Comments