Skip to content
#

observability

Here are 402 public repositories matching this topic...

netdata
wu-sheng
wu-sheng commented May 3, 2021

We have Linux monitoring, metrics collected by Prometheus and Zabbix agents. Some people in the community are asking about monitoring Windows OS, which is not very popular in service backend deployment, but still have some.
If someone new to SkyWalking or anything, want to take a reference from existing Linux monitoring and add this feature. We are welcome to accept.

stacey-gammon
stacey-gammon commented May 12, 2021

As per elastic/kibana#99462 (reply in thread), IIndexPattern is deprecated (and possibly IFieldType too?).

If an @deprecated flag is added into the description with an @removeBy we can start getting folks off of it and a path for removal. Usage would also show up in the deprecated API list [here](https://elasticdocstest.netlify.app/kibana-dev-docs/dep

daniel-hutao
daniel-hutao commented Apr 29, 2021

I have been asked several times whether the value filled in cc.spec.common.es.externalElasticsearchUrl requires an http prefix, but it is actually not needed, but this key is a bit confusing. I don’t know if I need an http prefix sometimes when I look at it, so I think it’s clearer to change it to externalElasticsearchUrl to externalElasticsearchHost

/kind feature-request

pyroscope
signoz
sls-dev-tools
mansurpasha
mansurpasha commented May 11, 2020

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:

regexrowboat
regexrowboat commented Nov 1, 2016

Currently, JavaScript SDK logs status code 0 when the connection between the client and server cannot be resolved. This makes diagnosing network errors very difficult, as there are many different problems that can cause 0 status code in failing dependency calls.

The proposal is to log status code information that indicates whether a network error occurred and what type.

Improve this page

Add a description, image, and links to the observability topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the observability topic, visit your repo's landing page and select "manage topics."

Learn more