Overview
OpsVerse's Observability stack (ObserveNow) brings together your telemetry (metrics, logs, and APM traces) under one umbrella.
Metrics, logs, and traces are core observability signals. But to get further visibility into an entire Engineering organization, ecosystem, and developer experience, checkout the Backstage-powered OpsVerse ONE
Metrics are useful for describing the what and when something is happening and the trends in your applications. With metrics, you are able to see patterns, anomalies, and able to set thresholds for alerts on real-time usage.
For example, a metric for CPU usage percentage can show when your app begins using high CPU cycles. Or a metric for the total number of times users have signed into your app can be used to alert product owners when there's either a sudden surge or no new logins.
Logs are useful for describing the why something is happening in your application. Applications that spit out good logs can help pinpoint the exact cause of an issue. For example, if a metric show high CPU usage for an app, you can look at the apps logs to see what it's doing to help root cause
Traces, in this modern world of distributed services, help describe the where something is happening. For example, in modern systems, a request may traverse several different apps (frontend, backend, databases, etc), and it's important to trace that single request all the way through your services. If a specific service seems to be a bottleneck, traces help quickly identify which one.
Please see the Install the OpsVerse Agent section for details running the agent in your environment.
OpsVerse's agent can be used to collect telemetry from a variety of infrastructure and applications.
How to integrate more than just the default into ObserveNow!
Once installed, the Agent will send several default metrics, logs, and any enabled traces to your ObserveNow instance.
An Observability stack (like ObserveNow) provides the maximum value when telemetry from the underlying infrastructure (hosts, containers, DBs, K8s etc) is combined with telemetry from the applications.
The links to your left discuss how to integrate some popular applications specific to your environment
The underlying tools and apps upon which your product-level applications are running (e.g., Kubernetes, PostgreSQL, MongoDB, etc)
The base providers for your infrastructure's virtual hardware and managed services (e.g., AWS, GCP, Azure, etc)
The apps and services your team writes and deploys for your business - usually developed in a variety of programming languages and frameworks (e.g., Java, Go, Python, Node, etc)
The links to your left discuss the common ways to instrument applications for emitting custom telemetry.
Applications developed on various tech stacks can easily be instrumented to send metrics and traces to your ObserveNow backend.
In addition to left-side navigation links, the following documents provide general information on instrumentation: