95e5edd9c4
Instruments Kibana with Elastic APM by adding the Node.js agent to the source code. The agent is not turned on by default but can be enabled by setting the environment variable `ELASTIC_APM_ACTIVE=true` or by creating an apm config file called `config/apm.dev.js` and setting `active: true` inside of it. This implementation is not meant to be used by end-users of Kibana as it lacks integration with the regular Kibana config file. For now, this is meant as a useful internal tool for Elastic employees when developing Kibana. By default, it's pre-configured with a `serverUrl` pointing to an APM Server hosted on Elastic Cloud. The data is stored in an ES cluster accessible only by Elastic employees. These defaults can easily be overwritten using environment variables or via the custom config file.
82 lines
2.9 KiB
JavaScript
82 lines
2.9 KiB
JavaScript
/*
|
|
* Licensed to Elasticsearch B.V. under one or more contributor
|
|
* license agreements. See the NOTICE file distributed with
|
|
* this work for additional information regarding copyright
|
|
* ownership. Elasticsearch B.V. licenses this file to you under
|
|
* the Apache License, Version 2.0 (the "License"); you may
|
|
* not use this file except in compliance with the License.
|
|
* You may obtain a copy of the License at
|
|
*
|
|
* http://www.apache.org/licenses/LICENSE-2.0
|
|
*
|
|
* Unless required by applicable law or agreed to in writing,
|
|
* software distributed under the License is distributed on an
|
|
* "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
|
* KIND, either express or implied. See the License for the
|
|
* specific language governing permissions and limitations
|
|
* under the License.
|
|
*/
|
|
|
|
/**
|
|
* DO NOT EDIT THIS FILE!
|
|
*
|
|
* This file contains the configuration for the Elastic APM instrumentaion of
|
|
* Kibana itself and is only intented to be used during development of Kibana.
|
|
*
|
|
* Instrumentation is turned off by default. Once activated it will send APM
|
|
* data to an Elasticsearch cluster accessible by Elastic employees.
|
|
*
|
|
* To modify the configuration, either use environment variables, or create a
|
|
* file named `config/apm.dev.js`, which exports a config object as described
|
|
* in the docs.
|
|
*
|
|
* For an overview over the available configuration files, see:
|
|
* https://www.elastic.co/guide/en/apm/agent/nodejs/current/configuration.html
|
|
*
|
|
* For general information about Elastic APM, see:
|
|
* https://www.elastic.co/guide/en/apm/get-started/current/index.html
|
|
*/
|
|
|
|
const { readFileSync } = require('fs');
|
|
const { join } = require('path');
|
|
const { execSync } = require('child_process');
|
|
const merge = require('lodash.merge');
|
|
|
|
module.exports = merge({
|
|
active: false,
|
|
serverUrl: 'https://f1542b814f674090afd914960583265f.apm.us-central1.gcp.cloud.es.io:443',
|
|
// The secretToken below is intended to be hardcoded in this file even though
|
|
// it makes it public. This is not a security/privacy issue. Normally we'd
|
|
// instead disable the need for a secretToken in the APM Server config where
|
|
// the data is transmitted to, but due to how it's being hosted, it's easier,
|
|
// for now, to simply leave it in.
|
|
secretToken: 'R0Gjg46pE9K9wGestd',
|
|
globalLabels: {},
|
|
centralConfig: false,
|
|
logUncaughtExceptions: true
|
|
}, devConfig());
|
|
|
|
const rev = gitRev();
|
|
if (rev !== null) module.exports.globalLabels.git_rev = rev;
|
|
|
|
try {
|
|
const filename = join(__dirname, '..', 'data', 'uuid');
|
|
module.exports.globalLabels.kibana_uuid = readFileSync(filename, 'utf-8');
|
|
} catch (e) {} // eslint-disable-line no-empty
|
|
|
|
function gitRev() {
|
|
try {
|
|
return execSync('git rev-parse --short HEAD', { encoding: 'utf-8' }).trim();
|
|
} catch (e) {
|
|
return null;
|
|
}
|
|
}
|
|
|
|
function devConfig() {
|
|
try {
|
|
return require('./apm.dev'); // eslint-disable-line import/no-unresolved
|
|
} catch (e) {
|
|
return {};
|
|
}
|
|
}
|