Website logo
Request featuresJoin Our Community
⌘K
KloudMate
Getting Started
Why KloudMate?
Setting Up KloudMate
Getting Help
KloudMate Infinity - Tech. Specs.
Homepage
Dashboards
Creating a Dashboard
Managing Dashboards and Panels
KloudMate Metrics
Explore
Lambda Functions
Log Management
Log Explorer
CloudWatch Logs
OpenTelemetry Logs
Traces
Issues
OpenTelemetry Support
What Is OpenTelemetry?
How Does OpenTelemetry Work?
OpenLLMetry: OpenTelemetry-based Observability for LLMs
LLM Observability with KloudMate and OpenLLMetry
Sending Data to KloudMate
Installing the OpenTelemetry Collector
Using OpenTelemetry Collector
Using OpenTelemetry SDKs
Service Integration Guides
Incident Management
What Is Incident Management?
Overview
Incident Lifecycle
Incidents
Services
Escalation Policy
Integrations
Slack Integration
Service Map
KloudMate - Real User Monitoring
What Is Real User Monitoring (RUM)?
Get Started With RUM
RUM Interface
Correlate RUM traces with OpenTelemetry backends
Alarms & Notifications
Understanding KloudMate Alarms
Setting Up KloudMate Alarms
Writing Expressions for KloudMate Alarms
Setting Up Notifications
Settings
Workspaces
Data Sources
Users & Permissions
Subscription & Billing
Usage Report
Profile & Security
Deleting Your AWS Account from KloudMate
Docs powered by Archbee
OpenTelemetry Support
...
Service Integration Guides
Server Metrics to KloudMate

Server Metrics to KloudMate Using Fluent-bit

1min

This document provides a guide on how to send metrics from Amazon EC2 instances/ Azure VMs / on-premise servers to KloudMate using Fluentbit.

In the described setup, the Node Exporter is responsible for exposing a diverse range of metrics related to hardware and the kernel. Its role involves exporting these metrics, which can then be collected and sent to the Kloudmate backend through Fluent bit.

Step 1: Prerequisites:

  • Fluentbit binaries and packages as per your system requirement.

Step 2: Configure fluentbit to send telemetry data to KloudMate.

Text
1[INPUT] 2 Name node_exporter_metrics 3 Tag node_metrics 4 Scrape_interval 30 5 6[OUTPUT] 7 name stdout 8 match * 9 10[OUTPUT] 11 Name opentelemetry 12 Match * 13 Host otel.kloudmate.dev 14 Port 4318 15 Metrics_uri /v1/metrics 16 Log_response_payload True 17 Tls On 18 Tls.verify Off 19 Header Authorization <Auth token> 20 # add user-defined labels 21 add_label service.name <Service Name> 22 add_label instance <instance name> 23


Step 3: After restarting the fluentbit service, the required metrics will be delivered to KloudMate.

Did this page help you?
PREVIOUS
Server Metrics to KloudMate Using Prometheus Node Exporter
NEXT
Server Metrics to KloudMate with Host Metrics Receiver
Docs powered by Archbee
Docs powered by Archbee