# Backport
This will backport the following commits from `main` to `8.12`:
- [[Profiling,Infra,APM] Disable Profiling integration by default
(#175201)](https://github.com/elastic/kibana/pull/175201)
<!--- Backport version: 8.9.8 -->
### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)
<!--BACKPORT [{"author":{"name":"Mykola
Harmash","email":"mykola.harmash@gmail.com"},"sourceCommit":{"committedDate":"2024-01-24T11:44:26Z","message":"[Profiling,Infra,APM]
Disable Profiling integration by default (#175201)\n\nCloses
https://github.com/elastic/kibana/issues/175016\r\n\r\n##
Summary\r\n\r\nThis PR disables the Profiling integration in Infra and
APM by default\r\non the plugin configuration level because this
integration require users\r\nto first configure the main `profiling`
plugin. On-prem users will have\r\nto manually enable both integrations
once they enabled the Universal\r\nProfiling for their hosts. Cloud
users will have Infra and APM\r\nintegrations enabled by default because
on Cloud instances Universal\r\nProfiling is already configured. A PR
for the default Cloud settings\r\nwill follow after this one is
merged.\r\n\r\nChanges I've made:\r\n* Disabled the Infra integration be
default\r\n* Introduced a new APM feature flag for the Profiling
integration\r\n* Made sure all the places in APM that rely on Profiling
integration\r\nrespect the new feature flag\r\n* Fixed a bug in APM when
Universal Profiling was shown even though the\r\nintegration was
disabled in UI
settings\r\n\r\n\r\n65dfbb5b-1850-4d18-a92a-6ad59e0436a3\r\n\r\n##
How To Test\r\n\r\n1. Checkout locally\r\n2. Make sure you don't have
`xpack.infra.featureFlags.profilingEnabled`\r\nalready enabled in
`kibana.yml`\r\n3. Open kibana and make sure you don't see \"Universal
Profiling\" tab in\r\nHost and Service details\r\n4. Enabled both flags
in `kibana.yml`:\r\n`xpack.infra.featureFlags.profilingEnabled`
and\r\n`xpack.apm.featureFlags.profilingIntegrationAvailable:
true`\r\n5. Check that now you see \"Universal Profiling\" tab in the
details\r\nscreens in both Infra and APM\r\n6. Go to Infra settings view
and disable the Profiling integration, make\r\nsure the tab
disappears\r\n7. 6. Go to APM settings view and disable the Profiling
integration,\r\nmake sure the tab
disappears\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"abd3515dda40d48bd0c59f7d2861ffa86db133c1","branchLabelMapping":{"^v8.13.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","backport
missing","Team:obs-ux-infra_services","v8.12.1","v8.13.0"],"number":175201,"url":"https://github.com/elastic/kibana/pull/175201","mergeCommit":{"message":"[Profiling,Infra,APM]
Disable Profiling integration by default (#175201)\n\nCloses
https://github.com/elastic/kibana/issues/175016\r\n\r\n##
Summary\r\n\r\nThis PR disables the Profiling integration in Infra and
APM by default\r\non the plugin configuration level because this
integration require users\r\nto first configure the main `profiling`
plugin. On-prem users will have\r\nto manually enable both integrations
once they enabled the Universal\r\nProfiling for their hosts. Cloud
users will have Infra and APM\r\nintegrations enabled by default because
on Cloud instances Universal\r\nProfiling is already configured. A PR
for the default Cloud settings\r\nwill follow after this one is
merged.\r\n\r\nChanges I've made:\r\n* Disabled the Infra integration be
default\r\n* Introduced a new APM feature flag for the Profiling
integration\r\n* Made sure all the places in APM that rely on Profiling
integration\r\nrespect the new feature flag\r\n* Fixed a bug in APM when
Universal Profiling was shown even though the\r\nintegration was
disabled in UI
settings\r\n\r\n\r\n65dfbb5b-1850-4d18-a92a-6ad59e0436a3\r\n\r\n##
How To Test\r\n\r\n1. Checkout locally\r\n2. Make sure you don't have
`xpack.infra.featureFlags.profilingEnabled`\r\nalready enabled in
`kibana.yml`\r\n3. Open kibana and make sure you don't see \"Universal
Profiling\" tab in\r\nHost and Service details\r\n4. Enabled both flags
in `kibana.yml`:\r\n`xpack.infra.featureFlags.profilingEnabled`
and\r\n`xpack.apm.featureFlags.profilingIntegrationAvailable:
true`\r\n5. Check that now you see \"Universal Profiling\" tab in the
details\r\nscreens in both Infra and APM\r\n6. Go to Infra settings view
and disable the Profiling integration, make\r\nsure the tab
disappears\r\n7. 6. Go to APM settings view and disable the Profiling
integration,\r\nmake sure the tab
disappears\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"abd3515dda40d48bd0c59f7d2861ffa86db133c1"}},"sourceBranch":"main","suggestedTargetBranches":["8.12"],"targetPullRequestStates":[{"branch":"8.12","label":"v8.12.1","labelRegex":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"},{"branch":"main","label":"v8.13.0","labelRegex":"^v8.13.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/175201","number":175201,"mergeCommit":{"message":"[Profiling,Infra,APM]
Disable Profiling integration by default (#175201)\n\nCloses
https://github.com/elastic/kibana/issues/175016\r\n\r\n##
Summary\r\n\r\nThis PR disables the Profiling integration in Infra and
APM by default\r\non the plugin configuration level because this
integration require users\r\nto first configure the main `profiling`
plugin. On-prem users will have\r\nto manually enable both integrations
once they enabled the Universal\r\nProfiling for their hosts. Cloud
users will have Infra and APM\r\nintegrations enabled by default because
on Cloud instances Universal\r\nProfiling is already configured. A PR
for the default Cloud settings\r\nwill follow after this one is
merged.\r\n\r\nChanges I've made:\r\n* Disabled the Infra integration be
default\r\n* Introduced a new APM feature flag for the Profiling
integration\r\n* Made sure all the places in APM that rely on Profiling
integration\r\nrespect the new feature flag\r\n* Fixed a bug in APM when
Universal Profiling was shown even though the\r\nintegration was
disabled in UI
settings\r\n\r\n\r\n65dfbb5b-1850-4d18-a92a-6ad59e0436a3\r\n\r\n##
How To Test\r\n\r\n1. Checkout locally\r\n2. Make sure you don't have
`xpack.infra.featureFlags.profilingEnabled`\r\nalready enabled in
`kibana.yml`\r\n3. Open kibana and make sure you don't see \"Universal
Profiling\" tab in\r\nHost and Service details\r\n4. Enabled both flags
in `kibana.yml`:\r\n`xpack.infra.featureFlags.profilingEnabled`
and\r\n`xpack.apm.featureFlags.profilingIntegrationAvailable:
true`\r\n5. Check that now you see \"Universal Profiling\" tab in the
details\r\nscreens in both Infra and APM\r\n6. Go to Infra settings view
and disable the Profiling integration, make\r\nsure the tab
disappears\r\n7. 6. Go to APM settings view and disable the Profiling
integration,\r\nmake sure the tab
disappears\r\n\r\n---------\r\n\r\nCo-authored-by: Kibana Machine
<42973632+kibanamachine@users.noreply.github.com>","sha":"abd3515dda40d48bd0c59f7d2861ffa86db133c1"}}]}]
BACKPORT-->
aa102263c2