Opserver | Stack Exchange 's Monitoring System | Monitoring library

by opserver C# Version: v0.1 License: MIT

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | Opserver Summary

Opserver is a C# library typically used in Performance Management, Monitoring applications. Opserver has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

Opserver is a monitoring system by the team at Stack Exchange, home of Stack Overflow. It is a tool for monitoring:. Known as “status” internally, Opserver provides a fast overall view of all our major systems that also allows drilling in for more detail. For an idea of the UI, you can see some screenshots from our Velocity 2013 talk.

Support

Quality

Security

License

Reuse

Support

Opserver has a medium active ecosystem.

It has 4311 star(s) with 823 fork(s). There are 316 watchers for this library.

It had no major release in the last 6 months.

There are 67 open issues and 158 have been closed. On average issues are closed in 99 days. There are 3 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of Opserver is v0.1

Quality

Opserver has 0 bugs and 0 code smells.

Security

Opserver has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

Opserver code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

Opserver is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

Opserver releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Opserver saves you 21410 person hours of effort in developing the same functionality from scratch.

It has 42045 lines of code, 0 functions and 476 files.

It has low code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of Opserver

Get all kandi verified functions for this library.

Opserver Key Features

No Key Features are available at this moment for Opserver.

Opserver Examples and Code Snippets

No Code Snippets are available at this moment for Opserver.

Community Discussions

Trending Discussions on Opserver

Retrieve Azure AppInsights Live Metrics through API

Right tools to implement logging and monitoring

QUESTION

Retrieve Azure AppInsights Live Metrics through API

Asked 2019-Dec-27 at 21:06

There is an one year old question How can I retrieve through an API *Live Metrics* of Microsoft Application Insights about is it possible to pull LiveMetrics data that appInsights generate for the application trough some API

Right now i don't see anything live related in the official documentation - https://dev.applicationinsights.io/reference . And the answer for old question was also that there is no any way to get them.

But maybe someone knows if AppInsights team plans were changed in this year and they are working on that API?

It might be really useful to pull that data in realtime through API to own alerting\metrics system to process data from different microservices\applications and display them in aggregated way in realtime. As example we can build something like OpServer has but based on different applications and their AppInsights data .

As right now there is no any way to get it

...

ANSWER

Answered 2019-Dec-27 at 21:06

Note: I work in Application Insights team at Microsoft.

LiveMetrics data is not persistently stored anywhere, and there is no API to retrieve it. The data is collected only when someone is actively on the Live Metrics portal page. The moment browser window is closed, data is gone as well.

If your goal is to get metrics/other in real-time, then you can do that by implementing own ITelemetryProcessor. Most people use ITelemetryProcessor to "filter" out unwanted telemetry. But that is not a rule. All telemetry passes through TelemetryProcessor, and you can chose to filter the data or do something else with it. In your case you want to send it instantly to some real-time service. In fact, LiveMetrics (internally known as QuickPulse) is implemented as a TelemetryProcessor. (https://github.com/microsoft/ApplicationInsights-dotnet/blob/develop/WEB/Src/PerformanceCollector/Perf.Shared/QuickPulseTelemetryProcessor.cs#L158)

General doc about TelemetryProcessor: https://docs.microsoft.com/en-us/azure/azure-monitor/app/api-filtering-sampling#create-a-telemetry-processor-c

Source https://stackoverflow.com/questions/59504687

QUESTION

Right tools to implement logging and monitoring

Asked 2019-Oct-20 at 06:38

My team and I recently started working on a new project. Our project is layered in 3 tiers - client (Winforms Application), middle ware (.NET Core 3.0 Web API), Database (PostgreSQL). I was assigned to find the optimal way to implement a logging and monitoring system.

What we need is log every exception (of course), as well as every query that our middle ware does to our database and also some audit logs. Bear in mind that these logs will occur very often since the users are more than 200 concurrently.

At first my search began from the noSQL databases. I was thinking of picking MongoDb, Cassandra or ElasticSearch, since they are fast and do not need a specific schema and log everything there. But then I stumbled upon this great blog post by Nick Craver - the Architecture Lead for Stack Exchange. There he mentions the use of StackExchange.Exceptional and I think that this is what we actually need. But I am not sure how to actually use it and which of all those great solutions that Nick gives I need for my use case.

So I am asking:

if you have ever used Exceptional enlighten me of its uses
do i need OPServer too to monitor the logs?
am I still better using just Mongo?

...

ANSWER

Answered 2019-Oct-19 at 16:35

If you asking me I will be going with ELKB stack. I haven't use OPServer. So I am not going to comment on this. But I would like to share my opinion about elasticsearch how your use case can be achievable on this.

As far I understand you have two things need to log:

Every Exception/Errors
Middleware Query logs

ELKB stack is designed for these use cases only. Where there will be a river kind of flow. Your logs will keep storing in Elasticsearch.

Below are a few steps for how you can achieve your use case:

Step 1: Setup Elasticsearch. For this, you don't need to be any professional. Just follow the wonderfull document they have.
Step 2: Setup Logstash / Filebeat which will read your logs file in realtime and keep inserting in Elasticsearch.
Step 3: Setup Kibana over the elasticsearch. You will get a complete view of your data logs.
Step 4: Just add logs point in your app where you will get Exceptions or you want to log something else.

PROS :

All tools are readymade and used by many other organizations with very heavy use cases. So it will be fit in your use case too.
Very good documentation and community support.
Great data view by kibana. You can create your own dashboard. It is like one view for your whole system logs.
There are already Some of beats available like MySQL beats, Nginx Beats, Apache beats, Mongo DB, etc.. Here you have to just plug and start using those.
It will be your centralize architecture whenever you want to add some new type of logs, You need to just start writing in the same log file and it will start logging.

There are lots of prons you will find on the Internet.

CONS:

You can set alert over this using 'watcher', which is paid.
If you want to set open source alert, You can go with alertmanager (Prometheus) where you need to do some extra integrations.

Below are a few Use cases I would like to share. I am sure it will help you out to understand:

Dream11 : https://medium.com/@D11Engg/elasticsearch-dream11-30328d913cd5
Uber : https://eng.uber.com/elk/
Ebay : https://www.elastic.co/blog/monitoring-petabytes-of-logs-at-ebay-with-beats

Source https://stackoverflow.com/questions/58462701

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install Opserver

Installation should be a snap, just build this project as-is and deploy it as an IIS website. If monitoring windows servers and using integrated auth sections (e.g. live polling, SQL, exception logs) then using a service account with needed permissions is all you need to do on the auth side. After that, configure Opserver to monitor your systems, keep reading for how.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: