sampathshivakumar

Alerts - destinations

In OpenObserve (O2), Destinations enable users to set up notification channels for alert messages. These destinations define where and how notifications will be delivered when alerts are triggered. Destinations are reusable, allowing them to be associated with multiple alerts for efficient management.

The Destinations section provides two configuration options:

1. Webhook: Used for sending notifications to third-party systems via HTTP requests.
2. Email: Used for delivering notifications directly to email addresses.

Below is a detailed guide on how to configure both Webhook and Email destinations in OpenObserve.

---

sampathshivakumar

Contributing a Blog to the OpenObserve website4 Repository

Thank you for your interest in contributing to the OpenObserve blog! Please follow the steps below to write, preview, and submit your blog post.

Step 1: Fork the Repository

To contribute to the OpenObserve blog, begin by forking the repository:

1. Go to the OpenObserve GitHub repository.
2. Click the "Fork" button in the top-right corner. This will create a copy of the repository under your own GitHub account.

sampathshivakumar

#!/bin/bash
sudo swapoff -a

# Enable IPv4 packet forwarding
# sysctl params required by setup, params persist across reboots
cat <<EOF | sudo tee /etc/sysctl.d/k8s.conf
net.ipv4.ip_forward = 1
EOF

# Apply sysctl params without reboot

sampathshivakumar

Aurora
Declan
Penelope
Zara
Elijah
Isla
Mila
Sebastian
Adelaide
Mateo

sampathshivakumar

# Linux for DevOps Lab Setup
$setup_lab = <<SCRIPT

# Enable root login in ssh configuration

sed -i "s/^PermitRootLogin no/PermitRootLogin yes/g" /etc/ssh/sshd_config
sed -i "s/^PasswordAuthentication no/PasswordAuthentication yes/g" /etc/ssh/sshd_config
systemctl restart sshd
SCRIPT

sampathshivakumar

Vagrant.configure("2") do |config|

    config.vm.define "controlplane" do |controlplane|
      controlplane.vm.box = "ubuntu/jammy64"
      controlplane.vm.network "private_network", ip: "192.168.32.10"
      controlplane.vm.hostname = "controlplane"
      controlplane.vm.provider "virtualbox" do |vb|
          vb.memory = "2048"
          vb.cpus = 2
      end

sampathshivakumar

Continuous Deployment on AWS Elastic Beanstalk with Jenkins

what is AWS Elastic Beanstalk?

• AWS Elastic Beanstalk is a fully managed platform as a service (PaaS) offered by AWS for deploying and managing applications.
• It simplifies the process of deploying applications by abstracting away the underlying infrastructure details and providing an easy-to-use interface.
• With Elastic Beanstalk, developers can focus on writing their application code while AWS takes care of the deployment, capacity provisioning, load balancing, and automatic scaling.
• It supports a variety of programming languages and frameworks, including Java, .NET, PHP, Node.js, Python, Ruby, and Go.

Prerequisites

sampathshivakumar

Three-Tier Architecture in AWS Using Terraform

The three-tier architecture is the most popular implementation of a multi-tier architecture and consists of a single presentation tier, logic tier, and data tier.

The following illustration shows an example of a simple, generic three-tier application.

GitHub Repo:- https://github.com/sampathshivakumar/3-Tier-Architecture-Terraform

Resources need to be created are

• Custom VPC

sampathshivakumar

AWS Event Driven Architecture

What is AWS Event Driven Architecture ?

• AWS Event-Driven Architecture is an approach that utilizes Amazon Web Services to build scalable and decoupled applications.
• It relies on events as the primary means of communication between components.
• The architecture includes event sources that generate events, an event bus for routing events, rules to filter and route events, and targets for actions triggered by events.
• Event Driven Architecture offers benefits such as scalability, loose coupling, flexibility, and real-time processing.

Prerequisites

• AWS Account

sampathshivakumar

How to Build Serverless Web Application in AWS.

What is Serverless?

• Serverless computing is a cloud computing model where developers write and deploy code as individual functions or services without managing servers.
• The cloud provider takes care of infrastructure provisioning, scaling, and maintenance.
• Developers focus solely on writing code, and the platform automatically allocates resources and scales applications based on demand.

Why Serverless?

• serverless computing provides developers with a more streamlined and efficient development experience while delivering automatic scaling, cost savings, and improved agility.
• It is particularly beneficial for applications with varying workloads, sporadic usage patterns, and the need for rapid innovation.

Prerequisites.