Skip to content

Conversation

@hemanth5544
Copy link
Contributor

❗ Important Announcement

Click here for more details:

⚠️ Please Note: We do not accept all types of pull requests, and we want to ensure we don’t waste your time. Before submitting, make sure you have read our pull request guidelines: Pull Request Rules

🚧 Temporary Delay in Feature Requests and Pull Request Reviews

At this time, we may be slower to respond to new feature requests and review pull requests. Existing requests and PRs will remain in the backlog but may not be prioritized immediately.

  • Reason: Our current focus is on addressing bugs, improving system performance, and implementing essential updates. This will help stabilize the project and ensure smoother management.
  • Impact: While no new feature requests or pull requests are being outright rejected, there may be significant delays in reviews. We encourage the community to help by reviewing PRs or assisting other users in the meantime.
  • What You Can Do: If you're interested in contributing, reviewing open PRs by following our Review Guidelines or offering support to other users is greatly appreciated. All feature requests and PRs will be revisited once the suspension period is lifted.

We appreciate your patience and understanding as we continue to improve Uptime Kuma.

🚫 Please Avoid Unnecessary Pinging of Maintainers

We kindly ask you to refrain from pinging maintainers unless absolutely necessary. Pings are reserved for critical/urgent pull requests that require immediate attention.

Why: Reserving pings for urgent matters ensures maintainers can prioritize critical tasks effectively.


📋 Overview

  • What problem does this pull request address?
    Uptime Kuma currently lacks support for RTSP (Real Time Streaming Protocol) monitoring, which is important for users monitoring IP cameras and similar devices.

  • What features or functionality does this pull request introduce or enhance?
    This PR introduces RTSP-related fields to the monitor table to store credentials and stream path, allowing RTSP monitors to be configured in the future:

    • rtsp_username
    • rtsp_password
    • rtsp_path

🔗 Related Issues


🔄 Changes

🛠️ Type of change

  • ✨ New feature (a non-breaking change that adds new functionality)
  • 🐛 Bugfix (a non-breaking change that resolves an issue)
  • ⚠️ Breaking change (a fix or feature that alters existing functionality in a way that could cause issues)
  • 🎨 User Interface (UI) updates
  • 📄 New Documentation (addition of new documentation)
  • 📄 Documentation Update (modification of existing documentation)
  • 📄 Documentation Update Required (the change requires updates to related documentation)
  • 🔧 Other (please specify):

📄 Checklist

  • 🔍 My code adheres to the style guidelines of this project.
  • ✅ I ran ESLint and other code linters for modified files.
  • 🛠️ I have reviewed and tested my code.
  • 📝 I have commented my code, especially in hard-to-understand areas (e.g., using JSDoc for methods).
  • ⚠️ My changes generate no new warnings.
  • 🤖 My code needed automated testing. I have added them (this is an optional task).
  • 📄 Documentation updates are included (if applicable).
  • 🔒 I have considered potential security impacts and mitigated risks.
  • 🧰 Dependency updates are listed and explained.
  • 📚 I have read and understood the Pull Request guidelines.

hostname:"807e9439d5ca.entrypoint.cloud.wowza.com",
port:"1935",

rtsp_username: "807e9439d5ca",
rtsp_password: "",
rtsp_path: "/app-rC94792j/068b9c9a_stream2",

use this smaple details to check

📷 Screenshots or Visual Changes

  • UI Modifications: None
  • Before & After: No visible UI changes. This is a backend database migration.
Event Before After
Monitor Table No RTSP-related fields Added rtsp_username, rtsp_password, rtsp_path

image

Copy link
Collaborator

@CommanderStorm CommanderStorm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work. 👍🏻

Could you add a testcase to ensure that there are no regressions with this monitoring type?
Doing so greatly increases the stability of this montior by preventing for example bad depenecy bumps, ... breaking you.


<template v-if="monitor.type === 'rtsp'">
<div class="my-3">
<label for="rtspUsername" class="form-label">RTSP {{ $t("Username") }}</label>
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please translate always with full translation keys.
=> "RTSP-Username" instead of excluding RTSP.

There are Left to right and right to left languages and we don't want to cause our translators more work in this department

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@CommanderStorm, I was intentionally trying to exclude "RTSP" from the label — similar to how the MQTT type works. The username and other keywords are already using translations.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that was a mistake for MQTT then which was missed.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hey @CommanderStorm can you guide me how to use weblate to add a new word

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shure.

You just add every translation that should become avaliable on weblate to en.json and once merged, our awsome army of translators can translate this.
Important: only add things to en.json, all other translations have to go via weblate to prevent merge conflicts.

</div>
<div class="my-3">
<label for="rtspPath" class="form-label">RTSP {{ $t("path") }}</label>
<input id="rtspPath" v-model="monitor.rtspPath" type="text" class="form-control">
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do these have a typical format? if yes, could you add a placeholder or helptext?

What a path is, might otherwise not be very self-explainatory without extra docs.

@CommanderStorm CommanderStorm changed the title Rtsp monitor RTSP monitor Jun 28, 2025
@CommanderStorm CommanderStorm added the pr:please address review comments this PR needs a bit more work to be mergable label Jun 28, 2025
@hemanth5544
Copy link
Contributor Author

@CommanderStorm any other changes are required ?

@CommanderStorm
Copy link
Collaborator

I am going to review it once you are done with the changes that I requested originally.

There are a few open things, such as the database layout or HiddenInput.

@CommanderStorm CommanderStorm added pr:needs review this PR needs a review by maintainers or other community members pr:please address review comments this PR needs a bit more work to be mergable and removed pr:please address review comments this PR needs a bit more work to be mergable pr:needs review this PR needs a review by maintainers or other community members labels Aug 4, 2025
@CommanderStorm CommanderStorm marked this pull request as draft August 4, 2025 12:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

needs:resolve-merge-conflict pr:please address review comments this PR needs a bit more work to be mergable

Projects

None yet

Development

Successfully merging this pull request may close these issues.

RTSP (Real Time Streaming Protocol)) support

2 participants