지금 지원 담당자와 채팅
지원 담당자와 채팅

syslog-ng Store Box 7.0 LTS - Administration Guide

Preface Introduction The concepts of SSB The Welcome Wizard and the first login Basic settings User management and access control Managing SSB Configuring message sources Storing messages on SSB Forwarding messages from SSB Log paths: routing and processing messages Configuring syslog-ng options Searching log messages Searching the internal messages of SSB Classifying messages with pattern databases The SSB RPC API Monitoring SSB Troubleshooting SSB Security checklist for configuring SSB Glossary

Adding a new Microsoft Azure-managed disk as a custom cloud service provider data disk on the Microsoft Azure Portal side

This section describes how you can add a new Microsoft Azure-managed disk as a custom cloud service provider data disk to your syslog-ng Store Box (SSB) configuration on the Microsoft Azure Portal side.

If you need more disk space than the disk size of your default data disk available in syslog-ng Store Box (SSB), from version 6.9.0, you can also add a custom cloud service provider data disk to your configuration. From 6.9.0, SSB supports adding a Microsoft Azure-managed disk and from 6.10.0, SSB supports adding additional disks in VMware ESXi to your SSB configuration as a custom cloud service provider data disk, and assigning the SSB logspace of your choice to it.

In version 7.0 LTS, SSB supports adding Microsoft Azure managed disks of up to 32,767 GiB storage space to your SSB device. For more information about managed data disks in Microsoft Azure, see Disk type comparison in the Microsoft Azure online documentation.

Adding a new Microsoft Azure-managed disk as a custom cloud service provider data disk to your SSB configuration requires procedures that you must complete in a strict order, both on the SSB side, and on the Microsoft Azure Portal, too.

NOTE: After you configure your custom Microsoft Azure-managed disk on the Microsoft Azure side, you must add the disk to your SSB configuration, and then assign the SSB logspace of your choice to it on the SSB side.

For more information about how you can add a Microsoft Azure-managed disk to your SSB configuration on the SSB side, see Adding a new custom cloud service provider data disk to your SSB configuration on the SSB side.

Prerequisites

When adding a new Microsoft Azure-managed disk that you will later want to add to your SSB configuration, consider the following prerequisites in advance:

  • You can only add an Azure managed disk as a custom cloud service provider data disk to your SSB on the Microsoft Azure portal side.

  • The number of managed disks you can add on the Microsoft Azure portal depends on the type of Microsoft Azure subscription you are using.

Limitations

When adding a new Microsoft Azure-managed disk that you will later want to add to your SSB configuration, consider the following limitations in advance:

  		•  Caution:

    HAZARD OF DATA LOSS!

    Although it is possible to decrease the size of Microsoft Azure and VMware ESXi managed disks, One Identity does not support decreasing the size of custom cloud service provider data disks already added to your SSB configuration. One Identity only supports increasing the size of such custom cloud service provider data disks after adding them to your SSB configuration.

  • In version 7.0 LTS, SSB supports adding Microsoft Azure managed disks of up to 32,767 GiB storage space to your SSB device. For more information about managed data disks in Microsoft Azure, see Disk type comparison in the Microsoft Azure online documentation.

  		•

    CAUTION: HAZARD OF DATA LOSS!

    One Identity does not support decreasing the size of an additional VMware ESXi hard disk added to your SSB configuration as a custom cloud service provider data disk.

    You can only add, remove, or resize a custom cloud service provider data disk in your configuration after shutting your SSB device down first. Hot swaps are not supported.

  • SSB only accepts and detects empty disks as custom cloud service provider data disks. As a result, you can only add a newly created Azure managed disk or VMware ESXi disk as a custom cloud service provider data disk to your SSB configuration. Adding an already existing Azure managed disk (by clicking Attach existing disks on the Microsoft Azure portal) or already existing VMware ESXi disk is not supported.

  • Transporting custom cloud service provider data disks between SSB devices is not supported.

  • One Identity does not support adding Microsoft Azure or VMware ESXi managed disks to your SSB logspaces as a shared disk.

Adding a new Microsoft Azure-managed disk as a custom cloud service provider data disk to your SSB configuration requires procedures that you must complete in a strict order.

To add a new Microsoft Azure-managed disk as a custom cloud service provider data disk on the Microsoft Azure Portal side,

  1. Shut down your SSB device completely.

  2. Log in to the Microsoft Azure Portal.

  3. Navigate to the virtual machine of your SSB device.

    Figure 155: Home > All resources> <your-virtual-machine-in-microsoft-azure>

  4. Follow the instructions of the Microsoft Azure online tutorial documentation to attach a new data disk with the size of your choice to the virtual machine of your SSB device.

    After successfully attaching the data disk, it appears under the Disks of the virtual machine of your SSB device.

    Figure 156: Home > All resources> <your-virtual-machine-in-microsoft-azure> > Settings > Disk - The new data disk attached to the virtual machine of your SSB device

    NOTE: The LUN (Logical Unit Number) value of your attached data disk corresponds to the last digit of the Host:Channel:Target:LUN (HCTL) of your custom cloud service provider data disk on the SSB side.

    Figure 157: Log > Disks> <your-custom-data-disk> - The LUN value corresponds to the last digit of the HCTL on the SSB side

  5. Restart the virtual machine for your SSB device, add the newly created Microsoft Azure-managed disk to your SSB configuration as a custom cloud service provider data disk, and then assign the SSB logspace of your choice to the newly added custom cloud service provider data disk.

Adding an additional disk in VMware ESXi as a custom cloud service provider data disk on the vSphere Client side

This section describes how you can add additional hard disks in the VMware vSphere Client as a custom cloud service provider data disk to your syslog-ng Store Box (SSB) configuration.

If you need more disk space than the disk size of your default data disk available in syslog-ng Store Box (SSB), from version 6.9.0, you can also add a custom cloud service provider data disk to your configuration. From 6.9.0, SSB supports adding a Microsoft Azure-managed disk and from 6.10.0, SSB supports adding additional disks in VMware ESXi to your SSB configuration as a custom cloud service provider data disk, and assigning the SSB logspace of your choice to it.

Limitations

When adding a new hard disk in VMware ESXi that you will later want to add to your SSB configuration, consider the following limitations in advance:

  		•

    CAUTION: HAZARD OF DATA LOSS!

    One Identity does not support decreasing the size of an additional VMware ESXi hard disk added to your SSB configuration as a custom cloud service provider data disk.

    You can only add, remove, or resize a custom cloud service provider data disk in your configuration after shutting your SSB device down first. Hot swaps are not supported.

  • SSB only accepts and detects empty disks as custom cloud service provider data disks. As a result, you can only add a newly created Azure managed disk or VMware ESXi disk as a custom cloud service provider data disk to your SSB configuration. Adding an already existing Azure managed disk (by clicking Attach existing disks on the Microsoft Azure portal) or already existing VMware ESXi disk is not supported.

  • Transporting custom cloud service provider data disks between SSB devices is not supported.

  • One Identity does not support adding Microsoft Azure or VMware ESXi managed disks to your SSB logspaces as a shared disk.

Adding an additional disk in VMware ESXi as a custom cloud service provider data disk on the Microsoft Azure Portal side

Adding a new Microsoft Azure-managed disk as a custom cloud service provider data disk to your SSB configuration requires procedures that you must complete in a strict order.

To add a new hard disk as a custom cloud service provider data disk on the VMware vSphere Client side,

  1. Shut down your SSB device completely.

  2. Log in to the VMware vSphere Client site.

  3. Navigate to the virtual machine of your SSB device.

    Figure 158: <your-virtual-machine-in-VMware-ESXi>

  4. Follow the instructions of the VMware documentation to Add a New Disk to a Virtual Machine with the size of your choice to the virtual machine of your device.

    Figure 159: <your-virtual-machine-in-VMware-ESXi> > VM Hardware > Edit settings... > ADD NEW DEVICE > Hard Disk - Adding a new disk

    After successfully attaching the data disk, it appears under the Disks of the virtual machine of your SSB device.

  5. Restart the virtual machine for your SSB device, add the newly created disk to your SSB configuration as a custom cloud service provider data disk, and then assign the SSB logspace of your choice to the newly added custom cloud service provider data disk.

Adding a new custom cloud service provider data disk to your SSB configuration on the SSB side

If you need more disk space than the disk size of your default data disk available in syslog-ng Store Box (SSB), from version 6.9.0, you can also add a custom cloud service provider data disk to your configuration. From 6.9.0, SSB supports adding a Microsoft Azure-managed disk and from 6.10.0, SSB supports adding additional disks in VMware ESXi to your SSB configuration as a custom cloud service provider data disk, and assigning the SSB logspace of your choice to it.

This section describes how you can add a new custom cloud service provider data disk to your syslog-ng Store Box (SSB) configuration on the SSB side.

For more information about how you can add a custom cloud service provider data disk on the cloud service provider side, see Adding a new custom cloud service provider data disk on the cloud service provider side.

For more information about assigning the SSB logspace of your choice to a custom cloud service provider data disk, see Assigning the SSB logspace of your choice to a custom cloud service provider data disk.

For more information about the data disk information for your custom cloud service provider data disks, see Data disk information for your custom cloud service provider data disks.

Prerequisites

When adding a new custom cloud service provider data disk to your SSB configuration on the SSB side, consider the following prerequisites in advance:

  • If you want to add a custom cloud service provider data disk to your SSB configuration, you must add a new custom cloud service provider data disk on your cloud service provider side before you can add it to your configuration on the SSB side.

  • If you want to add custom cloud service provider data disks to your configuration in SSB, you must add the custom cloud service provider data disk under Log > Disks > <your-custom-data-disk>, and commit your changes. After that, the newly added custom cloud service provider data disk will be available for selection in the dropdown list under Log > Logspaces > <your-new-logspace-with-custom-data-disk> > Storage > Disk.

Limitations

When adding a new custom cloud service provider data disk to your SSB configuration on the SSB side, consider the following limitations in advance:

  		•  Caution:

    HAZARD OF DATA LOSS!

    Although it is possible to decrease the size of Microsoft Azure and VMware ESXi managed disks, One Identity does not support decreasing the size of custom cloud service provider data disks already added to your SSB configuration. One Identity only supports increasing the size of such custom cloud service provider data disks after adding them to your SSB configuration.

  • NOTE: Resizing your custom cloud service provider data disk on the Microsoft Azure or VMware ESXi side may be quick, depending on your infrastructure, but your SSB configuration must resize the file system on your SSB side to match the resizing on the Microsoft Azure or VMware ESXi side. As a result, depending on the original size of the custom cloud service provider data disk and on the size you will expand it to, starting the virtual machine for your SSB device after you expand the size of your custom cloud service provider data disk may take a long time.

  • NOTE: If you fail to assign the newly created SSB logspace of your choice to the new custom cloud service provider data disk, SSB will not automatically detect and use the new custom cloud service provider data disk to store messages on it.

  • You can only configure custom cloud service provider data disks for logspaces that you newly create. One Identity does not support configuring custom cloud service provider data disks in logspaces that you configured and committed earlier.

  • In version 7.0 LTS, SSB supports adding Microsoft Azure managed disks of up to 32,767 GiB storage space to your SSB device. For more information about managed data disks in Microsoft Azure, see Disk type comparison in the Microsoft Azure online documentation.

  • If you want to add custom cloud service provider data disks to your configuration in SSB, you must add the custom cloud service provider data disk under Log > Disks > <your-custom-data-disk>, and commit your changes. After that, the newly added custom cloud service provider data disk will be available for selection in the dropdown list under Log > Logspaces > <your-new-logspace-with-custom-data-disk> > Storage > Disk.

  • Transporting custom cloud service provider data disks between SSB devices is not supported.

  		•

    CAUTION: HAZARD OF DATA LOSS!

    One Identity does not support decreasing the size of an additional VMware ESXi hard disk added to your SSB configuration as a custom cloud service provider data disk.

    You can only add, remove, or resize a custom cloud service provider data disk in your configuration after shutting your SSB device down first. Hot swaps are not supported.

  • You can only add an Azure managed disk as a custom cloud service provider data disk to your SSB on the Microsoft Azure portal side.

  • SSB only accepts and detects empty disks as custom cloud service provider data disks. As a result, you can only add a newly created Azure managed disk or VMware ESXi disk as a custom cloud service provider data disk to your SSB configuration. Adding an already existing Azure managed disk (by clicking Attach existing disks on the Microsoft Azure portal) or already existing VMware ESXi disk is not supported.

  • One Identity does not support adding Microsoft Azure or VMware ESXi managed disks to your SSB logspaces as a shared disk.

  • The number of managed disks you can add on the Microsoft Azure portal depends on the type of Microsoft Azure subscription you are using.

After adding a new custom cloud service provider data disk on your cloud service provider side, you can add the new custom cloud service provider data disk on the SSB side.

To add a new custom cloud service provider data disk to your SSB configuration,

  1. On the SSB side, shut down your SSB device

    1. Navigate to Basic Settings > System.

    2. Under System control, click Shutdown.

  2. On the cloud service provider side, complete the following steps depending on which cloud service provider you want to use:

  3. In the virtual machine for your SSB device, complete the following steps on the SSB web interface:

    1. Navigate to Log > Disks.

      SSB will automatically detect newly added custom cloud service provider data disks and display them:

      Figure 160: Log > Disks - New disks detected

    2. Enter a name for your new custom cloud service provider data disk, and click .

      Figure 161: Log > Disks > <your-custom-data-disk>

    3. Navigate to Log > Logspaces, and assign the SSB logspace of your choice to the custom cloud service provider data disk.

      NOTE: If you fail to assign the newly created SSB logspace of your choice to the new custom cloud service provider data disk, SSB will not automatically detect and use the new custom cloud service provider data disk to store messages on it.

      NOTE:After adding a newly created custom cloud service provider data disk to your SSB configuration, and assigning the SSB logspace of your choice to it, removing the custom cloud service provider data disk from your SSB configuration has a strict order, especially if there are referenced objects tied to the custom cloud service provider data disk. For more information about the process to remove such custom cloud service provider data disks from your SSB configuration, see Removing a custom cloud service provider data disk from your SSB configuration.

      NOTE: For newly created logspaces, selecting a data disk for your logspace is required.

Data disk information for your custom cloud service provider data disks

If you need more disk space than the disk size of your default data disk available in syslog-ng Store Box (SSB), from version 6.9.0, you can also add a custom cloud service provider data disk to your configuration. From 6.9.0, SSB supports adding a Microsoft Azure-managed disk and from 6.10.0, SSB supports adding additional disks in VMware ESXi to your SSB configuration as a custom cloud service provider data disk, and assigning the SSB logspace of your choice to it.

In version 7.0 LTS, SSB supports adding Microsoft Azure managed disks of up to 32,767 GiB storage space to your SSB device. For more information about managed data disks in Microsoft Azure, see Disk type comparison in the Microsoft Azure online documentation.

This section describes the data disk information available for custom cloud service provider data disks on the web interface.

For more information about custom cloud service provider data disks on the cloud service provider side, see Adding a new custom cloud service provider data disk on the cloud service provider side.

For more information about custom cloud service provider data disks on the side, see Adding a new custom cloud service provider data disk to your SSB configuration.

For more information about assigning the SSB logspace of your choice to a custom cloud service provider data disk, see Assigning the SSB logspace of your choice to a custom cloud service provider data disk.

Data disk information for your custom cloud service provider data disks

After adding the new custom cloud service provider data disk to your SSB configuration, the following data disk information will be displayed under Log > Disks > <your-custom-data-disk>:

Figure 162: Log > Disks > <your-custom-data-disk> — Data disk information for your custom cloud service provider data disks

  • Status: The connectivity status of the custom cloud service provider data disk between the SSB side and the cloud service provider side.

    The possible status states are the following:

    • attached: The custom cloud service provider data disk is successfully attached to the virtual machine for your SSB device on the cloud service provider (in this case, Microsoft Azure) side.

    • missing: The custom cloud service provider data disk is committed to your SSB configuration, but the SSB device can not detect or access it on the cloud service provider side for some reason (for example, it was removed on the Microsoft Azure side earlier, or there is a connectivity issue with the Microsoft Azure portal).

  • File system ID: The unique identifier for your file system on the SSB side.

  • Host:Channel:Target:LUN (HCTL): The locally unique identifier for your custom cloud service provider data disk, which consists of the colon-separated data of the Host, the Channel, the Target, and the LUN (Logical Unit Number) value.

    The last digit of the custom cloud service provider data disk's Host:Channel:Target:LUN (HCTL) corresponds to the attached custom cloud service provider data disk's LUN value on the Microsoft Azure portal:

    Figure 163: Log > Disks > <your-custom-data-disk> — Data disk information for your newly added custom cloud service provider data disks (Microsoft Azure)

    Figure 164: Log > Disks > <your-custom-data-disk> — Data disk information for your custom cloud service provider data disks, with no SSB logspace assigned to them yet (Microsoft Azure)

    The second to last digit of the custom cloud service provider data disk's Host:Channel:Target:LUN (HCTL) corresponds to the attached custom cloud service provider data disk's Target value in VMware ESXi:

    Figure 165: Log > Disks > <your-custom-data-disk> — Data disk information for your newly added custom cloud service provider data disks (VMware ESXi)

    Figure 166: Log > Disks > <your-custom-data-disk> — Data disk information for your custom cloud service provider data disks, with no SSB logspace assigned to them yet (VMware ESXi)

  • Device name: The navigation path to your device on the SSB side.

  • Disk utilization: The utilization ratio of your custom data disk (in percentage), followed by the exact amount of free space, and the full size of the disk, in brackets.

  • (Optional) Onscreen information about logspaces assigned to the data disk: When you have not assigned the SSB logspace of your choice to the custom cloud service provider data disk yet, you will see the There are no available logspaces on this disk yet. onscreen information displayed on the SSB web interface.

  • (Optional) Logspaces available on this disk: When you have already assigned the SSB logspace of your choice to the custom cloud service provider data disk, the assigned logspaces will be listed here.

    Figure 167: Log > Disks > <your-custom-data-disk> — Data disk information for your custom cloud service provider data disks, with the SSB logspace of your choice assigned to them

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택