Samplerate=44100 quality=10%2e0 channels=2 (LadioCast) audio-info Information about the bitrate/samplerate/quality of the stream. Metadata set by source client audio_bitrate Audio bitrate in bits/sĬan be set by source client audio_channels Number of audio channels. Metadata set by source client title Title of the current song Please note that the statistics are valid within the scope of the current source connection.Ī reconnect or disconnection will reset those. stats_connections Number of times a stats client has connected to Icecast. stats The total of currently connected STATS clients. sources The total of currently connected sources. source_total_connections Both clients and relays. source_relay_connections Number of outbound relay connections to (master) icecast servers. source_client_connections Source client connections are the number of times (cumulative since start-up, not just currently connected) a source This field is deprecated and may be removed in a future version, server_start Timestamp of server startup in RFC 2822 date format. server_start_iso8601 Timestamp of server startup in ISO 8601 date format. While not recommended it can be overriden in server_id Defaults to the version string of the currently running Icecast server. location As set in the server config, this is a free form field that should describe e.g. listeners Number of currently active listener connections. listener_connections Number of listener connections to mount points. host As set in the server config, this should be the full DNS resolveable name or FQDN for the host on which this file_connections This is an accumulating counter. connections The total of all inbound TCP connections since start-up. clients Number of currently active client connections. These include listeners (not concurrent,īut cumulative), any admin function accesses, and any static content (file serving) accesses. client_connections Client connections are basically anything that is not a source connection. Usually this will be an email address, but as this can be an arbitrary string it could also be a phone number. General Statistics admin As set in the server config, this should contain contact details for getting in touch with the server administrator. The following example stats tree will be used: 2.5 Stats XML tree will be shown and each element will be described. This section contains information about the raw XML server statistics data available inside Icecast. Still we recommend to design robust software that can deal with possible changes like addition or removal of variables.Īlso note that not all variables are available all the time and availability may change at runtime due to stream type, etc. The intention is to not break backwards compatibility of this interface in the future, It exposes the same set of server statistics that are available through the web interface and Since version 2.4.0 Icecast includes a basic JSON endpoint ( /status-json.xsl) based on a xml2json template by Doeke Zanstra For example, to specify sliderEntry, either of sliderEntry or the longer .SliderEntry may be given.We strongly discourage attempts to scrape data from the web interface as we do not consider this anĪPI and will change it, even completely, between versions! The preferred ways are custom XSLT, JSON and raw XML. The component's tag name may be specified, or for backwards compatibility, the component class name may still be specified. For example, to specify sliderEntry, .SliderEntry would be given. The component's full class name must be specified. For this reason, applications may specifically list the components by name, space delimited, that they wish to pre-load. There is a performance cost to pre-loading every component's resources, especially when this might apply to components that your application may not even use at all. A simple yet blunt method of accomplishing this is to set it to all, so that every componnt which participates in the MandatoryResourceComponent mechanism may have their resources pre-loaded into the head. In that case, it's necessary to have pre-loaded the resources into the head, for the eventuality of the component being later dynamically added to the view. This can cause problems when a component is initially not in the page, but then on a postback it is dynamically added to the page. When none is specified, then only when a component is actually on the page will its Javascript and CSS resources be rendered into the head of the page. The mandatoryResouceConfiguration may be set to one of three values: none, all, or a space delimited list of components. false mandatoryResourceConfigurationĭefault is 'all' in ICEfaces 2.0, and 'none' in ICEfaces 3.0+
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |