Skip to main content

Documentation Index

Fetch the complete documentation index at: https://www.activepieces.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

​
Prerequisites:

​
Why On-Call?

We need to ensure there is exactly one person at the same time who is the main point of contact for the users and the first responder for the issues. It’s also a great way to learn about the product and the users and have some fun.
You can listen to Queen - Under Pressure while on-call, it’s fun and motivating.
If you ever feel burn out in middle of your rotation, please reach out to the team and we will help you with the rotation or take over the responsibility.

​
On-Call Schedule

The on-call rotation is managed through BetterStack, with each engineer taking a one-week shift. You can:
  • View the current schedule and upcoming rotations on BetterStack On-Call Schedule
  • Add the schedule to your Google Calendar using the calendar feed link from BetterStack
Make sure to update the on-call schedule in BetterStack if you cannot be available during your assigned rotation. This ensures alerts are routed to the correct person and maintains our incident response coverage.To modify the schedule:
  1. Go to BetterStack On-Call Schedule
  2. Find your rotation slot and create an override for your unavailable period
  3. Coordinate with the team to find coverage for your slot

​
What it means to be on-call

The primary objective of being on-call is to triage issues and assist users. It is not about fixing the issues or coding missing features. Delegation is key whenever possible. You are responsible for the following:
Friendly Tip #1: always escalate to the team if you are unsure what to do.

​
How do you get paged?

Monitor and respond to incidents that come through these channels:

​
Slack Fire Emoji (🔥)

When a customer reports an issue in Slack and someone reacts with 🔥, you’ll be automatically paged via BetterStack.

​
Automated Alerts

Watch for notifications from:
  • Digital Ocean about CPU, Memory, or Disk outages
  • BetterStack Monitors about website downtime or uptime failures
  • Playwright CI about e2e test failures