metrics

This is kind of a follow up to #32677 and the PR #34762.

In #34762 we improved the test data source implementation by checking the body of the response from Tempo. The Tempo team is not comfortable making the body of a 404 response part of our stable API, so instead we are currently adding a separate endpoint specifically for testing: /api/echo (grafana/tempo#714).

Hi @apache/skywalking-committers and contributors

SkyWalking INFRA e2e subproject is almost ready to release because this is for testing scope only, we could adopt it in the main repo based on commit IDs.

We are welcome everyone to join this and replace the existing Java Maven based e2e tests. The latest one should be much more friendly and m

Above the fields list and in the layer pane, change Change index pattern to Index pattern.

Above fields list:

In layer pane:
![Screen Shot 2021-07-15 at 3 23 11 PM](https://user-images.githubusercontent.com/38990715/125852638-d794c03c-86b1-4

If I set all the prefixes (globalPrefix, prfixTimer, etc.) to "", what kind of ramifications will that have on the server side if any? Will all the timers, gauges, counters be calculated as normal or will see if any side effects?

Hi
Wikiann dataset needs to have "spans" columns, which is necessary to be able to use this dataset, but this column is missing from huggingface datasets, could you please have a look? thank you @lhoestq

Before opening, please confirm:

• I have searched for duplicate or closed issues and discussions.
• I have read the guide for submitting bug reports.
• I have done my best

Currently the labels for NFS metrics from mountstats are "export", "protocol", "mountaddr"

I'm requesting that another label be added, the mountpoint on the NFS client.

For example if /proc/self/mountstats had the following device info:
device myhostname.com:/exports/example mounted on /auto/example with fstype nfs statvers=1.1

I'd like to have a label: `mountpoint: /auto/example

We see many devs from Germany are using SigNoz. It would be be good if README is translated to German.

This will make it easier for devs from Germany and German speaking countries to get started with SigNoz.

Scenario

create table tab(f float);
insert into tab(f) values(4273.8);

Results in: org.postgresql.util.PSQLException: ERROR: inconvertible types: DOUBLE -> FLOAT [from=4273.8, to=f]

Expectation

Possibly enhance type compatibility check (SqlCompiler.isAssignableFrom) with extra cases for numeric types:

• Float <- Double: if the double fits in the Float, then

For the moment there is no ability to use IAM instance profile for access to s3 bucket as it is not described in documentation
Could yo

提问题？
请把问题现象、相关日志、初步排查结果写清楚，即提供尽量多的线索，这样方便我们定位问题。

提建议？
请写明白建议原因，即为何有此建议。

提修复PR？
请说明为何做此修改，需要做好测试。

提Feature？
建议先将想法提出，不着急写代码，与社区同道沟通，大家觉得OK再做代码实现

---

另外，我们是在做开源软件，不是服务于您的企业，做您的乙方，您一分钱没付，就不要颐指气使了，认同我们这个社区，则参与进来，不认同，就不参与，谢谢理解

🚀 Feature

Here is the feature I would like to have, for example, with TensorboardLogger, but we can implement that for all exp tracking systems:

tb_logger = TensorboardLogger(log_dir="experiments/tb_logs")

tb_logger.attach_output_handler(
    trainer,
    event_name=Events.ITERATION_COMPLETED,
    tag="training",
    state_attrs=["alpha", "beta"]  # <->  trainer.state.alph

As we all know golang has give us the feature that convert proto to json with https://github.com/golang/protobuf/blob/master/jsonpb/encode.go ,and with encode.go ,we can define diffrent style like casesensitive , emit empty , json indent and so on , we can see [Customizing Protobuf JSON Serialization in Go](https://seb-nyberg.medi