Handbook Help Center
Home Website
Home
Categories
⭐ Marketing
  • Brand Guidelines
  • [Guidelines] Taking product screenshots/screencasts
  • Super Chat's Marketing Playbook
  • How to add blog posts to Super Chat?
🏢 Company
  • History of Super Chat
  • Investors
🚴‍♂️ Culture
  • Communication
🎨 Design
  • Guidelines
👩‍💻 Engineering
  • Frontend Guidelines
  • Swagger Documentation
  • Pull Request Guidelines
  • Scheduled maintenance
  • Engineering FAQ
  • Release Process
  • Best Practices
  • Features FAQ
  • How do push notifications work in Super Chat?
  • Speed up your local development workflow with Make
  • Runbooks
  • Translation Guidelines
  • Backend Guidelines
💸 Enterprise Edition
  • Developing Enterprise Edition Features
🚣‍♀️ Processes
  • Triaging an issue - Labels, Weights
  • Product - Guidelines
  • Account Suspension & Restoration
  • Reporting scams to Super Chat
Home 👩‍💻 Engineering Runbooks

Runbooks

Open in
View as Markdown
Open in ChatGPT Open in Claude
Vishnu

Vishnu

Last updated on Mar 5, 2024

How to respond to low-logs alert? (p0)

This might be due to the Nimbus log forwarding system.

To bypass Nimbus and forward logs directly, remove the Nimbus log drain from the Heroku app. (This is to avoid logs duplication when/if Nimbus is back online )

Set NEWRELIC_LOGS_FORWARDING_ENABLED environment variable to true for Super Chat Heroku app.

Back to Engineering