Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Time-based browsing of Instance logs #5301

Open
knolleary opened this issue Mar 12, 2025 · 0 comments
Open

Time-based browsing of Instance logs #5301

knolleary opened this issue Mar 12, 2025 · 0 comments
Labels
customer request requested by customer feature-request New feature or request that needs to be turned into Epic/Story details headline Something to highlight in the release size:M - 3 Sizing estimation point
Milestone

Comments

@knolleary
Copy link
Member

knolleary commented Mar 12, 2025

Description

We currently show the latest Node-RED logs to the user and they can click 'earlier' to go back in time.

If the user sees an audit-log entry about an unexpected NR event, they may want to check the logs (in fact, some audit log entries tell the user to check the logs).

Clicking 'earlier' a lot is tedious and slow. A user should be able to browse to a given time in the logs and jump straight there.

Note: we only keep a fixed buffer size of logs within the launcher that affects how much history is available; meaning a noisy NR instance will have a shorter duration of available logs. That's a separate matter for now.

Which customers would this be available to

Everyone - CE/Starter/Team/Enterprise

Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate

@knolleary knolleary added feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do size:M - 3 Sizing estimation point labels Mar 12, 2025
@knolleary knolleary added the customer request requested by customer label Mar 12, 2025
@joepavitt joepavitt moved this to Scheduled in ☁️ Product Planning Mar 12, 2025
@joepavitt joepavitt moved this to Todo in 🛠 Development Mar 12, 2025
@joepavitt joepavitt added this to the 2.16 milestone Mar 12, 2025
@joepavitt joepavitt added headline Something to highlight in the release and removed needs-triage Needs looking at to decide what to do labels Mar 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer request requested by customer feature-request New feature or request that needs to be turned into Epic/Story details headline Something to highlight in the release size:M - 3 Sizing estimation point
Projects
Status: Scheduled
Status: Todo
Development

No branches or pull requests

2 participants