Self-hosting
Run the slaOS indexer on your own infrastructure
The self-hosted solution allows you to run the slaOS indexer on your own infrastructure, providing greater control over your data. This option is ideal for organizations with strict data locality requirements or those who prefer to manage their own infrastructure.
System requirements
Minimum
XCPU cores,XGBRAMXXXGBstorage (scalable based on data volume)Network access to your data sources and slaOS API endpoints
Setting up the self-hosted solution
Download the Docker Image: Obtain the slaOS indexer from our repository.
Install the Indexer: Deploy the indexer on your infrastructure, whether it’s Docker, Kubernetes, or a bare-metal environment.
Configure the Indexer: Modify the configuration file in YAML format to suit your specific data sources and slaOS account details. Here's a sample configuration:
Configuration file example
inputs:
- integration: cloudwatch
integration_prefix: "cloudwatch_logs_test"
type: logs
cloudwatch:
region: us-east-1
aws_access_key_id: AKIAXXXXX
aws_secret_access_key: X/XXX+XXX
logs_config:
log_group_name: "/aws/apprunner/prod-rated-api/"
filter_pattern: '{ $.event = "request_finished" }'
filters:
version: 1
log_format: json_dict
fields:
- key: "status_code"
field_type: "integer"
path: "status_code"
- key: "customer_id"
field_type: "string"
path: "user.id"
- key: "path"
field_type: "string"
path: "request_route_name"
offset:
type: redis
override_start_from: true
start_from: 1724803200000
start_from_type: bigint
redis:
host: redis
port: 6379
db: 0
output:
type: "console"
console:
verbose: true
secrets:
use_secrets_manager: false
Start the Indexer: Launch the indexer and verify data ingestion via the slaOS dashboard.
Always refer to the most up-to-date documentation available on our GitHub repository for detailed setup instructions and best practices.
Last updated

