Methods
- Activities
- Alarms
- Audit
- Buckets
- Clearance
- Commands
- COP-1
- Database
- Events
- File Transfer
- IAM
- Indexes
- Instances
- Links
- MDB Override
- MDB
- Packets
- Parameter Archive
- Parameter Lists
- Parameter Values
- Processing
- Queues
- Replication
- RocksDB
- Sdls
- Server
- Services
- Sessions
- Stream Archive
- Table
- Time Correlation
- Time
- Timeline
Yamcs Release Notes
Yamcs Server Manual
Source Code Documentation
List EventsΒΆ
List events
URI Template
GET /api/archive/{instance}/events
POST /api/archive/{instance}/events:list
{instance}Yamcs instance name
Query Parameters
posThe zero-based row number at which to start outputting results. Default:
0This option is deprecated and will be removed in a later version. Use the returned continuationToken instead.
limitThe maximum number of returned records per page. Choose this value too high and you risk hitting the maximum response size limit enforced by the server. Default:
100orderThe order of the returned results. Can be either
ascordesc. Default:descseverityThe minimum severity level of the events. One of
info,watch,warning,distress,criticalorsevere. Default:infosourceThe source of the events. Names must match exactly.
nextContinuation token returned by a previous page response.
startFilter the lower bound of the event's generation time. Specify a date string in ISO 8601 format. This bound is inclusive.
stopFilter the upper bound of the event's generation time. Specify a date string in ISO 8601 format. This bound is exclusive.
qText to search for in the message.
filterFilter query. See Filtering for how to write a filter query.
Literal text search matches against the fields
message,sourceandtype.Field comparisons can use any of the following fields:
messagestring
seqNumbernumber
severityenum
One of
info,watch,warning,distress,criticalorsevere.sourcestring
typestring
Response Type
interface ListEventsResponse {
// Deprecated, use ``events`` instead
event: Event[];
// Page with matching events
events: Event[];
// Token indicating the response is only partial. More results can then
// be obtained by performing the same request (including all original
// query parameters) and setting the ``next`` parameter to this token.
continuationToken: string;
}
Related Types
interface Event {
source: string;
generationTime: string; // RFC 3339 timestamp
receptionTime: string; // RFC 3339 timestamp
seqNumber: number;
type: string;
message: string;
severity: EventSeverity;
// Set by API when event was posted by a user
createdBy: string;
// Additional properties
extra: {[key: string]: string};
}
enum EventSeverity {
INFO = "INFO",
WARNING = "WARNING",
// Legacy, avoid use.
ERROR = "ERROR",
WATCH = "WATCH",
// Placeholder for future WARNING constant.
// (correctly sorted between WATCH and DISTRESS)
//
// Most clients can ignore, this state is here
// to give Protobuf clients (Python Client, Yamcs Studio)
// the time to add a migration for supporting both WARNING
// and WARNING_NEW (Protobuf serializes the number).
//
// Then in a later phase, we move from:
// WARNING=1, WARNING_NEW=4
//
// To:
// WARNING_OLD=1, WARNING=4
//
// (which is a transparent change to JSON clients)
WARNING_NEW = "WARNING_NEW",
DISTRESS = "DISTRESS",
CRITICAL = "CRITICAL",
SEVERE = "SEVERE",
}