Skip to content
#

observability

Here are 304 public repositories matching this topic...

netdata
pmuellr
pmuellr commented Oct 27, 2020

Currently there is no explicit way to "refresh" the alerts list or the alert details view, to view the most recent data. Unless you make some UI action on the page, the data will never be updated, once it's rendered.

You can implicitly refresh those pages with current data by performing some other action on the view:

  • on the alerts list, you can switch from the the "Alerts" tab to the "C
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:

odin
ttymck
ttymck commented Aug 2, 2020

Describe the bug
Deploying a new job, then pulling logs via the CLI results in a panic (SIGSEGV).

To Reproduce

  1. odin deploy -f test.job.yaml
  2. odin log -i {job_id}
vagrant@vagrant:~/odin$ odin log -i dea194794589
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x40 pc=0x79c764]

goroutine

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

You can’t perform that action at this time.