Come join our live training webinar every other Wednesday at 11am PST and hear LogicMonitor experts explain best practices and answer common questions. We understand these are uncertain times, and we are here to help!
Properties can be added to your LogicMonitor websites to facilitate organization, customize alert message templates, set authentication credentials, and more. You can set website properties at the individual website level, website group level, and at the root group (account) level. As shown next, website properties, once established, can be viewed from the Info tab.
Before you set properties for your websites, you should decide where to set them. Ultimately, this decision depends on how many websites a property applies to. For example:
Properties cascade down the Website tree until they are overridden. For example, if the same property is set at the website group level and individual website level, the individual website takes precedence. As a best practice, we recommend that you set global credentials and override them as needed for groups of websites or individual websites.
Website properties can be added when first creating the website, or can be added later. The following set of steps illustrate how to add a property to an existing website, a website group, or the Websites tree root.
Note: Existing property values can be edited from this section as well by simply placing your cursor into the Value field.
LogicMonitor offers several built-in properties for website monitoring that allow you to manipulate the settings of the external Web Checks we perform from our checkpoints. Specifically, these settings were created to provide some flexibility in cases where sites may load slower than our default timeouts.
The following built-in properties all default to 30 seconds and all support an acceptable value range between >0 and <=60.
>0 and <=60
A common use for website properties is for authentication. Username and password properties can be established and then passed in as tokens when authenticating requests, as shown next.
Note: In a real application, LogicMonitor will mask the password as hard-coded passwords are also supported, but as shown above for effect, the password can be passed in as a property as well.
Setting credentials as properties (vs. hard coding credentials into the authorization fields of a Web Check) is useful when there are multiple websites requiring the same authentication credentials. These websites can be grouped together and username and password properties can be set at the group level. With this setup, the process of updating authentication credentials is trivial, requiring only a single update. Additionally, websites that are subsequently added to the group will automatically inherit the correct username and password properties.
In This Article