Overall Satisfaction with Splunk Infrastructure Monitoring
1.
Determine what custom logs you wish to capture.
2.
Note and document the paths that the logs are located.
3.
Note and document the hosts that contain those logs (IP, short hostname,
FQDN)
4.
Gather sample log files
5.
Check for application guidance for Splunk ingest (i.e. iis
logs require a specific configuration so that logs are readable inside Splunk,
some application can utilize http event collector, etc.)
Determine what custom logs you wish to capture.
2.
Note and document the paths that the logs are located.
3.
Note and document the hosts that contain those logs (IP, short hostname,
FQDN)
4.
Gather sample log files
5.
Check for application guidance for Splunk ingest (i.e. iis
logs require a specific configuration so that logs are readable inside Splunk,
some application can utilize http event collector, etc.)
- Logging
- Log Forwarding
- Monitoring
- Improve search latency
- Ability to export data using other apps
- Ways to remove IP's when exporting data
- No experience with SignalFX
It's able to quickly detect and resolve issues across the entire spectrum of deployments including on-premises, public cloud, private cloud, hybrid cloud and multicloud
Do you think Splunk Infrastructure Monitoring delivers good value for the price?
Yes
Are you happy with Splunk Infrastructure Monitoring's feature set?
Yes
Did Splunk Infrastructure Monitoring live up to sales and marketing promises?
I wasn't involved with the selection/purchase process
Did implementation of Splunk Infrastructure Monitoring go as expected?
Yes
Would you buy Splunk Infrastructure Monitoring again?
Yes