If i set up a nagios alert notification escalation definition, is it possible to somehow tell nagios to pause escalation while someone who's notified earlier tries to fix the problem?
e.g. if the web server starts flapping but someone tries to fix it, there's no need to notify people further up the chain.
Thanks
You can use Acknowledge this service problem command on the service's page.
This command is used to acknowledge a
service problem. When a service
problem is acknowledged, future
notifications about problems are
temporarily disabled until the service
changes from its current state. If you
want acknowledgement to disable
notifications until the service
recovers, check the 'Sticky
Acknowledgement' checkbox. Contacts
for this service will receive a
notification about the
acknowledgement, so they are aware
that someone is working on the
problem. Additionally, a comment will
also be added to the service. Make
sure to enter your name and fill in a
brief description of what you are
doing in the comment field. If you
would like the service comment to
remain once the acknowledgement is
removed, check the 'Persistent
Comment' checkbox. If you do not want
an acknowledgement notification sent
out to the appropriate contacts,
uncheck the 'Send Notification'
checkbox.
For more information, see http://www.bulletproof.net.au/Tutorials/How-to-acknowledge-an-alert.aspx
Related
After the successful authentication on Google, user get event information
Which is processed on our server.
But if any events edit or delete user is not able to getting update regarding this, user need again call calender api.
How we can get changing update regarding google calendar events on our server without again call of calendar api.
If I understand you correctly, you want to receive a notification to your server whenever a calendar event changes.
If that's the case, consider using push notifications:
First, set up a URL where notifications will be received.
Second, call Events: watch to set up the notification channel.
Take a look at push notifications for a complete guide on this, and Events: watch for documentation on the method you'll have to call after setting up the webhook.
I want to push notifications to my Alexa Device until the recent notification is seen by the user. If the user has seen the notification I should stop sending it. If the customer hasn't seen my recent notification I should keep on sending the notifications until they have seen it.
So I need to identify whether my notification has been seen by the user or not.
Is there any service or API that could fetch me whether the delivered notification is seen by the user or not?
As far as I know, Proactive Events are one-way and not bidirectional: you send a notification to the user, the user can read it but there is no way to know if the user has read the notification.
I'm building an app using MEAN Stack (something like Facebook). So a user can login to my app using different browsers and I want for example, if there user will add a new message to the MongoDB, I want to update his messages in the other sessions. The same of he will remove a massage. At the same time, there maybe logged in different users from different browsers and I want to notify the user with his update in the other sessions.
Does Socket.io supports such an option? And what is the best way to do it?
Thanks.
Yes socket.io do support that. Here is an example made by socket.io themselves: https://github.com/socketio/socket.io/tree/master/examples/chat
You should be looking for socket.on() which are the listeners for an event on the server side and look into socket.emit() which are the senders of the events. the .emit()could be added into an function which are triggered on a button click for example.
Depending on you needs, if you're going to send the message to every user using your app then you could use this above code. But if you only wants to send to a specific list of persons you should look into something called Rooms (http://socket.io/docs/rooms-and-namespaces/#rooms).
This does exactly what it sounds like, it emits the messages to the specific room where users have been added to when they connect to your application.
I am curious how others are solving the following problem...
I have an angular application that requires user authentication. The user must log in to the system to make requests. The user must also be authorized to create a socket.io connection.
When the application first starts up I must determine if the user is already authorized. I was planning on looking in sessionStorage for a user object/token. Does that make sense? And if the user is not authorized, the application will make a request to get the current user. If/When that fails, a 401 error is returned and angular intercepts/prompts for a username/password.
Given that there are two different code paths for authentication (check sesssionStorage vs make a request and wait for the response) how do you trigger the requests for all the other information that is required for the application? Do you emit/listen to a LOGIN event that gets broadcast in both scenarios?
My plan was to wrap the socket.io connection attempt and the ".on(...)" calls inside of the LOGIN event, does that make sense?
And if you want to listen to socket.io events or grab information from the server in a controller that is loaded after the LOGIN event has fired, how do you trigger the data from being retrieved from the server?
Sorry for the long winded questions, but I've hit a road block and I'm wondering how others are managing all the authentication and different pieces of information that is required to get from the server.
Ok, I guess let's go in order of question asked.
Does it make sense to use sessionStorage to hold user auth info?
Yes. You will need to decide between local/session Storage depending on how you want it to work. We decided we wanted the session to still be active for the time period that the backend recognizes, so even if the user closes the browser and reopens it, they will be logged in, and so we opted for localStorage instead of sessionStorage.
How do you trigger the requests for all the other information that is required for the application? Do you emit/listen to a LOGIN event that gets broadcast in both scenarios?
After login, we redirect the user to the "landing" page (route). All of our route/state changes wait on a resolve function which is doing the session auth. We only store the session id in localStorage. After the successful state change, the controllers that go with the newly loaded views start requesting data from our services. All of our controllers are designed to load data on init. So no, we do not use events. It feels like events should be used only as a last resort - and that is also the impression I get from core Angular devs since I get chastised for event usage in pull requests :)
My plan was to wrap the socket.io connection attempt and the ".on(...)" calls inside of the LOGIN event, does that make sense?
Maybe. I am not using socket.io outright, but instead have been experimenting with atmosphere (mainly because we had a java backend requirement). I do initiate the connection in the login success handler. But the general atmosphere event handling I have put into an application-level controller that is on <body>.
And if you want to listen to socket.io events or grab information from the server in a controller that is loaded after the LOGIN event has fired, how do you trigger the data from being retrieved from the server?
I could imagine (again using an app-level controller, or a service, or in my case, likely both) a function that returns the socket.io connection. A controller that has come into being could grab the socket.io stuff on init, and setup the listeners for the events that it is interested in.
My advice is to get all of your session and auth stuff worked out first, especially with regard to how you are going to do routing. Once all of it is working to your satisfaction, then add the socket.io stuff in. I realize that this might not be possible in all cases because perhaps you need something from the socket.io connection that is critical to your app even at an early stage.
I'm writing a service in "C" and I'd like to display a warning window once the user tries to stop the service ( With "OK" and "Cancel" Buttons ).
Is there any specific windows API available to achieve this?
Any other simple ways are there to achieve??
No, this is not possible. Windows services are unable to interact directly with the user's desktop, so they will be unable to show a user interface of any kind.
This shouldn't really be a big deal, though. You have to have adequate permissions to stop and start a service, and by default, only Administrators have those rights. If you don't want users inadvertently stopping your service, then you should take advantage of permissions to solve that problem for you.
You stop a service with Service control panel; your service normally doesn't have access to this control panel process, so you can't override it's UI and present a dialog asking OK/Cancel.
I just learned the hard way that any calls made to the UI from a service will cause it to hang. MSDN does have a page here on work arounds.
If you don't want anybody to be able to stop the service, just tell the service manager that you don't accept stop messages. You could instead provide an application that stops the service (using some form of IPC) and that application could present as many warning messages as you wanted.
On the other hand, this will annoy your users, and it is unlikely to be necessary. By default, only administrators can stop services, and people are unlikely to try to stop your service without a good reason.