Kibana deprecated settings

Hello,

Can you help me, how to get of rid of this deprecated setting in KIbana GUI under Upgrade asistant?
I Already removed these settings in my kibana.yml but it is still shwoing.

How to fix

  1. Remove the "xpack.reporting.index" setting.
  2. Reindex reports stored in a custom reporting index into the default ".reporting-*" indices or regenerate the reports to be able to access them in 8.0.

Should I do second step also ? And if YES how ?
i Dont have .reporting indicies

@ayounes could you please help me?

@elastic_team guys? I cannot upgrade to 8.0.0

Please be patient in waiting for responses to your question and refrain from pinging multiple times asking for a response or opening multiple topics for the same question. This is a community forum, it may take time for someone to reply to your question. For more information please refer to the Community Code of Conduct specifically the section "Be patient". Also, please refrain from pinging folks directly, this is a forum and anyone that participates might be able to assist you.

If you are in need of a service with an SLA that covers response times for questions then you may want to consider talking to us about a subscription.

It's fine to answer on your own thread after 2 or 3 days (not including weekends) if you don't have an answer.

Hello, as you can see there is only one line which is commented and the upgrade assistant still says to remove it.

grep -r xpack.reporting.index /etc/kibana/
/etc/kibana/kibana.yml:#xpack.reporting.index: ".reporting-*"

Did you restart Kibana?

Hi David,

yes multiple times.

Here is my kibana.yml config

# Disable newsfeed
newsfeed.enabled: false

# Kibana is served by a back end server. This setting specifies the port to use.
server.port: 5601

# Specifies the address to which the Kibana server will bind. IP addresses and host names are both valid values.
# The default is 'localhost', which usually means remote machines will not be able to connect.
# To allow connections from remote users, set this parameter to a non-loopback address.
server.host: "127.0.0.1"
server.publicBaseUrl: "http://xxx:5601"
# Enables you to specify a path to mount Kibana at if you are running behind a proxy.
# Use the `server.rewriteBasePath` setting to tell Kibana if it should remove the basePath
# from requests it receives, and to prevent a deprecation warning at startup.
# This setting cannot end in a slash.
#server.basePath: ""

# Specifies whether Kibana should rewrite requests that are prefixed with
# `server.basePath` or require that they are rewritten by your reverse proxy.
# This setting was effectively always `false` before Kibana 6.3 and will
# default to `true` starting in Kibana 7.0.
#server.rewriteBasePath: false

# The maximum payload size in bytes for incoming server requests.
#server.maxPayloadBytes: 1048576

# The Kibana server's name.  This is used for display purposes.
server.name: "xxx"

# The URLs of the Elasticsearch instances to use for all your queries.
elasticsearch.hosts: ["http://xxx:9200", "http://xxx:9200"]

# When this setting's value is true Kibana uses the hostname specified in the server.host
# setting. When the value of this setting is false, Kibana uses the hostname of the host
# that connects to this Kibana instance.
#elasticsearch.preserveHost: true

# Kibana uses an index in Elasticsearch to store saved searches, visualizations and
# dashboards. Kibana creates a new index if the index doesn't already exist.
kibana.index: ".reporting"

# The default application to load.
#kibana.defaultAppId: "discover"

# If your Elasticsearch is protected with basic authentication, these settings provide
# the username and password that the Kibana server uses to perform maintenance on the Kibana
# index at startup. Your Kibana users still need to authenticate with Elasticsearch, which
# is proxied through the Kibana server.
elasticsearch.username: "xxx"
elasticsearch.password: "xxx"

#elasticsearch.customHeaders: [ "Authorization: Basic dGVzdDp0ZXN0" ]

# Enables SSL and paths to the PEM-format SSL certificate and SSL key files, respectively.
# These settings enable SSL for outgoing requests from the Kibana server to the browser.
#server.ssl.enabled: true
#server.ssl.certificate: /ca/testweb01.crt
#server.ssl.key: /ca/testweb01_decrypted.key

# Optional settings that provide the paths to the PEM-format SSL certificate and key files.
# These files validate that your Elasticsearch backend uses the same key files.
#elasticsearch.ssl.certificate: /path/to/your/client.crt
#elasticsearch.ssl.key: /path/to/your/client.key

# Optional setting that enables you to specify a path to the PEM file for the certificate
# authority for your Elasticsearch instance.
#elasticsearch.ssl.certificateAuthorities: [ "/path/to/your/CA.pem" ]

# To disregard the validity of SSL certificates, change this setting's value to 'none'.
elasticsearch.ssl.verificationMode: none

# Time in milliseconds to wait for Elasticsearch to respond to pings. Defaults to the value of
# the elasticsearch.requestTimeout setting.
elasticsearch.pingTimeout: 1500

# Time in milliseconds to wait for responses from the back end or Elasticsearch. This value
# must be a positive integer.
elasticsearch.requestTimeout: 60000

# List of Kibana client-side headers to send to Elasticsearch. To send *no* client-side
# headers, set this value to [] (an empty list).
elasticsearch.requestHeadersWhitelist: [ authorization ]

# Header names and values that are sent to Elasticsearch. Any custom headers cannot be overwritten
# by client-side headers, regardless of the elasticsearch.requestHeadersWhitelist configuration.
#elasticsearch.customHeaders: {}

# Time in milliseconds for Elasticsearch to wait for responses from shards. Set to 0 to disable.
elasticsearch.shardTimeout: 60000

# Time in milliseconds to wait for Elasticsearch at Kibana startup before retrying.
#elasticsearch.startupTimeout: 5000

# Logs queries sent to Elasticsearch. Requires logging.verbose set to true.
elasticsearch.logQueries: false

# Specifies the path where Kibana creates the process ID file.
#pid.file: /var/run/kibana.pid

# Enables you specify a file where Kibana stores log output.
logging.dest: /var/log/kibana/kibana.log

# Set the value of this setting to true to suppress all logging output.
#logging.silent: false

# Set the value of this setting to true to suppress all logging output other than error messages.
#logging.quiet: false

# Set the value of this setting to true to log all events, including system usage information
# and all requests.
#logging.verbose: false

# Set the interval in milliseconds to sample system and process performance
# metrics. Minimum is 100ms. Defaults to 5000.
ops.interval: 5000

# Specifies locale to be used for all localizable strings, dates and number formats.
# Supported languages are the following: English - en , by default , Chinese - zh-CN .
i18n.locale: "en"


# Disable XPack - could collide with readonlyrest plugin
#xpack.graph.enabled: false
#xpack.ml.enabled: false
#xpack.monitoring.enabled: true
#xpack.security.enabled: false
#xpack.watcher.enabled: false
#xpack.reporting.enabled: false
xpack.security.session.lifespan: 0
xpack.security.session.idleTimeout: 0
xpack.reporting.roles.enabled: false
#xpack.monitoring.collection.enabled: true
#xpack.reporting.enabled: false
#kibana.index: ".kibana-a"
#xpack.task_manager.index: ".kibana_task_manager-*"

# Customization
#readonlyrest_kbn.login_custom_logo: '/plugins/readonlyrest_kbn/logo.png'
#readonlyrest_kbn.login_html_head_inject: '<style>body{background:#0096A1}</style><script>document.addEventListener("DOMContentLoaded", function(event) {document.getElementsByClassName("ror-footer")[0].childNodes[0].childNodes[0].innerHTML="You are on Test  environment!"})</script>'
#readonlyrest_kbn.login_title: "Internal Security Kibana"
#readonlyrest_kbn.login_subtitle: "Welcome to <b>Internal Security Test Kibana</b> instance.<br/><br/>To login, please enter your CORP domain credentials, in format firstname.lastname (withoutdomain).<br/><br/>To report an issue or send feedback, contact us on <a href=\"mailto:miroslav.kardos@xxx.com?subject=ELK%20issue\">miroslav.kardos@xxx.com</a>"
#readonlyrest_kbn.login_subtitle: "<h1 style='color:red'>Emergency maintenance from 13:00 CET to 17:00 CET. Login is disabled.</h1>"
#readonlyrest_kbn.session_timeout_minutes: 1440


# REPORTING
#xpack.reporting.kibanaServer.port: 443
#xpack.reporting.kibanaServer.protocol: https
#xpack.reporting.kibanaServer.hostname: xxxx
#xpack.reporting.encryptionKey: "xxxx"
#xpack.reporting.capture.browser.chromium.disableSandbox: false
#xpack.reporting.index: ".reporting-*"


## MONITORING
#xpack.monitoring.elasticsearch.hosts: http://my_ip:9200
monitoring.kibana.collection.enabled: false
#monitoring.enabled: true
#xpack.monitoring.ui.enabled: true
#xpack.monitoring.cluster_alerts.email_notifications.email_address: "miroslav.kardos@xxx.sk"
#xpack.monitoring.kibana.collection.enabled: true

# READONLYREST session handling
readonlyrest_kbn.cookiePass: "xxxxx"
readonlyrest_kbn.store_sessions_in_index: true
readonlyrest_kbn.sessions_refresh_after: 1000
readonlyrest_kbn.sessions_probe_interval_seconds: 43200

I Found you can add to /etc/systemd/system/kibana.service line :

--deprecation.skip_deprecated_settings[0]="xpack.reporting.index"

Is this OK or NOK ?

[Unit]
Description=Kibana

Documentation=https://www.elastic.co
Wants=network-online.target
After=network-online.target

type or paste code here

[Service]
Type=simple
User=kibana
Group=kibana

Environment=KBN_HOME=/usr/share/kibana
Environment=KBN_PATH_CONF=/etc/kibana

EnvironmentFile=-/etc/default/kibana
EnvironmentFile=-/etc/sysconfig/kibana

ExecStart=/usr/share/kibana/bin/kibana --logging.dest="/var/log/kibana/kibana.log" --pid.file="/run/kibana/kibana.pid" --**deprecation.skip_deprecated_settings[0]="xpack.reporting.index" --deprecation.skip_deprecated_settings[1]="logging.dest"**

Restart=on-failure
RestartSec=3

StartLimitBurst=3
StartLimitInterval=60

WorkingDirectory=/usr/share/kibana

StandardOutput=journal
StandardError=inherit

[Install]
WantedBy=multi-user.target`Preformatted text`

I guess that should be ok.

Note that the upgrade assistant does not check 3rd party plugins like the ones you added.