profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/reactima/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Ilya Sidorov reactima Platforms change the world San Francisco Tokyo Singapore Melbourne https://www.linkedin.com/in/reactima-san-francisco/ Reactjs D3 Nodejs Python Golang Redis RabbitMQ PostgreSQL Elastic AWS DevOps

reactima/adeptima-hiring 0

Adeptima Hiring repo

reactima/coding-interview-university 0

A complete computer science study plan to become a software engineer.

reactima/react-plugin-system 0

Basic plugin system for React applications

reactima/reactima-d3 0

Repo for quick and vanilla D3.js prototyping

reactima/reactima-go 0

Collection of Golang helpers for bundling Echo, Postgres, Websockets, Query Builders, Loggers, Data Binding, Validors, etc together

reactima/reactima-slate-go 0

Package for server side html rendering of internal json format from incredible Slatejs editor

issue openedopenfaas/faas

Call for feedback/ideas for FaaS Metric Collection with Prometheus

Hi!

Sorry if creating an issue for this is not the right way, but I can see OpenFaas is recommending Prometheus for metric collection: https://docs.openfaas.com/architecture/metrics/

As the Prometheus community, we are looking for feedback/ideas on how to improve monitoring of the world of Serverless/FaaS. In this thread, I am specifically looking for:

  • Existing best practices for using Prometheus for gathering metrics from Serverless/FaaS platforms and functions
  • Specific gaps and limitation users might have in these scenarios
  • Existing success stories?
  • Ideas for improvements.

If you want to help please feel free to respond on prometheus-dev mailing list: https://groups.google.com/g/prometheus-developers/c/FPe0LsTfo2E 🤗

created time in 11 hours

startededgeware/mp4ff

started time in 2 days

startedssb-ngi-pointer/ssb-network-errors

started time in 2 days

created repositoryssb-ngi-pointer/ssb-network-errors

Detect various muxrpc and network errors between SSB peers

created time in 2 days

release cube-js/cube.js

v0.27.35

released time in 2 days

startedhandshake-org/hs-airdrop

started time in 2 days

fork matryer/go-stdlib

OpenTracing instrumentation for packages in the Go stdlib

fork in 3 days

startedtestdouble/standard

started time in 4 days

push eventopenfaas/faas

Alex Ellis

commit sha 36e93983093c52e0f4eaab75898c7aee6174877c

Create EULA.md

view details

push time in 5 days

release benbjohnson/litestream

v0.4.0-alpha.0

released time in 8 days

startedtwitter/twemoji

started time in 11 days

pull request commentopenfaas/faas

blogs: add new post for 2021

Thank you for this PR

jsiebens

comment created time in 11 days

push eventopenfaas/faas

Johan Siebens

commit sha f0780198d320cdcccec40898099ff10357dbd3eb

blogs: add new post for 2021 Signed-off-by: Johan Siebens <johan.siebens@gmail.com>

view details

push time in 11 days

PR merged openfaas/faas

blogs: add new post for 2021 new-contributor

Signed-off-by: Johan Siebens johan.siebens@gmail.com

<!--- Provide a general summary of your changes in the Title above -->

Description

<!--- Describe your changes in detail -->

Motivation and Context

<!--- Why is this change required? What problem does it solve? --> <!--- If it fixes an open issue, please link to the issue here. -->

  • [ ] I have raised an issue to propose this change (required)
  • [ ] My issue has received approval from the maintainers or lead with the design/approved label

How Has This Been Tested?

<!--- Please describe in detail how you tested your changes. --> <!--- Include details of your testing environment, and the tests you ran to --> <!--- see how your change affects other areas of the code, etc. -->

Types of changes

<!--- What types of changes does your code introduce? Put an x in all the boxes that apply: -->

  • [ ] Bug fix (non-breaking change which fixes an issue)
  • [ ] New feature (non-breaking change which adds functionality)
  • [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

<!--- Go over all the following points, and put an x in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->

  • [x] My code follows the code style of this project.
  • [ ] My change requires a change to the documentation.
  • [ ] I have updated the documentation accordingly.
  • [x] I've read the CONTRIBUTION guide
  • [x] I have signed-off my commits with git commit -s
  • [ ] I have added tests to cover my changes.
  • [ ] All new and existing tests passed.
+1 -0

0 comment

1 changed file

jsiebens

pr closed time in 11 days

startedsnowpackjs/astro

started time in 11 days

startedumesh-timalsina/riju

started time in 12 days

PR opened openfaas/faas

blogs: add new post for 2021

Signed-off-by: Johan Siebens johan.siebens@gmail.com

<!--- Provide a general summary of your changes in the Title above -->

Description

<!--- Describe your changes in detail -->

Motivation and Context

<!--- Why is this change required? What problem does it solve? --> <!--- If it fixes an open issue, please link to the issue here. -->

  • [ ] I have raised an issue to propose this change (required)
  • [ ] My issue has received approval from the maintainers or lead with the design/approved label

How Has This Been Tested?

<!--- Please describe in detail how you tested your changes. --> <!--- Include details of your testing environment, and the tests you ran to --> <!--- see how your change affects other areas of the code, etc. -->

Types of changes

<!--- What types of changes does your code introduce? Put an x in all the boxes that apply: -->

  • [ ] Bug fix (non-breaking change which fixes an issue)
  • [ ] New feature (non-breaking change which adds functionality)
  • [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

<!--- Go over all the following points, and put an x in all the boxes that apply. --> <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->

  • [x] My code follows the code style of this project.
  • [ ] My change requires a change to the documentation.
  • [ ] I have updated the documentation accordingly.
  • [x] I've read the CONTRIBUTION guide
  • [x] I have signed-off my commits with git commit -s
  • [ ] I have added tests to cover my changes.
  • [ ] All new and existing tests passed.
+1 -0

0 comment

1 changed file

pr created time in 12 days

startedstaltz/nj-tag-prebuild

started time in 12 days

created repositorystaltz/nj-tag-prebuild

Rename a node-bindgen index.node to a prebuildify-style file

created time in 12 days

startedshadowwalker/next-pwa

started time in 13 days

startedhuytd/vscode-github-light-monochrome

started time in 13 days

release benbjohnson/litestream

v0.3.5

released time in 14 days

release benbjohnson/litestream

v0.3.5-alpha.10

released time in 14 days

release vslinko/obsidian-outliner

1.2.5

released time in 15 days

release vslinko/obsidian-outliner

1.2.4

released time in 15 days

release vslinko/obsidian-outliner

1.2.3

released time in 15 days

release vslinko/obsidian-outliner

1.2.2

released time in 15 days

startedstaltz/ssb-validate2-rsjs-wasm

started time in 16 days

created repositorystaltz/ssb-validate2-rsjs-wasm

Cryptographic validation of Scuttlebutt messages

created time in 16 days

startedssb-ngi-pointer/ssb-validate2-rsjs-node

started time in 16 days