Splunk Enterprise

Why is "times.conf disabled=1" no longer working in Splunk 7.1?

simpkins1958
Contributor

For our splunk simple xml application we have a times.conf that disables certain time options for all our dashboards. This is no longer working on Splunk 7.1.0 was working as expected in 7.0.x. Anyway to get this functionality in 7.1 working?

times.conf:

[real_time_all]
disabled = 1

[real_time_last1h]
disabled = 1

[real_time_menu]
disabled = 1

[real_time_last30s]
disabled = 1

[real_time_last30m]
disabled = 1

[real_time_last5m]
disabled = 1

[real_time_last1m]
disabled = 1

[year_to_date]
disabled = 1

[previous_year]
disabled = 1
0 Karma

jkat54
SplunkTrust
SplunkTrust

I don’t even see the disabled option in times.conf.spec for 7.1 or 7.0.

Still believe it worked for you previously. Where did you put your custom times.conf?

Did you put it in etc/system/local?

0 Karma

somesoni2
Revered Legend
0 Karma

simpkins1958
Contributor

From splunk webui disabled "Previous Month" which added a times.conf file to etc\system\local with:

[previous_month]
disabled = 1

The simple XML timepicker is still showing "Previous month" as a selection. Tried restarting splunk and still seeing.

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

Are you leveraging automation to its fullest potential in your threat detection strategy?Our upcoming Security ...

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...