HTTPS Log Server - Send Log Message
  • 22 Nov 2022
  • 4 Minutes to read
  • Dark
    Light
  • PDF

HTTPS Log Server - Send Log Message

  • Dark
    Light
  • PDF

HTTPS Log Server - Send Log Message creates a log message with a custom description and/or the action results summary (incident description) in an HTTPS log server. It also creates optional JSON messages with the asset data (device or user) for each of the assets in the query results or a JSON file with data about the system entity queried, for queries created on Activity logs and Fetch History using filters.

To use this action, you must enable the Use HTTPS logs setting and configure the HTTPS Logs host and port. For more details, see Global Settings.

The incident description message includes the Enforcement Set name, the triggered query, the condition for executing the Enforcement (if it exists), and number of current and previous results.

Message Example

Click to view Message Example

Alert - "test" for the following query has been triggered: Missing Sophos

Alert Details
The alert was triggered because: The number of entities is above 0
The number of devices returned by the query:4
The previous number of devices was:4

You can view the query and its results here: https://demo-latest.axonius.com/devices?view=Missing Sophos


Connection Settings

Click to view Connection Settings


  1. Authorization Header (optional, default: empty) - If the HTTPS log server message requires user authentication, specify the required HTTP authorization request in the field.
    • If supplied, Axonius will pass the specified authorization header information with the HTTP request.
    • If not supplied, Axonius will not pass any additional information with the HTTP request.

Action Settings

Click to view Action Settings


  1. Description (optional, default: empty) - Specify an optional description.
    • If supplied, Axonius will include the specified description in HTTPS log server message.
    • If not supplied, Axonius will not include any custom description in HTTPS log server message.
  2. Send result details (required, default: False) - Select whether to send additional messages to the HTTPS log server with the details of the results.
    • If enabled, Axonius will send a JSON file with details of the results.
    • If disabled, Axonius will not send details of the results.
  3. Add default incident description (required, default: False) - Select whether to send the incident description to the HTTPS log server.
    • If enabled, Axonius will include the default incident description (mentioned above) in HTTPS log server message.
    • If disabled, Axonius will not include the default incident description (mentioned above) in HTTPS log server message.
  4. Send CSV data (required, default: False) - Select whether to send the ran query data in a CSV format to the HTTPS log server.
    • If enabled, Axonius will include the query data in a CSV format in HTTPS log server message.
    • If disabled, Axonius will not include the query data in HTTPS log server message.
  5. Extra headers around message (JSON format) (optional, default: empty) - Use this setting to add a JSON formatted string that can be added to the HTTPS Log JSON thus enabling efficient integration with tools that accept input of JSON. The input should appear as follows:
     {"index": 12345, "sourcetype": "_json"}
    

Additional CSV Settings

  1. Split by asset entities (required, default: false) - Select to create a CSV file where each asset on a device is shown as a separate row. This separates each asset as the 'expand' option in the application. It separates each asset by its entity. For example, you will be able to know which values were fetched from each adapter connection.
    a. If supplied, each value on a device or user is shown as a separate row.
    b. If not supplied all values on a device are in the same cell on the CSV file.
  2. Split by field values (optional, default empty) - Choose field value - For complex fields and lists you can create a CSV file where the values of complex fields and lists are represented as separate rows in the file. From the drop-down box select the value that you want to display in the file, 'Tags' for instance. Only fields that have been discovered are available. For example, if you export by Installed Software, you will be able to see each installed Software name and its version.
  3. Don't split complex objects into columns (optional, default: false) - When selected, complex objects appear in a single column in JSON format. By default, each field in a complex object is split into a separate column in the CSV file.
  4. Export CSV delimiter to use for multi-value fields (optional, default: Export CSV delimiter to use for multi-value fields field under the System Settings section in the GUI Settings) - Specify a delimiter to separate between values within the same field of an exported CSV file, otherwise the delimiter defined in Export CSV delimiter to use for multi-value fields is used.
  5. Maximum rows (optional, default: 1048500) - Specify the maximum number of rows to be included in the CSV file. When you set a value here the generated CSV file will include the top x rows, based on the specified values. Otherwise, the generated CSV file will include the default maximum rows, set as 1048500.


To learn more about configuring Enforcement Sets, see Configuring Enforcement Sets.


Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.