Overview

opsverse's observability stack (observenow) brings together your telemetry ( metrics , logs , and apm traces ) under one umbrella supported observability signals 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 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 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 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 agent please see the install the opsverse agent https //docs opsverse io/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 integrations 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 infrastructure the underlying tools and apps upon which your product level applications are running (e g , kubernetes, postgresql, mongodb, etc) cloud providers the base providers for your infrastructure's virtual hardware and managed services (e g , aws, gcp, azure, etc) applications 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) extending with custom instrumentation 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 prometheus instrumentation https //prometheus io/docs/practices/instrumentation/ prometheus client libraries https //prometheus io/docs/instrumenting/clientlibs/