Latest Post

Fluentd error: Unable to push logs to [elasticsearch]

-
After application deployments, Kibana stopped showing logs exactly after 7 days. The error "Fluentd error: Unable to push logs to [elasticsearch]" was shown in the fluentd logs. The initial response was to increase the buffer limits for fluentd as follows: chunk_limit_size 10M queue_limit_length 256 The behavior occurred again after two weeks, which led to the same error. On closer investigation, the error was preceded by the statement "Failed to write to the buffer." This led me to inspect the fluentd configuration again and found the following code in the buffer part which caused the fluentd buffers to be filled as per the official documentation on Fluentd : overflow_action block The fix for this overflow_action is to change from block to drop_oldest_chunk, allowing the fluentd logs to flow seamlessly to the elastic search by dropping the oldest logs in the buffer.   <buffer> @type file path /var/log/fluentd-buffers/kubernet...
Post a Comment

On-board Linux computers to Azure Log Analytics

-
For on-boarding linux servers to Azure log analytics, just execute the command on the respective server:

wget https://raw.githubusercontent.com/Microsoft/OMS-Agent-for-Linux/master/installer/scripts/onboard_agent.sh && sh onboard_agent.sh -p [protocol://][user:password@]proxyhost[:port] -w <YOUR WORKSPACE ID> -s <YOUR WORKSPACE PRIMARY KEY>

In few cases like mine, the servers will not have access to internet and we will need to install the downloaded oms agent package with the proxy information. 

sh omsagent-1.6.0-42.universal.x64.sh --install -w <YOUR WORKSPACE ID> -s <YOUR WORKSPACE PRIMARY KEY> -p [protocol://][user:password@]proxyhost[:port]

The proxy can have username and password for authentication and even if no proxy authentication is required, we will need to enter a dummy username and password which in the example below is azure and azure.

sh omsagent-1.6.0-42.universal.x64.sh --install -w <YOUR WORKSPACE ID> -s <YOUR WORKSPACE PRIMARY KEY> -p http://azure:azure@proxyhost[:port]

If you have SCOM agent already installed then instead of --install we will need to specify --upgrade.

sh omsagent-1.6.0-42.universal.x64.sh --upgrade -w <YOUR WORKSPACE ID> -s <YOUR WORKSPACE PRIMARY KEY> -p http://azure:azure@proxyhost[:port]

Comments

  1. suryaJuly 21, 2020 at 5:39 PM

    Very useful post. This is my first time i visit here. I found so many interesting stuff in your blog especially its discussion. Really its great article.
    angular js training in chennai

    angular js online training in chennai

    angular js training in bangalore

    angular js training in hyderabad

    angular js training in coimbatore

    angular js training

    angular js online training

    ReplyDelete
  2. Real-Time TeachingFebruary 3, 2022 at 10:46 PM

    Informative and knowledgeable content. Keep up this work in your further blog.
    Online UI Development Training in Hyderabad
    Online RPA Training in Hyderabad
    Online Python Training in Hyderabad
    Online Mean Stack Training in Hyderabad

    ReplyDelete
  3. syedhaseebOctober 6, 2022 at 9:59 AM

    Dolby Atmos 3.13.249.0 Crack License Key Download 2022 ; Increase your sea bass and turnips. Listen to high-quality songs. Connect the Dolby Home .Dolby Atmos Crack 2022

    ReplyDelete
  4. techOctober 6, 2022 at 10:55 AM

    Be strong and courageous. Do not fear or be in dread of them, for it is the LORD your God who goes with you. He will not leave you or forsake .Bible Verse About Encouraging Others

    ReplyDelete

Post a Comment

Popular posts from this blog

Office 365 User unable to book room on-premise in Exchange Hybrid environment

-
In a federated environment, an Office 365 user was unable to book meeting in room which was on-premise. After tracing the messages created for booking the room, it was confirmed that the message indeed reached but the room was rejecting it for some reason. The room was rejecting the meeting request as it was considering the Office 365 user as an external user. So to solve this, we need to run the following command in the On-premise Exchange environment if we want to allow all the rooms: Get-Mailbox | where {$_.RecipientTypeDetails -like "Roommailbox"}| Get-CalendarProcessing | Set-CalendarProcessing -ProcessExternalMeetingMessages $true For single room, run the following command: Get-CalendarProcessing -Identity <Room name> | Set-CalendarProcessing -ProcessExternalMeetingMessages $true  Now the Office 365 user will be able to book the on-premise meeting room. (This is assuming that the free/busy calendar sharing is already enabled in the federated environme...
Read more

Fluentd error: Unable to push logs to [elasticsearch]

-
After application deployments, Kibana stopped showing logs exactly after 7 days. The error "Fluentd error: Unable to push logs to [elasticsearch]" was shown in the fluentd logs. The initial response was to increase the buffer limits for fluentd as follows: chunk_limit_size 10M queue_limit_length 256 The behavior occurred again after two weeks, which led to the same error. On closer investigation, the error was preceded by the statement "Failed to write to the buffer." This led me to inspect the fluentd configuration again and found the following code in the buffer part which caused the fluentd buffers to be filled as per the official documentation on Fluentd : overflow_action block The fix for this overflow_action is to change from block to drop_oldest_chunk, allowing the fluentd logs to flow seamlessly to the elastic search by dropping the oldest logs in the buffer.   <buffer> @type file path /var/log/fluentd-buffers/kubernet...
Read more