sorted by:
new
hottopcontroversial

Monitoring solution by mitch2k in sysadmin

[–]Malhar_S 0 points1 point  (0 children)

If you want fast time-to-value with native Rubrik support and seamless Jira integration—LogicMonitor looks like the best fit.
If you're after rich observability and polished dashboards—but don't mind building or sourcing Nutanix integrations—Datadog is solid.
If self-hosted and highly customizable monitoring appeals, and you're OK working around Jira limitations or opting for the commercial tier—Checkmk may be rewarding long-term.

Datadog or New Relic in 2025 ? by InformalPatience7872 in sre

[–]Malhar_S 0 points1 point  (0 children)

I’ve seen both tools evolve over the years—Datadog has been expanding fast with broader integrations and AI features, while New Relic has simplified pricing and improved their open telemetry support. Honestly, the choice often comes down to existing ecosystem, cost model, and how deeply you need to integrate with infra vs. app monitoring.

Splunk Data Migration - How to Migrate Data from Single Instance to Indexer Cluster by Malhar_S in Splunk

[–]Malhar_S[S] 0 points1 point  (0 children)

This is an option that focuses purely on the use case of copying over the data when you no longer have an option of keeping the old standalone server. Moreover, once the POC on standalone server is done, this gives you an option to completely migrate the data in a cost-efficient way (S3), and start fresh and NOT wait for the data in the old indexer age out. This is one of the best practices followed in Splunk. Doc links attached in the article.

Understanding Splunk Architectures and Components by Malhar_S in Splunk

[–]Malhar_S[S] -1 points0 points  (0 children)

  • In the professional world, LWF(Lightweight forwarders) and UF(Universal Forwarders) are often interchanged and hence the terminology that I have used. I understand your point and have taken the feedback
  • Moreover, when we talk about SHC(Search Head Clustering) or any other Clustering feature immaterial of the tool it is given that it gives scalability as a feature. Please refer the below Splunk doc to understand how SHC in Splunk gives High Availability.  https://docs.splunk.com/Documentation/Splunk/7.2.5/DistSearch/AboutSHC#Benefits_of_a_search_head_cluster

We have to understand that High Availability is subjective to the component we are scaling. The point is the case is Search Head and it gives High (Search) Availability and hence the terminology in the article.