On-Premise Overview
You can run Atatus in your own environment (on-premises, hybrid or BYOC) when you need full control over your observability data. This page covers the on-premise setup for Atatus agents. This solution is ideal for businesses with strict compliance, data sovereignty, or security requirements that restrict sending telemetry data to the cloud.Why Use On-Premise?
- 🔒 Data Privacy & Security: Keep all monitoring data within your private network.
- 🏢 Compliance: Meet regulatory standards (e.g., GDPR, HIPAA, SOC 2).
- 🚀 Performance: Reduce latency by hosting the observability backend closer to your services.
- ⚙️ Custom Control: Fully control scaling, backups, and integrations.
How to Get On-Premise
To get access to the on-premise version of Atatus:- Contact Support: Email success@atatus.com or reach out via the dashboard.
- Get Installation Package: You’ll receive a Docker-based deployment package.
- Install & Configure: Follow the installation guide provided.
- Replace Endpoint URLs in agents as shown below.
Agent Endpoint Configuration
To connect your services to the on-premise Atatus instance, you must update the Atatus agent configurations by replacing:YOUR_ON_PREMISE_DOMAIN→ your Atatus on-premise server URLYOUR_APP_NAME→ the name of your monitored appYOUR_LICENSE_KEY→ You’ll find your license key in the Atatus dashboard during onboarding.
https://atatus-observability.mycompany.compayment-servicelic_apm_8deff58f1ca9a05b1ad30185
Infra Agent
File:/etc/atatus-infra-agent/atatus.yml
Python Agent
File:settings.py
Node.js Agent
Create anatatus.js file in your project root:
-r flag:
Ruby Agent
File:config/atatus.yml
PHP Agent
1. Find the config path:atatus.ini:
Java Agent
.NET Agent
Option 1:appsettings.json
ASP .NET Agent
Option 1:Web.config
Go Agent
Docker Monitoring
Kubernetes Monitoring
File:atatus_values.yaml
Browser Agent
OpenTelemetry Collector
File:otelcol-config-extras.yml