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

Performance Concerns with SC4S Dashboard (Proposal update attached) #2552

Closed
makal27 opened this issue Aug 8, 2024 · 4 comments
Closed

Performance Concerns with SC4S Dashboard (Proposal update attached) #2552

makal27 opened this issue Aug 8, 2024 · 4 comments
Assignees
Labels
enhancement New feature or request

Comments

@makal27
Copy link

makal27 commented Aug 8, 2024

Was the issue replicated by support?
No

What is the sc4s version ?
3.28.1

Which operating system (including its version) are you using for hosting SC4S?
Rocky Linux 8.10 (Green Obsidian)

Which runtime (Docker, Podman, Docker Swarm, BYOE, MicroK8s) are you using for SC4S?
Docker

Is there a pcap available? If so, would you prefer to attach it to this issue or send it to Splunk support?
N/A

Is the issue related to the environment of the customer or Software related issue?
Software

Is it related to Data loss, please explain ?
No

Last chance index/Fallback index?
N/A

Is the issue related to local customization?
No

Do we have all the default indexes created?
N/A

Describe the bug

Certain Dashboard panels could leverage tstats to accomplish the same task, drastically improving performance and reducing resource usage.

To Reproduce
Sample new Dashboard XML attached.

sc4s_dashboard_proposal.TXT

@makal27 makal27 changed the title Performance Concerns with SC4S Dashboard (Fix Provided) Performance Concerns with SC4S Dashboard (Proposal update attached) Aug 8, 2024
@cwadhwani-splunk cwadhwani-splunk self-assigned this Aug 12, 2024
@cwadhwani-splunk cwadhwani-splunk added the enhancement New feature or request label Aug 12, 2024
@cwadhwani-splunk
Copy link
Collaborator

Hi @makal27

The suggestion is greatly appreciated. We will look into it and will take further actions.

@mstopa-splunk
Copy link
Contributor

Hello @makal27 I have your changes in #2592 and will merge them in 3-4 weeks in the second new release from now, but would you like to submit a PR on your own for the credit?

@makal27
Copy link
Author

makal27 commented Sep 19, 2024

@mstopa-splunk I appreciate the offer; I'll defer to your standard procedures. Thank you!

@mstopa-splunk
Copy link
Contributor

sure, thank you for your contribution!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants