-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Telemetry. Report "server.name" setting usage #114508
Comments
Pinging @elastic/kibana-core (Team:Core) |
@Bamieh isn't this info already accessible via the kibana/src/core/server/core_usage_data/core_usage_data_service.ts Lines 507 to 509 in c766a2b
kibana/src/core/server/core_usage_data/core_usage_data_service.ts Lines 351 to 353 in c766a2b
|
Indeed we do send telemetry for this setting (and all configs)
Note that it is reported as |
We're only sending it when it's explicitly set by the user via the config, right? |
@pgayvallet yes it is only sent if the user sets it (even if they set it manually to match the exact default value). I've used existing apis from core to do this |
Should we close this issue? |
server.name
has been introduced in #4335 and it was renamed once in #5587Right now it serves the only purpose to populate
kbn-name
response header. It's not clear whether we should continue supporting the features. Before making a decision to remove it, we want to understand how often it's used by Kibana users.Extend
core_usage_collector
to get information on whetherserver.name
has been set in the config file explicitlykibana/src/core/server/core_usage_data/core_usage_data_service.ts
Line 263 in dc1e1b1
Note that a default value is used if no value is set in the
kibana.yml
filekibana/src/core/server/http/http_config.ts
Line 34 in b7acb1a
The text was updated successfully, but these errors were encountered: