Great monitoring tool for web application and API tools
Updated February 28, 2023

Great monitoring tool for web application and API tools

Anonymous | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User

Software Version

SignalFx Infrastructure Monitoring

Overall Satisfaction with Splunk Infrastructure Monitoring

As the engineering team, we use Splunk Infrastructure Monitoring mainly to monitor the application usage and system load (DevOps) together. We do share some metrics with other teams within the organization (marketing, BizDev, Product, and so on) mainly to understand our user usage and main flow.

Pros

  • Easy integration with the code and infrastructure.
  • Easy to define new (and complex) metrics.
  • Advance alerts mechanize.

Cons

  • Better integration with our clients (native mobile clients SDKs will be great).
  • A way to easily tag filters and move them across metrics/formula.
  • Alert system to easy false [alarm] and hard to configure.
  • Be able to have group more dimensions (and have more values on each).
  • Splunk Infrastructure Monitoring helps us to detect and monitor potential problem[s] (before they happen).
  • Splunk Infrastructure Monitoring helps us to fatly understand [the] root cause of a problem in the system (when we have the right metrics),.
  • We can't easily monitor our client usage with Splunk Infrastructure Monitoring.
Being a SAS reduce[s] our infrastructure is the main reason for using Splunk Infrastructure Monitoring.

Do you think Splunk Observability Cloud delivers good value for the price?

Yes

Are you happy with Splunk Observability Cloud's feature set?

Yes

Did Splunk Observability Cloud live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Splunk Observability Cloud go as expected?

Yes

Would you buy Splunk Observability Cloud again?

Yes

We do monitor our infrastructure using Splunk Infrastructure Monitoring, and it is the main reason and purpose of using it.
IMO ramping up my team and understand Splunk Infrastructure Monitoring is not an easy task. However, managing the quotas and team management is relatively easy.
We do get [too] many false alarms when we usage outlier detection and smart monitoring. Those days we prefer to use more [simple] alerting mechanized (which are pretty sad). I hope that while receiving alarms I'll be able to set it as "false alarm" so Splunk Infrastructure Monitoring algorithm will not trigger on those cases again.
Monitor our application usage and system load.

Using Splunk Infrastructure Monitoring

20 - Software engineers - monitor app usage (business), internal errors and usage, and performance monitor. DevOps team - monitor hardware infrastructure usage and outbreak.Product team - platform usage and
3 - DevOps for operation issues and contact Splunk for issues
Dev for integration issues and API changes (rare that we have issue here)
  • Infrastructure monitor
  • Performance monitor
  • API and Application usage
  • Software flows dashboard
  • Business usage which includes performance metrics
  • Dashboard with cross dimension filtering
  • Delay metric reporting to reduce reporting overhead (due to luck of library)
  • Automate API reporting
  • More hardware and performance reporting
  • business development reporting
Good:
Stable system with low error rate
Easy to use for simple use cases

Bad:
UI is not very clear for complex usage
Mobile view (when logged in from phone) is bad
No library for .net

Comments

More Reviews of Splunk Observability Cloud

  1. Home
  2. Observability Tools
  3. Splunk Observability Cloud Reviews
  4. User Review of Splunk Observability Cloud