This identifies you with your Panopta account. By setting this value, the agent will automatically add the server to the Panopta control panel. You can find this key in the control panel under My Account under your icon at the top right.
The server key is what allows the Agent to communicate with our servers securely. You have the option of setting this value if you like. However, we highly recommend that you allow a key to be generated for you and linked to the server in Panopta accordingly.
Note: all server keys must be unique.
This controls the API which the Agent communicates with to report its results. You should not enter an aggregator URL unless you are using Panopta Onsight as a proxy for servers that do not have outbound public internet access. If you are using Panopta Onsight as a proxy and don't know the aggregator URL, please contact firstname.lastname@example.org
This controls which group your server gets added to in the control panel. Any server template(s) that you have set to be applied to this group will be applied to this server as well. The value of the server group is identified by an ID or a name. If you go to an instance group in the control panel, you can see that group's ID number at the end of that page's URL.
This field acts as an override for the hostname that is auto-detected by the Agent. If you do not include this field, your server will be given its natural FQDN in the control panel.
This field lets you set a logical name for this server. That name will identify the server in the control panel.
This value is only used if:
If your server has multiple network interfaces and the template which is being applied has placeholders for multiple network interfaces, you have to provide a mapping of the IP for that network interface to the placeholder.
For example, if your server template has the network interface placeholder named Private, and your server has a network interface with the IP set to 10.100.100.2, you would configure it like this:
interface_mapping = private:10.100.100.2
This field lets you choose which templates you would like to apply to this server. The value of the template is identified by an ID. If you go to a server template in the control panel, you can see that template's ID number at the end of that page's URL.
This field would allow you to add tags to your server. This can be set to any value but would need to be comma-separated to indicate different tags.
tags = tag1, tag2, tag3
This value can be used by Panopta partners in order to store their own internal unique identifiers for that server. Setting the value in the manifest file sets it on the Server/Instance object which can then help in server lookups by the partner's ID (via API or within the control panel).
The default behavior, when customer_key is provided, is to do some automatic server matching by hostname or IP. In some cases, this may be undesirable if you have overlapping private IP ranges across environments. This option allows you to disable the matching logic.
You can also add an additional field for attributes. This will need to go underneath the rest of the manifest file configurations, and you can set the attributes to any value.
If you have written your own custom plugins, you can host them centrally and have the agent retrieve them during installation so that you do not have to manually manage them post-install. The value of this variable can be a compressed archive (.zip, .tar or .tgz) or a single python file (with a .py extension).
New plugins are fetched from the URL defined in custom_plugin_url during metadata rebuilds. By default, metadata rebuilds occur once every hour. You also have the option to manually re-fetch new plugins by issuing a metadata rebuild command, either through the control panel or the command line.
This flag enables the CounterMeasures remediation feature in the Agent. Read more about this here.
If you have written your own custom CounterMeasures plugins, you can host them centrally and have the Agent retrieve them during installation so that you do not have to manually manage them post-install. The value of this variable can be a compressed archive (.zip, .tar or .tgz).
If you would like updates to your CounterMeasures plugins to automatically be applied, you can optionally set countermeasures_refresh_plugins to the number of hours for the refresh interval and the Agent will re-fetch the newest plugins from your remote plugin location.
To pass plugin configuration to a standard Panopta plugin or one of your own custom plugins, specify those at the bottom of the file. Examples for Linux and Windows are shown in the following sections.