TeskaLabs LogMan.io API Reference

Welcome to the TeskaLabs LogMan.io API documentation. Whether you're building integrations, automating workflows, or connecting external tools, this guide will help you get started with our APIs.

Getting Started

The LogMan.io API provides programmatic access to the same functionality available in the web interface. This means anything you can do through the UI (e.g. managing alerts, querying data, or configuring services) you can also accomplish through the API.

Authentication

To use the API, you'll need an API key. See the Authentication Guide for step-by-step instructions on how to obtain and use your key.

API Structure

LogMan.io follows a microservices architecture, where each service exposes its own API endpoints. This modular design allows for scalability and clear separation of concerns across different functional areas.

Service Discovery

LogMan.io uses asab-discovery microservice to manage and proxy API requests to microservices. This component keeps track of multiple running instances of each service, ensuring your requests are routed correctly even as services scale up or down.

API URL Pattern

When making API calls, use the following URL structure:

/api/asab-discovery/~/service_id/{service_name}/{endpoint_path}

Example: To call the GET /mycompany/ticket endpoint in the lmio-alerts service:

GET /api/asab-discovery/~/service_id/lmio-alerts/mycompany/ticket

This pattern routes your request through the discovery service to the appropriate microservice instance.

API Documentation

For detailed specifications of all available endpoints, request/response formats, and schemas, explore the interactive API reference documentation.