metrics

What happened:

The classnames library is not necessary as emotion/css has a similar function called cx. For consistency we should refactor our codebase to only use emotion's classname implementation.

Tasks:

• Check performance when using the classNames library vs using the c

PagerDuty(https://www.pagerduty.com/) is widely used for on-call globally. We are welcome the contributions to support it as alarm notification channel.

Kibana version: 7.15.0 BC-4 Kibana Cloud environment

Host OS and Browser version: All, Chrome and Firefox

Build details:

Build: 43886
Commit: 29a6969dc230abf16dc65a41c535cb534ae64fa7
Artifact Link: https://staging.elastic.co/7.15.0-9e0972b3/summary-7.15.0.html

Preconditions:

1. 7.15.0 BC-4 Kibana Cloud environment should be available.
2. Agent must be insta

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?

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

Host operating system: output of uname -a

Linux sarbian 5.13.5-arch1-1 #1 SMP PREEMPT Sun, 25 Jul 2021 18:02:58 +0000 x86_64 GNU/Linux

node_exporter version: output of node_exporter --version

node_exporter, version 1.2.0 (branch: tarball, revision: 1.2.0)
build user: someone@builder
build date:
go version: go1.16.5
platform: linux/amd64

n

We support opentelemetry, so it should be possible to instrument ruby applications and visualise data on SigNoz. But we don't have lots of expertise in Ruby in the core team, so we have not tested this.

https://github.com/open-telemetry/opentelemetry-ruby

It would be good first issue for folks expert in Ruby to test this and report their findings. If this works fine, we can add this to our d

Is your feature request related to a problem? Please describe.
So I'm working on a product that should allow schema-less ingestion out of the box. So my default ingestion method is via the influx line protocol.

But my challenge is that I also need to add indexes to some of the tags (symbols) after table creation. The problem is that the Influx Line protocol holds a lock to the table makin

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再做代码实现

---

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

Currently we are rendering our examples in the docs like this https://pytorch.org/ignite/generated/ignite.engine.engine.Engine.html#ignite.engine.engine.Engine which is not very neat.
What we want to do is to find a better way to make it more good looking, and update our docs examples

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