Logging with bare metal servers

Before you begin

Read about IBM Log Analysis. For more information, see About.

Work in a supported region.

You can send data from an Ubuntu instance that is located in the same region as your logging instance, in a different region, or not in the IBM Cloud.

Use a user ID that is a member, or an owner of, an IBM Cloud account. To get an IBM Cloud IBMID, go to: Create an account.

Your IBMID must have assigned IAM policies for each of the following resources in the region that your IBM Log Analysis instance is in:

Your IBMID must have assigned IAM policies for each of the following resources:

The IBM Cloud CLI must be installed. For more information, see Installing the IBM Cloud CLI.

Provision a bare metal server

If you have a bare metal server that you want to monitor, you can skip this step.

If you don't have a bare metal server, complete the following steps

1. Provision a bare metal server.

   To complete the steps in this topic, ensure you have internet access from the bare metal server. This is needed for configuring the monitoring agent.

2. Configure a VPN connection between your terminal and the bare metal server

   Virtual Private Networking (VPN) access enables users to manage all servers remotely and securely over the IBM Cloud® private network. A VPN connection from your location to the private network allows out-of-band management and server rescue through an encrypted VPN tunnel. VPN tunnels can be initiated to any IBM Cloud data center or PoP allowing you geographic redundancy.

   Complete the following steps to configure a VPN connection between your terminal and the bare metal server:

   1. Enable VPN access on each account that needs VPN access.

   2. Depending on your operating system, download the latest MotionPro 32-bit or 64-bit files from the Array Networks Clients and Tools download site. Learn more.

   3. Configure a standalone SSL VPN client and open a connection:

   For example, if you use the MotionPro Plus client for MacOS, to add a profile, click Add.

   In the Basic section, enter a Title. Enter a Gateway, for example, for a bare metal in Dallas 10, enter vpn.dal10.softlayer.com. Enter your VPN user name. Check that the Port is set to 443. Then, click OK.

   To open a secure connection, click Login.

3. Connect to a bare metal server by using SSH

   You might require a VPN to access your system depending on your security setup and ssh configuration on the bare metal host.

   You must ssh to the host by using your credentials, or the root credentials that are available from the IBM Cloud Console.

   You will require root permissions in order to install the monitoring agent.

   For example, you can complete the following steps to get the bare metal server information that you need to ssh into the server:

   1. Log in to your IBM Cloud account.

   2. Click the Menu icon > Classic Infrastructure > Device List.

   3. Identify the bare metal server that you want to monitor. Copy the Public IP.

   4. Click the bare metal server device name.

   5. Select Passwords. Copy the password for the root user.

      Then, from a terminal, run the following command:

      ssh <USER_ID>@<IP_ADDRESS>
      

      Where:

      <USER_ID> is the user ID that you use to log in to the bare metal server. For example, use root.

      <IP_ADDRESS> is the public IP address of the bare metal server.

      For example: ssh root@45.123.122.12

Provision an IBM Log Analysis instance

To provision an instance of IBM Log Analysis through the IBM Cloud UI, complete the following steps:

1. Log in to your IBM Cloud account.

   Click Log in to IBM Cloud to sign in to the IBM Cloud.

   After you log in with your user ID and password, the IBM Cloud console opens.

2. Click Catalog. The list of the services that are available in IBM Cloud opens.

3. To filter the list of services that is displayed, click Services and select the Logging and Monitoring category.

4. Click the IBM Log Analysis tile.

5. Select a region for the service instance.

6. Select the Lite service plan.

   By default, the Lite plan is set.

   For more information about other service plans, see Pricing plans.

7. Specify a Service name for your IBM Log Analysis service instance.

8. Select the Default resource group.

   By default, the Default resource group is set.

9. To provision the IBM Log Analysis service in the IBM Cloud selected resource group, click Create.

After you provision an instance, the IBM Log Analysis dashboard opens.

To provision an instance of logging through the CLI, see Provisioning logging through the IBM Cloud CLI.

Configure a bare metal server to send logs to your logging instance

To configure your bare metal server to send logs to your IBM Log Analysis instance, you must install a logging-agent. The logging agent reads log files from /var/log or other directories you specify, and forwards the log data to your logging instance.

To configure your bare metal server to forward logs to your logging instance, complete the following steps from an Ubuntu terminal:

1. Install the logging agent. Run the following commands:

   echo "deb https://assets.logdna.com stable main" | sudo tee /etc/apt/sources.list.d/logdna.list
   

   wget -O- https://assets.logdna.com/logdna.gpg | sudo apt-key add -
   

   sudo apt-get update
   

   sudo apt-get install logdna-agent < "/dev/null"
   

2. Set the ingestion key that the logging agent will use to forward logs to the IBM Log Analysis instance.

   sudo logdna-agent -k <INGESTION_KEY>
   

   where <INGESTION_KEY> contains the ingestion key for the IBM Log Analysis instance where the logs will be forwarded.

   You can retrieve the ingestion key using the IBM Cloud console, or by the IBM Cloud CLI.

3. Set the authentication endpoint. The logging agent uses this host to authenticate and get the token to forward logs.

   sudo logdna-agent -s LOGDNA_APIHOST=api.us-south.logging.cloud.ibm.com
   

4. Set the ingestion endpoint.

   sudo logdna-agent -s LOGDNA_LOGHOST=logs.us-south.logging.cloud.ibm.com
   

5. (Optional) Define any additional log paths to be monitored. Run the following command:

   sudo logdna-agent -d <PATH_TO_LOG_FOLDERS>
   

   Where <PATH_TO_LOG_FOLDERS> is the path where logs are saved on your system. By default, /var/log is monitored.

6. (Optional) Configure the logging agent to tag your hosts. Run the following command:

   sudo logdna-agent -t TAG1,TAG2
   

   Tags must be separated by commas and without any spaces between the comma and tag name.

7. Update the logging agent with your changes. Run the following command:

   sudo update-rc.d logdna-agent defaults
   

8. Start the logging agent. Run the following command:

   sudo /etc/init.d/logdna-agent start
   

Launch the logging Web UI

To launch the IBM Log Analysis dashboard from the IBM Cloud UI, complete the following steps:

1. Log in to your IBM Cloud account.

   Click IBM Cloud dashboard to launch the IBM Cloud dashboard.

   After you log in with your user ID and password, the IBM Cloud Dashboard opens.

2. In the navigation menu, select Observability.

3. Click Logging.

   The list of IBM Log Analysis instances that are available on IBM Cloud is displayed.

4. Select one instance. Then, click Open dashboard.

   The logging Web UI opens and displays your cluster logs.

View your logs

From the logging Web UI, you can view your logs as they pass through the system. You view logs by using log tailing.

With the Free service plan, you can only tail your latest logs.

For more information, see Viewing logs.

Next steps

The following additional features are available:

• Filtering logs
• Searching logs
• Defining views
• Configuring alerts.

To use any of these features, you must upgrade the IBM Log Analysis plan to a paid plan.