Runex

Feature · Operate & collaborate

Logs and metrics for every deployment.

Application monitoring shows what your app is doing right now: its logs, its resource use, and whether it's healthy. Runex streams build and runtime logs live, charts CPU and memory per app, and alerts you when a deploy fails.

Start deploying →How it works
  • Live build & runtime logs
  • CPU and memory charts
  • Failed-deploy alerts
logs · acme/api
build
✓ compiled · image pushed
runtime
GET /api/cart 200
cpu
34%
memory
212 MB / 512 MB
alerts
deploy failed → webhook
stream
live
logs & monitoringrunex

Definition

What is application monitoring?

Application monitoring is collecting an app's logs and metrics to see how it behaves and spot problems early.

Logs are the text your app and its build print: requests, errors, stack traces. Metrics are numbers over time, like CPU and memory use.

Runex collects both for every deployment. Build logs show why a build failed, runtime logs show what the running app is doing, and metrics show whether it's running out of resources.

Your app decides what gets logged. Write useful lines to standard output and standard error and Runex captures them, no logging agent to install.

How it works

How do logs and monitoring work on Runex?

Print to stdout; Runex does the rest.

  1. You

    Log to stdout

    Use console.log, print, or your logger.

  2. Runex

    Stream logs live

    Build and runtime logs, as they happen.

  3. Runex

    Chart resources

    CPU and memory per app, over time.

  4. Runex

    Alert on failures

    Failed deploys trigger a notification.

Benefits

Why do logs and metrics matter?

Find the bug before your users report it.

Debug failed builds

See the exact line where a build broke.

Watch requests live

Tail runtime logs while you test.

Spot resource limits

Memory creeping up? You'll see it early.

Know when deploys fail

Alerts reach you without watching a dashboard.

Compare

Logs vs metrics: what's the difference?

Logs tell you what happened; metrics tell you how much.

Logs vs metrics: what's the difference?
LogsMetrics
FormatLines of text with timestampsNumbers over time
AnswersWhat went wrong, and where?Is usage normal or climbing?
ExampleTypeError: cart is undefinedMemory at 480 MB of 512 MB
Use forDebugging a specific errorSpotting trends and limits

Example

Example: tracking down a memory leak

A slow API is traced to a memory leak using metrics first and logs second.

  1. Users report the API getting slower
  2. The memory chart climbs steadily since the last deploy
  3. Runtime logs show a cache that never clears
  4. The developer fixes the cache and pushes
  5. The new deploy ships; memory stays flat
  6. Failed-deploy alerts stay on for next time
logs-and-monitoring
memory
↑ steady growth
since
deploy #212
log hint
cache size 48,210 entries
fix
deploy #213
memory now
flat
illustrative namesrunex

FAQ

Questions developers ask

Short answers about logs & monitoring. More in the documentation.

Where do I find my app's logs?

In your deployment platform's dashboard. On Runex, each deployment has build logs and live runtime logs.

What should I log in a web app?

Requests, errors with stack traces, and key business events. Leave out secrets and personal data, and use log levels so you can filter noise.

What is the difference between monitoring and observability?

Monitoring watches known signals, like CPU or error counts. Observability is being able to ask new questions of your system from its logs, metrics, and traces.

How do I monitor a container's CPU and memory usage?

Use your platform's metrics. Runex charts CPU and memory for each app against its limits, so you know when to size up. If traffic is the cause, autoscaling can add instances instead.

Next step

Ship with logs & monitoring today.

Sign up, install the GitHub App, and deploy your first app. It's free to start.

Deploy with Runex →Getting started guide