Logit.io
Platform

Multiple Kibana Instances

Run as many isolated Kibana instances as you require, side by side with support for multiple versions by using Logit.io

observability stack
Ingest
Correlate
Visualize
Act
Logs
Logstash · OpenSearch
12.4k/s
Metrics
Prometheus · Grafana
10k series
APM
OTLP · traces
p95 84ms
--:--:-- INFO request.completed duration_ms=42 route="/api/v1/orders"
--:--:-- WARN latency.spike service=checkout p95=820ms threshold=500ms
--:--:-- INFO trace.exported spans=128 backend=jaeger status="ok"
--:--:-- INFO metric.scrape target=prometheus job=k8s-pods samples=8421
--:--:-- INFO log.shipped bytes=184032 index=logs-prod
--:--:-- WARN auth.failure ip=203.0.113.42 attempts=3 action=rate_limit
--:--:-- INFO alert.routed severity=high channel="#incidents" dedupe=on
--:--:-- INFO dashboard.refresh uid=ops-overview panels=14 cache=hit
--:--:-- ERROR disk.pressure node=worker-3 usage=92% reclaim=started
--:--:-- INFO pipeline.batch size=2048 lag_ms=18 status=healthy
--:--:-- WARN queue.backpressure topic=ingest depth=1200
--:--:-- INFO otel.export endpoint=collector.svc spans_ok=512
--:--:-- INFO search.query hits=1284 took_ms=37 index=logs-*
--:--:-- INFO retention.policy applied hot=14d warm=30d
--:--:-- WARN tls.cert.expiring host=ingest.logit.io days=12
--:--:-- INFO ha.failover check region=eu-west status=ready
--:--:-- INFO request.completed duration_ms=42 route="/api/v1/orders"
--:--:-- WARN latency.spike service=checkout p95=820ms threshold=500ms
--:--:-- INFO trace.exported spans=128 backend=jaeger status="ok"
--:--:-- INFO metric.scrape target=prometheus job=k8s-pods samples=8421
--:--:-- INFO log.shipped bytes=184032 index=logs-prod
--:--:-- WARN auth.failure ip=203.0.113.42 attempts=3 action=rate_limit
--:--:-- INFO alert.routed severity=high channel="#incidents" dedupe=on
--:--:-- INFO dashboard.refresh uid=ops-overview panels=14 cache=hit
--:--:-- ERROR disk.pressure node=worker-3 usage=92% reclaim=started
--:--:-- INFO pipeline.batch size=2048 lag_ms=18 status=healthy
--:--:-- WARN queue.backpressure topic=ingest depth=1200
--:--:-- INFO otel.export endpoint=collector.svc spans_ok=512
--:--:-- INFO search.query hits=1284 took_ms=37 index=logs-*
--:--:-- INFO retention.policy applied hot=14d warm=30d
--:--:-- WARN tls.cert.expiring host=ingest.logit.io days=12
--:--:-- INFO ha.failover check region=eu-west status=ready
+ one managed platform
+ peak overage protection
! bundle up to 30% off

Trusted by engineering teams worldwide

Maersk
Murphy
Ringier
GDS
Guesty
HackerRank
Equal Experts
DevEx
Digitale Medier
xneelo
CAA
Pivotal
Robomed Network
Neoway
Gomo Learning
Department for BEIS
IBM
Broad Institute
The Honest Company
Traels
De Banke
Dofinity
BioCatch
Kainos
Youredi
Flux Music
Goji
Ving
HypSports
Boston Logic
Double Jump

Logit.io gives you the ability to run as many isolated Kibana instances as you require, side by side with support for multiple versions. You have complete control as to when to upgrade your ELK stacks to the particular version you require.

Proactive security alerting is critical to an organisation, getting notified when someone is trying to gain unauthorised access to your systems, requires immediate attention by your team. Not only does this protect your organisation and ensure you stay compliant, but it helps everyone to sleep easily at night.

Benefits of Running Multiple Kibana Instances

With multiple Kibana instances, you can create custom dashboards, visualizations, and workflows tailored to the unique requirements of different teams or departments. Whether it's marketing, sales, IT, or operations, each team can have its own dedicated Kibana instance configured to display the most relevant metrics and data, ensuring a personalized user experience that enhances productivity and decision-making.

Maintain strict control over data access and permissions by deploying separate Kibana instances for different user groups or projects. With role-based access controls (RBAC) and fine-grained permissions, you can restrict access to sensitive information and ensure compliance with regulatory requirements such as GDPR, HIPAA, and PCI DSS.

Distribute the load and optimize performance by deploying multiple Kibana instances across your infrastructure. By spreading the workload across multiple instances, you reduce the risk of performance bottlenecks and ensure consistent responsiveness, even during periods of high usage or data processing.

pipeline
Ingest
Parse
Index
Query
+streams normalized · schema applied
output ready for search, alerts, and dashboards

Multi-Stack Kibana

Logit.io gives you the freedom to display multiple Kibana dashboards, for all your organisation's stacks, in a single browser session. This flexibility allows for side-by-side comparisons and gives complete visibility even when your dashboards are combined on larger displays in mission control setups.

stream
--:--:-- INFO request.completed duration_ms=42 route="/api/v1/orders"
--:--:-- WARN latency.spike service=checkout p95=820ms threshold=500ms
--:--:-- INFO trace.exported spans=128 backend=jaeger status="ok"
--:--:-- INFO metric.scrape target=prometheus job=k8s-pods samples=8421
--:--:-- INFO log.shipped bytes=184032 index=logs-prod
--:--:-- WARN auth.failure ip=203.0.113.42 attempts=3 action=rate_limit
--:--:-- INFO alert.routed severity=high channel="#incidents" dedupe=on
--:--:-- INFO dashboard.refresh uid=ops-overview panels=14 cache=hit
--:--:-- ERROR disk.pressure node=worker-3 usage=92% reclaim=started
--:--:-- INFO pipeline.batch size=2048 lag_ms=18 status=healthy
--:--:-- WARN queue.backpressure topic=ingest depth=1200
--:--:-- INFO otel.export endpoint=collector.svc spans_ok=512
--:--:-- INFO search.query hits=1284 took_ms=37 index=logs-*
--:--:-- INFO retention.policy applied hot=14d warm=30d
--:--:-- WARN tls.cert.expiring host=ingest.logit.io days=12
--:--:-- INFO ha.failover check region=eu-west status=ready
--:--:-- INFO request.completed duration_ms=42 route="/api/v1/orders"
--:--:-- WARN latency.spike service=checkout p95=820ms threshold=500ms
--:--:-- INFO trace.exported spans=128 backend=jaeger status="ok"
--:--:-- INFO metric.scrape target=prometheus job=k8s-pods samples=8421
--:--:-- INFO log.shipped bytes=184032 index=logs-prod
--:--:-- WARN auth.failure ip=203.0.113.42 attempts=3 action=rate_limit
--:--:-- INFO alert.routed severity=high channel="#incidents" dedupe=on
--:--:-- INFO dashboard.refresh uid=ops-overview panels=14 cache=hit
--:--:-- ERROR disk.pressure node=worker-3 usage=92% reclaim=started
--:--:-- INFO pipeline.batch size=2048 lag_ms=18 status=healthy
--:--:-- WARN queue.backpressure topic=ingest depth=1200
--:--:-- INFO otel.export endpoint=collector.svc spans_ok=512
--:--:-- INFO search.query hits=1284 took_ms=37 index=logs-*
--:--:-- INFO retention.policy applied hot=14d warm=30d
--:--:-- WARN tls.cert.expiring host=ingest.logit.io days=12
--:--:-- INFO ha.failover check region=eu-west status=ready

The Logit.io ELK Stack

  • Each Logit.io ELK stack has its own dedicated resources, featuring highly available Elasticsearch, Logstash and Kibana instances.
  • All Logit.io ELK stacks are customisable to meet your team's needs reducing friction and increasing the effectiveness of your logging and metrics management.
  • Running production ELK stacks on the Logit.io platform allows you to reduce the total cost of ownership (TCO) of your logging and metrics solution.
shell
$
logit trace export --protocol=otlp --backend=jaeger
→ distributed spans indexed · p99=84ms

Companies Feel The Difference When They Use Logit.io

Internally, Logit.io has made it easier for us to provide better support for our customers, since finding individual messages based on various data in the payload has become easier.

At Youredi, pretty much everyone from our technical support teams through to our professional services teams uses Logit.io.

Youredi

Mats von Weissenberg

CTO @ Youredi

Start your 14-day free trial

No credit card required. Managed OpenSearch, Prometheus, and Grafana from $25/mo.