observability

Hi,

first thanks for this awesome software. But I have some trouble and I don't know how to proceed. First I try to find out what else I could provide for this report to be a good bug report.

First, I use the latest version (v1.14.0) from openSUSE build Service. I know, I should compile it by my self to avoid any other causes for this behavior. But for now I still use this package from there

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

I find some configurations are in configurations.md , but not in the agent.config , such as agent.trace_segment_ref_limit_per_span 、agent.instance_properties[key]=value . Otherwise , the configuration ```

All APM apis with very few exceptions should be marked as internal. We can do that easily by prefxing a route with /internal/. APM apis are defined in: x-pack/plugins/apm/server/routes

Public APIs:

• [Agent configuration APIs](https://www.elastic.co/guide/en/kibana/master/ag

What's it about?
When you want to select the drop-down menu box in the console, you can search by regular expression or sort by the letters A-Z
What's the reason why we need it?
Can improve the development efficiency, shorten the search time
I believe this is an important feature for Kubesphere. There're a few use cases:
For example, if I have 200 services on a project, I have to manu

Is your feature request related to a problem?

The first step towards app optimization

Please describe.
Configure whyDidYouRender under the development env

**Note: make sure it is compatible with all the custom hooks that we are using in the project **

We recently added support for dynamic tags in Ruby and Python integrations. We need to do the same in our Go app.

Here's an example from our python docs:

# You can use a wrapper:
with pyroscope.tag_wrapper({ "controller": "slow_controller_i_want_to_profile" }):
  slow_code()

# Or you can add / remove tags manually:
pyroscope.tag({ "controller": "slow_controller_i_want_to_profi

It would be helpful to add a 'Download' (to file) option to the Kiali Debug information view, instead of having to copy/paste into a file.

Why: When opening the Event Injection modal for a particular eventBus, the tool populates each field (source, detail type, and detail) with the last values used for that eventBus. Allowing all events to be saved, similar to the command history in the terminal, will allow users to quickly test multiple events without having to type the same parameters repeatedly.

Expected Behaviour:

please look at images

like this