How to monitor a YACS server using RSS?
Actually it is almost as simple as the usual subscription to any RSS feed. We only have added some HTTP authentication to restrict access to associates.
[title]Where is the feed?[/title]
The very first step is to locate the monitoring feed.
Unix guys have to know that the target link is at the following address:
Windows guys, who are well known to use the mouse only, can use the following tutorial 8)
From the home page of the target YACS server, use the shortcut to the index page for feeds.
If no shortcut appears at the home page, go to the control panel, and then select the feeds module.
The link we are looking after should be listed just after the usual feed formats.
If the link does not appear, it is likely that either you are not logged in, or you are not an associate
Use the right button of your mouse to copy the link.
[title]How to configure the news reader?[/title] Then launch your preferred news reader. For this tutorial we have used FeedReader, but any news reader that supports HTTP authentication would be ok.
Ask the news reader to create a new feeding entry.
Then paste the feed link and click on the
FeedReader attempts to read the feed, but the server asks for authentication.
Therefore FeedReader displays a dialog box to let you provide a user name and a password.
Please note that you have to provide credentials related to a valid user profile with associates privileges.
Click on the
The server provides the feed, and FeedReader allows for title modification before recording the entry.
The default name is always 'Event log at <your_server>', but you can change this if you wish.
Let FeedReader updates the feed and that's it!
[title]What's next?[/title]
Here is a general view of FeedReader after the update.
The channel information provides some links to the home page and to the control panel of the monitored server.
For each information item the originating script is placed is the topic field. Quite handy for software developers ::)
You can now stay tuned to your server(s) all the day long if you wish.
In the example below, the server reports an issue with one of the feeds it is supposed to aggregate.
Hmm, I will probably trigger the debugging facility of YACS and see what's happening here :P . But that's another story.
Unix guys have to know that the target link is at the following address:
http://<your_server>/yacs/agents/feed.php
Windows guys, who are well known to use the mouse only, can use the following tutorial 8)
From the home page of the target YACS server, use the shortcut to the index page for feeds.
If no shortcut appears at the home page, go to the control panel, and then select the feeds module.
The link we are looking after should be listed just after the usual feed formats.
If the link does not appear, it is likely that either you are not logged in, or you are not an associate
Use the right button of your mouse to copy the link.
[title]How to configure the news reader?[/title] Then launch your preferred news reader. For this tutorial we have used FeedReader, but any news reader that supports HTTP authentication would be ok.
Ask the news reader to create a new feeding entry.
Then paste the feed link and click on the
Next button.FeedReader attempts to read the feed, but the server asks for authentication.
Therefore FeedReader displays a dialog box to let you provide a user name and a password.
Please note that you have to provide credentials related to a valid user profile with associates privileges.
Click on the
Next button. FeedReader attempts to read the feed again, adding authentication credentials.The server provides the feed, and FeedReader allows for title modification before recording the entry.
The default name is always 'Event log at <your_server>', but you can change this if you wish.
Let FeedReader updates the feed and that's it!
[title]What's next?[/title]
Here is a general view of FeedReader after the update.
The channel information provides some links to the home page and to the control panel of the monitored server.
For each information item the originating script is placed is the topic field. Quite handy for software developers ::)
You can now stay tuned to your server(s) all the day long if you wish.
In the example below, the server reports an issue with one of the feeds it is supposed to aggregate.
Hmm, I will probably trigger the debugging facility of YACS and see what's happening here :P . But that's another story.