Hi we added a new plugin check for Cabot that allows Cabot to create something similar to https://deadmanssnitch.com/ . It uses redis keys to check for background jobs/processes that fail to check in within a specific interval. Also unlike Deadmansnitch it works with much more granular intervals down to seconds or even larger ones like days.

https://github.com/objectstoragesolutions/cabot-

Hello,

Is there is any UI documentation for adding custom collector info ? Also to add any new models and repositories for custom collector ?
Trying to build tfs deployment collector

Thanks in advance
Priya.

Multiples wiki issues.

Typos

• https://github.com/infobyte/faraday/wiki/Executive-Report#using-markdown-on-a-report: -lenguage +language

Bad links

• https://github.com/infobyte/faraday/wiki/Executive-Report#requirements: https://github.com/infobyte/faraday/wiki/first-steps, the nedpoint first-steps doesn't exist anymore.

Images

• https://github.com/infob

Hi,

would it be possible to offer a swagger document that describes the REST API?
Having this, it would be easy to create additional clients, also for the administrative interfaces.

Thanks!
Cheers, Lutz.

Is it possible to add support for usernames already defined in the ssh config? It isn't technically "passing" it but ssh just uses it. This is how I believe Ansible works. This would be very helpful so (a) usernames aren't hardcoded and (b) a username configured already for the server in ssh so you don't duplicate the definition elsewhere.

An easy example is ec2-user for Amazon Linux instanc

Hello -

If windows support has been merged into Frontail as mentioned in #194 then the readme should be updated to include it.

Currently the readme states:

Installation options
download a binary file from Releases page (currently **frontail doesn't work on Windows**)

The nomad-acl-token is being logged at the default logging level of info. I think that it makes sense to log other useful info at info level, but secret info like tokens would ideally never be logged, or at best, at debug level only.
In looking at the code, it seems most if not all logging is done at the info level, so other levels of logging aren't very useful as a work-around.

That

The protobuf "well-known types" (https://developers.google.com/protocol-buffers/docs/reference/google.protobuf) are included in every language runtime, including the npm package (see protocolbuffers/protobuf#1638).

Currently, grpcc requires proto files that import a well-known type to have a copy of the well-known type locally, otherwise you get an `Error: failed to import '...

We need a proper website, with docs, examples, etc.
Basic static generation (e.g. with Gatsby) from markdown (to allow for current docs reuse) would probably work just fine.

• Make a static website (done thanks to @FDiskas )
• Setup CI builds on every push / PR
• Setup CD to github pages
• Figure out a domain (github org domain? .js.org domain? something else?)

When I visit /swagger-stats/ui, it seems that request will stay in processing status for statistics.
And I see [api_all_request_in_processing_total] growing when I visit /swagger-stats/ui.
Is that correct? The swagger-stats version I used is 0.95.6.

Is your feature request related to a problem? Please describe.

I am unable to add instrumentation for Global Objects in the agent in a way that is described here. There are few methods that I needed to instrument like eval(), setTimeout() etc.
(PS: I don't know if I am approaching this right)

**Describe the solution you'd li

Right now, when you archive a key, you can only see it if you manually search for it.

This can cause some key name conflict issues, or issues when trying to create a folder with the same name as an archived (bu not yet deleted key).

It would be ideal for there to be a way to see all archived keys at once, without the need to search for them in the search bar.

With CodeCommit's new Approval Rule Template feature there should be a separate message denoting this. The current implementation defaults to a generic message of Pull Request <number>